Numbers of DB in SQL

Is there a limitation of how many db you can have in SQL Standard Edition?
Will it cause problem if we have too much? somewhere around 45 DBs.
Thanks.The documented limit is 32767 databases per server instance, so you have
some way to go yet! With the appropriate hardware 45 databases is certainly
no problem.
--
David Portas
SQL Server MVP
--|||Thanks for replied my post. My server is a Dell 8450 Quad-processors with 2
GB of RAM.
"David Portas" wrote:
> The documented limit is 32767 databases per server instance, so you have
> some way to go yet! With the appropriate hardware 45 databases is certainly
> no problem.
> --
> David Portas
> SQL Server MVP
> --
>
>|||David,
I think that when David Portas mentioned "appropriate hardware", he didn't
mean that there's some magic formula for 45 databases. It depends on what
those databases are doing -- how much data they contain, how many users
concurrently use each of them, what those users are doing, etc. If each
database has 100 concurrent users doing million-row queries, you'll quickly
run into a problem. On the other hand, if each database has 1 table with 10
rows of data and has a query run against it once a week, you'll be able to
support thousands of databases :)
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"David" <David@.discussions.microsoft.com> wrote in message
news:668C567C-E459-4ABB-A1F7-129BBADD6EB8@.microsoft.com...
> Thanks for replied my post. My server is a Dell 8450 Quad-processors with
2
> GB of RAM.
> "David Portas" wrote:
> > The documented limit is 32767 databases per server instance, so you have
> > some way to go yet! With the appropriate hardware 45 databases is
certainly
> > no problem.
> >
> > --
> > David Portas
> > SQL Server MVP
> > --
> >
> >
> >|||David,
In addition to David's and Adam's excellent responses, you may find
limitations with SQL-DMO which will manifest through Enterprise Manager.
After a certain number of databases, you will find that enumeration of
databases will take a long time when you expand the databases node in
the tree. At some point you will find that it takes longer than you are
willing to wait for it, and you will have to administer your databases
using T-SQL.
SMO in SQL Server 2005 addresses this issue by using partial
instantiation (aka delayed instantiation) and caching.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
David wrote:
> Is there a limitation of how many db you can have in SQL Standard Edition?
> Will it cause problem if we have too much? somewhere around 45 DBs.
> Thanks.
>

Number times Stored Proc. executed in week?

I have a server with SQL Server 2000 Enterprise Edition
with one production database.
Is there a way to determine the number of times a stored
procedure or view as executed within a week time interval?
Thanks,
MikeYou would have to log this yourself or with a tool. Three potentially
relevant articles:
http://www.aspfaq.com/search.asp?q=lumigent
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:f81401c43dfd$d38c1610$a001280a@.phx.gbl...
> I have a server with SQL Server 2000 Enterprise Edition
> with one production database.
> Is there a way to determine the number of times a stored
> procedure or view as executed within a week time interval?
> Thanks,
> Mike|||Mike,
No, unless you have the trace files or any logic inside the proc which will
log into some table.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:f81401c43dfd$d38c1610$a001280a@.phx.gbl...
> I have a server with SQL Server 2000 Enterprise Edition
> with one production database.
> Is there a way to determine the number of times a stored
> procedure or view as executed within a week time interval?
> Thanks,
> Mike

Number of licences & Calls

My Problem is that I don’t know really what does a call means.

We got a SQL Standard Edition.

Can I install as many instances I want in a Server?

How many users can access the Server at the same time?

If I use SQL authentication, and two users use this logging information, how many calls do they made? 2 one per each user (PC) or just 1 one per logging.

If I have a client / server application, and the server access the SQL Server using SQL authentication. Can I have unlimited number of clients?

SQL Server is generally speaking licensed per processor or per Client Access Licenses (CALs). CALs, are merely the maximum number of CONCURRENT USERS you may have. Thus, if you had 10 CALs, up to 10 Clients could access your SQL Server at the same time. In my experience, most companies purchase the product on the CPU model though it is usually not cheap.

Can I install as many instances I want in a Server? Not sure license wise on this, but my hunch is yes

How many users can access the Server at the same time? See above, CPU model is unlimited clients, CALs are not unlimited.

If I use SQL authentication, and two users use this logging information, how many calls do they made? If at the same time, 2 CALs, else 1.

Hope this Helps,

Derek

|||

Standard Edition is limited to a maximum of 16 Instances.

There is no limit to the number of users. However, each user MUST have a Client Access License (CAL) UNLESS the server is operating under a 'Processor' license.

Effective End Users count as a user, not the number of Logins, or servers accessing data, etc.

For a Public Web application, where client licenses cannot be determined, requires a 'Processor' license. A private web application may operate with each client having a CAL and the server only a 'server' license.

So, to clarify, each end user of data served by SQL Server MUST covered with a CAL or the server MUST have a 'Processor' license.

For the definitie answers about licensing, call the licensing folks at:

Licensing –VL Contact
(800) 426-9400

For Other licensing questions/answers:

Licensing -FAQ
http://www.microsoft.com/sql/howtobuy/faq.mspx

Licensing -SQL 2000
http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part2/c0461.mspx?mfr=true

Licensing -SQL 2005
http://download.microsoft.com/download/e/c/a/ecafe5d1-b514-48ab-93eb-61377df9c5c2/SQLServer2005Licensingv1.1.doc

Number of databases

This may sound like a silly question, but is their a limit
to how many databases you can have on a SQL 2000
Enterprise Edition?
Our orginization has a Clustered SQL server and I have
always just put all of our databases on it. I am having
no problems with performance but was chastised for having
so many on it any way. I have 83 databases.
Anyway I was curious if Microsoft has a reccomendation of
max amount of db.
Thanks
jjThis is a multi-part message in MIME format.
--=_NextPart_000_0190_01C35B57.E055FD40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
You're allowed 32,727 database per instance of SQL Server.
-- Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"John Jarrett" <jarrej@.yahoo.com> wrote in message =news:013c01c35b78$7a919430$a401280a@.phx.gbl...
This may sound like a silly question, but is their a limit to how many databases you can have on a SQL 2000 Enterprise Edition?
Our orginization has a Clustered SQL server and I have always just put all of our databases on it. I am having no problems with performance but was chastised for having so many on it any way. I have 83 databases.
Anyway I was curious if Microsoft has a reccomendation of max amount of db.
Thanks
jj
--=_NextPart_000_0190_01C35B57.E055FD40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

You're allowed 32,727 database per =instance of SQL Server.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"John Jarrett" wrote in =message news:013c01c35b78$7a=919430$a401280a@.phx.gbl...This may sound like a silly question, but is their a limit to how many =databases you can have on a SQL 2000 Enterprise Edition?Our =orginization has a Clustered SQL server and I have always just put all of our databases =on it. I am having no problems with performance but was chastised =for having so many on it any way. I have 83 databases. Anyway I was curious if Microsoft has a reccomendation of =max amount of db.Thanksjj

---

--=_NextPart_000_0190_01C35B57.E055FD40--|||> This may sound like a silly question, but is their a limit
> to how many databases you can have on a SQL 2000
> Enterprise Edition?
Yes. The limit is 32767 per server instance.
> Anyway I was curious if Microsoft has a reccomendation of
> max amount of db.
The above is the limit stated in BOL. Other factors (such as size, number of
users / transactions) will be far more significant constraints on
performance than the number of DBs. Possibly you might want to limit the
number of DBs per server for administrative reasons or in the interests of
availability and resilience but I'm looking at 4 servers which have a total
of 188 DBs between them, so 83 doesn't seem excessive by that benchmark.
--
David Portas
--
Please reply only to the newsgroup
--|||I have a client who is currently running 700 databases on 1 server. And
while the system seems to be functioning, they are seeing latency in data
showing up. Meaning that a record that is added or updated to the database
doesent seem to show up for hours.
These databases average about 150MB each. Is there any configuration option
that would help this, or is this something that they just need to throw more
hardware at?
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:eVHkQu3WDHA.3248@.tk2msftngp13.phx.gbl...
> > This may sound like a silly question, but is their a limit
> > to how many databases you can have on a SQL 2000
> > Enterprise Edition?
> Yes. The limit is 32767 per server instance.
> > Anyway I was curious if Microsoft has a reccomendation of
> > max amount of db.
> The above is the limit stated in BOL. Other factors (such as size, number
of
> users / transactions) will be far more significant constraints on
> performance than the number of DBs. Possibly you might want to limit the
> number of DBs per server for administrative reasons or in the interests of
> availability and resilience but I'm looking at 4 servers which have a
total
> of 188 DBs between them, so 83 doesn't seem excessive by that benchmark.
> --
> David Portas
> --
> Please reply only to the newsgroup
> --
>
>|||You should run performance monitor, and run various SQL, cpu, memory and
disk counters to try to determine where the bottleneck is. I was almost
about to suggest changing the affinity mask if you had more than two
processors (because I remember that from studying). When you get
performance counter measurements back, you can tell whether to throw more
memory, CPU, upgrade the disk subsystem or if it is something more
configurable software wise (adjusting system properties to favor background
processes, adjusting pagefile size and location, creating filegroups to move
database objects to other disks, etc). Good luck.
--
*************************************
Andy S.
andy_mcdba@.yahoo.com
*************************************
"Robert Barr" <RobertLBarr@.cox.net> wrote in message
news:%23jn7wEXfDHA.1712@.TK2MSFTNGP11.phx.gbl...
> I have a client who is currently running 700 databases on 1 server. And
> while the system seems to be functioning, they are seeing latency in data
> showing up. Meaning that a record that is added or updated to the database
> doesent seem to show up for hours.
> These databases average about 150MB each. Is there any configuration
option
> that would help this, or is this something that they just need to throw
more
> hardware at?
>
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
> news:eVHkQu3WDHA.3248@.tk2msftngp13.phx.gbl...
> > > This may sound like a silly question, but is their a limit
> > > to how many databases you can have on a SQL 2000
> > > Enterprise Edition?
> >
> > Yes. The limit is 32767 per server instance.
> >
> > > Anyway I was curious if Microsoft has a reccomendation of
> > > max amount of db.
> >
> > The above is the limit stated in BOL. Other factors (such as size,
number
> of
> > users / transactions) will be far more significant constraints on
> > performance than the number of DBs. Possibly you might want to limit the
> > number of DBs per server for administrative reasons or in the interests
of
> > availability and resilience but I'm looking at 4 servers which have a
> total
> > of 188 DBs between them, so 83 doesn't seem excessive by that benchmark.
> >
> > --
> > David Portas
> > --
> > Please reply only to the newsgroup
> > --
> >
> >
> >
>

number of CPUs that are assigned to each NUMA node

Hello,
SQL Server STD edition with sp2 plus cumlative update package 2
os = 2003 enterprise edition 64 bit.
After looking at http://support.microsoft.com/kb/329204
I was wondering how to detect the number of CPUs that are assigned to each
NUMA node.
I have issued the following :
SELECT DISTINCT memory_node_id
FROM sys.dm_os_memory_clerks
with the return of:
Memory_node_id
0
3
1
2
I believe this indicates that hardware NUMA is enabled.
This box has 4 dual core procs.
TIA,Yes, and I believe that relates back to parent_node_id in
sys.dm_os_schedulers
--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:A7FB4D85-F710-4CC1-843C-8A8D80D167BB@.microsoft.com...
> Hello,
> SQL Server STD edition with sp2 plus cumlative update package 2
> os = 2003 enterprise edition 64 bit.
> After looking at http://support.microsoft.com/kb/329204
> I was wondering how to detect the number of CPUs that are assigned to each
> NUMA node.
> I have issued the following :
> SELECT DISTINCT memory_node_id
> FROM sys.dm_os_memory_clerks
> with the return of:
> Memory_node_id
> 0
> 3
> 1
> 2
> I believe this indicates that hardware NUMA is enabled.
> This box has 4 dual core procs.
> TIA,sql