When you use sql 2005 management studio to connect to a sql 2005 server, you can deny view on any database and one user will not be able to see any database that he/she does not own.
However, what about if this person uses sql 2005 management studio to connect to a sql 2000 server. Since sql 2005 management studio does not call the store procedure sp_MSdbuseraccess, it will display all the database in the server.
It does not seem like I can use "deny view on any database to username" on a sql 2000 server.
Does anyone have any idea what I need to do in order to not show all the database when I use sql 2005 management studio to connect to a sql 2000 server box?
Thank you.EM will show the database as existing, but you can still deny access to the database and prevent people from opening it up or viewing the objects and data inside it.
Only admins should be using Enterprise Manager anyway...|||What I want to do is to deny any login id (who owns certain database) to not be able to see other database at all.
Just like sql 2005, you can run "deny view any database to userid"
However, doesn't seem like sql 2000 has this command.|||The databases are like houses. You can prevent people from going inside, but you can't prevent people from seeing them.
Showing posts with label databases. Show all posts
Showing posts with label databases. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
How Much More Can I Put on This SQL Server?
It depends on kind of db applications you are running,
database design, overall size of databases in GB etc. A
database which is not bulky (for example more than 50gb)
in size, where most tables have a pk, and pre-defined
queries fetch one or few records at a time based on a
unique where condition, you could have few hundreds
simulaneious connections. Whereas in a data warehouse
application where you have really huge tables, users are
allowed to create and run queries as they like, and each
query ususally reads through millions of records, few
simulatneious users can saturate the system, and sometime
even one user can dominate the whole system.
Based on the information you have given, your db server
falls more into the first category, 150 or more
simultaneous users could stress the system. If possible,
you should run a stress test to see when the cpu hits 90%
or more utilization, that will be the saturation point.
i hope this answers your question to some extent. Let us
know if you have further questions.
>--Original Message--
>We have a 4 processor (Xeon 700mhz), 3GB, SQL Server 2000
Standard Edition,
>Win2K Standard, with 3 RAID Array's. Currently running
about 20 databases,
>75 concurrent connections. Performance monitor readings
look good,
>processor rarely goes above 35 percent, memory looks
good, the disk drives
>spike but are usually not too busy.
>My question is how much more can I load on this thing
(ballpark) before it
>starts to get even medium stress. I'm looking for anyone
with a similar
>configuration, with much bigger numbers to get some idea
of how fare I can
>go with this machine. I have looked on www.tpc.org site
and similar
>configurations list 67,000 concurrent users and 87,000
tmp, but that just
>doesn't seem real.
>Thanks for any info.
>Steven Berringer
>
>.
>Thanks for the feedback. I guess I was hoping to hear from someone who had
a similar configuration and had X number of users connected and running at
the same time. I understand the OLTP versus OLAP and good database design,
and all that, but 150 is a far cry from the 67,000 listed on the tpm web
site for a 4 processor box.
Does anyone have any real world stories?
Thanks
Steven
<anonymous@.discussions.microsoft.com> wrote in message
news:1401701c3f7c3$8b5961c0$a501280a@.phx
.gbl...
> It depends on kind of db applications you are running,
> database design, overall size of databases in GB etc. A
> database which is not bulky (for example more than 50gb)
> in size, where most tables have a pk, and pre-defined
> queries fetch one or few records at a time based on a
> unique where condition, you could have few hundreds
> simulaneious connections. Whereas in a data warehouse
> application where you have really huge tables, users are
> allowed to create and run queries as they like, and each
> query ususally reads through millions of records, few
> simulatneious users can saturate the system, and sometime
> even one user can dominate the whole system.
> Based on the information you have given, your db server
> falls more into the first category, 150 or more
> simultaneous users could stress the system. If possible,
> you should run a stress test to see when the cpu hits 90%
> or more utilization, that will be the saturation point.
> i hope this answers your question to some extent. Let us
> know if you have further questions.
>
>
> Standard Edition,
> about 20 databases,
> look good,
> good, the disk drives
> (ballpark) before it
> with a similar
> of how fare I can
> and similar
> tmp, but that just
database design, overall size of databases in GB etc. A
database which is not bulky (for example more than 50gb)
in size, where most tables have a pk, and pre-defined
queries fetch one or few records at a time based on a
unique where condition, you could have few hundreds
simulaneious connections. Whereas in a data warehouse
application where you have really huge tables, users are
allowed to create and run queries as they like, and each
query ususally reads through millions of records, few
simulatneious users can saturate the system, and sometime
even one user can dominate the whole system.
Based on the information you have given, your db server
falls more into the first category, 150 or more
simultaneous users could stress the system. If possible,
you should run a stress test to see when the cpu hits 90%
or more utilization, that will be the saturation point.
i hope this answers your question to some extent. Let us
know if you have further questions.
>--Original Message--
>We have a 4 processor (Xeon 700mhz), 3GB, SQL Server 2000
Standard Edition,
>Win2K Standard, with 3 RAID Array's. Currently running
about 20 databases,
>75 concurrent connections. Performance monitor readings
look good,
>processor rarely goes above 35 percent, memory looks
good, the disk drives
>spike but are usually not too busy.
>My question is how much more can I load on this thing
(ballpark) before it
>starts to get even medium stress. I'm looking for anyone
with a similar
>configuration, with much bigger numbers to get some idea
of how fare I can
>go with this machine. I have looked on www.tpc.org site
and similar
>configurations list 67,000 concurrent users and 87,000
tmp, but that just
>doesn't seem real.
>Thanks for any info.
>Steven Berringer
>
>.
>Thanks for the feedback. I guess I was hoping to hear from someone who had
a similar configuration and had X number of users connected and running at
the same time. I understand the OLTP versus OLAP and good database design,
and all that, but 150 is a far cry from the 67,000 listed on the tpm web
site for a 4 processor box.
Does anyone have any real world stories?
Thanks
Steven
<anonymous@.discussions.microsoft.com> wrote in message
news:1401701c3f7c3$8b5961c0$a501280a@.phx
.gbl...
> It depends on kind of db applications you are running,
> database design, overall size of databases in GB etc. A
> database which is not bulky (for example more than 50gb)
> in size, where most tables have a pk, and pre-defined
> queries fetch one or few records at a time based on a
> unique where condition, you could have few hundreds
> simulaneious connections. Whereas in a data warehouse
> application where you have really huge tables, users are
> allowed to create and run queries as they like, and each
> query ususally reads through millions of records, few
> simulatneious users can saturate the system, and sometime
> even one user can dominate the whole system.
> Based on the information you have given, your db server
> falls more into the first category, 150 or more
> simultaneous users could stress the system. If possible,
> you should run a stress test to see when the cpu hits 90%
> or more utilization, that will be the saturation point.
> i hope this answers your question to some extent. Let us
> know if you have further questions.
>
>
> Standard Edition,
> about 20 databases,
> look good,
> good, the disk drives
> (ballpark) before it
> with a similar
> of how fare I can
> and similar
> tmp, but that just
How much memory is safe to reserve for SQL?
I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
Gb of RAM. One of the databases is taking 1GB of space and it has 8
connections running at all times. I want to limit the amount of memory
that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
server. How much memory is advise to let SQL use in this case? 50%, 60%
of the total memory of the server?Hi,
If the server is dedicated for SQL Server then I will go with dynamic memory
allocation. If you have any other application running in the same server
apart from SQL Server then probably limit the SQL Server memort by 1 GB or
so...
Thanks
Hari
SQL Server MVP
"WR" <wilsonrey@.gmail.com> wrote in message
news:1156132604.617900.25730@.h48g2000cwc.googlegroups.com...
>I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> connections running at all times. I want to limit the amount of memory
> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> server. How much memory is advise to let SQL use in this case? 50%, 60%
> of the total memory of the server?
>|||Thank you for your advise. The server actually runs a point of sale
system and some customize software too. My concern is that the memory
usage is always high, generally running at 70 of the memory. I read
that SQL is not very good releasing memory after a service runs, and
that it will only release it when a programa needs it. I don't want to
wait until Windows sends a low memory warning for SQL release the
memory.
If you recommend 1 GB, then my next question is: Can the SQL server
service be reprogram to restart one a day in the middle of the day? so,
it will release the memory that is hugging?
WR wrote:
> I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> connections running at all times. I want to limit the amount of memory
> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> server. How much memory is advise to let SQL use in this case? 50%, 60%
> of the total memory of the server?|||Hi,
Why do you want an outage in the middle of the day. Let SQL Server takes 1
GB RAM and use it for its own purpose.
The rest of the memory will be used for operating system and other
applications.You do not require a service restart.
Incase if you are experiancing slow performance; try monitoring the using
the memory related counters
mentioned in below URL.
[url]http://www.sql-server-performance.com/performance_monitor_counters_sql_server.asp[
/url]
Thanks
Hari
SQL Server MVP
"WR" <wilsonrey@.gmail.com> wrote in message
news:1156167157.496825.260490@.h48g2000cwc.googlegroups.com...
> Thank you for your advise. The server actually runs a point of sale
> system and some customize software too. My concern is that the memory
> usage is always high, generally running at 70 of the memory. I read
> that SQL is not very good releasing memory after a service runs, and
> that it will only release it when a programa needs it. I don't want to
> wait until Windows sends a low memory warning for SQL release the
> memory.
> If you recommend 1 GB, then my next question is: Can the SQL server
> service be reprogram to restart one a day in the middle of the day? so,
> it will release the memory that is hugging?
>
> WR wrote:
>|||Hello,
Thank you again for your information. I gets I was having too much
cafeine that day before I sent the email. What I meant to say what to
restart SQL once a day in the middle of the night.
Any way, I will follow your advise to your advise and monitor the
memory, still I would like to be able to not to have SQL taking all
that memory at all times. (I know, I am hard head) ;-)
Hari Prasad wrote:[vbcol=seagreen]
> Hi,
> Why do you want an outage in the middle of the day. Let SQL Server takes 1
> GB RAM and use it for its own purpose.
> The rest of the memory will be used for operating system and other
> applications.You do not require a service restart.
> Incase if you are experiancing slow performance; try monitoring the using
> the memory related counters
> mentioned in below URL.
> http://www.sql-server-performance.c...ver.as
p
>
> Thanks
> Hari
> SQL Server MVP
>
>
> "WR" <wilsonrey@.gmail.com> wrote in message
> news:1156167157.496825.260490@.h48g2000cwc.googlegroups.com...sql
Gb of RAM. One of the databases is taking 1GB of space and it has 8
connections running at all times. I want to limit the amount of memory
that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
server. How much memory is advise to let SQL use in this case? 50%, 60%
of the total memory of the server?Hi,
If the server is dedicated for SQL Server then I will go with dynamic memory
allocation. If you have any other application running in the same server
apart from SQL Server then probably limit the SQL Server memort by 1 GB or
so...
Thanks
Hari
SQL Server MVP
"WR" <wilsonrey@.gmail.com> wrote in message
news:1156132604.617900.25730@.h48g2000cwc.googlegroups.com...
>I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> connections running at all times. I want to limit the amount of memory
> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> server. How much memory is advise to let SQL use in this case? 50%, 60%
> of the total memory of the server?
>|||Thank you for your advise. The server actually runs a point of sale
system and some customize software too. My concern is that the memory
usage is always high, generally running at 70 of the memory. I read
that SQL is not very good releasing memory after a service runs, and
that it will only release it when a programa needs it. I don't want to
wait until Windows sends a low memory warning for SQL release the
memory.
If you recommend 1 GB, then my next question is: Can the SQL server
service be reprogram to restart one a day in the middle of the day? so,
it will release the memory that is hugging?
WR wrote:
> I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> connections running at all times. I want to limit the amount of memory
> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> server. How much memory is advise to let SQL use in this case? 50%, 60%
> of the total memory of the server?|||Hi,
Why do you want an outage in the middle of the day. Let SQL Server takes 1
GB RAM and use it for its own purpose.
The rest of the memory will be used for operating system and other
applications.You do not require a service restart.
Incase if you are experiancing slow performance; try monitoring the using
the memory related counters
mentioned in below URL.
[url]http://www.sql-server-performance.com/performance_monitor_counters_sql_server.asp[
/url]
Thanks
Hari
SQL Server MVP
"WR" <wilsonrey@.gmail.com> wrote in message
news:1156167157.496825.260490@.h48g2000cwc.googlegroups.com...
> Thank you for your advise. The server actually runs a point of sale
> system and some customize software too. My concern is that the memory
> usage is always high, generally running at 70 of the memory. I read
> that SQL is not very good releasing memory after a service runs, and
> that it will only release it when a programa needs it. I don't want to
> wait until Windows sends a low memory warning for SQL release the
> memory.
> If you recommend 1 GB, then my next question is: Can the SQL server
> service be reprogram to restart one a day in the middle of the day? so,
> it will release the memory that is hugging?
>
> WR wrote:
>|||Hello,
Thank you again for your information. I gets I was having too much
cafeine that day before I sent the email. What I meant to say what to
restart SQL once a day in the middle of the night.
Any way, I will follow your advise to your advise and monitor the
memory, still I would like to be able to not to have SQL taking all
that memory at all times. (I know, I am hard head) ;-)
Hari Prasad wrote:[vbcol=seagreen]
> Hi,
> Why do you want an outage in the middle of the day. Let SQL Server takes 1
> GB RAM and use it for its own purpose.
> The rest of the memory will be used for operating system and other
> applications.You do not require a service restart.
> Incase if you are experiancing slow performance; try monitoring the using
> the memory related counters
> mentioned in below URL.
> http://www.sql-server-performance.c...ver.as
p
>
> Thanks
> Hari
> SQL Server MVP
>
>
> "WR" <wilsonrey@.gmail.com> wrote in message
> news:1156167157.496825.260490@.h48g2000cwc.googlegroups.com...sql
How much memory is safe to reserve for SQL?
I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
Gb of RAM. One of the databases is taking 1GB of space and it has 8
connections running at all times. I want to limit the amount of memory
that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
server. How much memory is advise to let SQL use in this case? 50%, 60%
of the total memory of the server?Hi,
If the server is dedicated for SQL Server then I will go with dynamic memory
allocation. If you have any other application running in the same server
apart from SQL Server then probably limit the SQL Server memort by 1 GB or
so...
Thanks
Hari
SQL Server MVP
"WR" <wilsonrey@.gmail.com> wrote in message
news:1156132604.617900.25730@.h48g2000cwc.googlegroups.com...
>I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> connections running at all times. I want to limit the amount of memory
> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> server. How much memory is advise to let SQL use in this case? 50%, 60%
> of the total memory of the server?
>|||Thank you for your advise. The server actually runs a point of sale
system and some customize software too. My concern is that the memory
usage is always high, generally running at 70 of the memory. I read
that SQL is not very good releasing memory after a service runs, and
that it will only release it when a programa needs it. I don't want to
wait until Windows sends a low memory warning for SQL release the
memory.
If you recommend 1 GB, then my next question is: Can the SQL server
service be reprogram to restart one a day in the middle of the day? so,
it will release the memory that is hugging?
WR wrote:
> I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> connections running at all times. I want to limit the amount of memory
> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> server. How much memory is advise to let SQL use in this case? 50%, 60%
> of the total memory of the server?|||Hi,
Why do you want an outage in the middle of the day. Let SQL Server takes 1
GB RAM and use it for its own purpose.
The rest of the memory will be used for operating system and other
applications.You do not require a service restart.
Incase if you are experiancing slow performance; try monitoring the using
the memory related counters
mentioned in below URL.
http://www.sql-server-performance.com/performance_monitor_counters_sql_server.asp
Thanks
Hari
SQL Server MVP
"WR" <wilsonrey@.gmail.com> wrote in message
news:1156167157.496825.260490@.h48g2000cwc.googlegroups.com...
> Thank you for your advise. The server actually runs a point of sale
> system and some customize software too. My concern is that the memory
> usage is always high, generally running at 70 of the memory. I read
> that SQL is not very good releasing memory after a service runs, and
> that it will only release it when a programa needs it. I don't want to
> wait until Windows sends a low memory warning for SQL release the
> memory.
> If you recommend 1 GB, then my next question is: Can the SQL server
> service be reprogram to restart one a day in the middle of the day? so,
> it will release the memory that is hugging?
>
> WR wrote:
>> I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
>> Gb of RAM. One of the databases is taking 1GB of space and it has 8
>> connections running at all times. I want to limit the amount of memory
>> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
>> server. How much memory is advise to let SQL use in this case? 50%, 60%
>> of the total memory of the server?
>|||Hello,
Thank you again for your information. I gets I was having too much
cafeine that day before I sent the email. What I meant to say what to
restart SQL once a day in the middle of the night.
Any way, I will follow your advise to your advise and monitor the
memory, still I would like to be able to not to have SQL taking all
that memory at all times. (I know, I am hard head) ;-)
Hari Prasad wrote:
> Hi,
> Why do you want an outage in the middle of the day. Let SQL Server takes 1
> GB RAM and use it for its own purpose.
> The rest of the memory will be used for operating system and other
> applications.You do not require a service restart.
> Incase if you are experiancing slow performance; try monitoring the using
> the memory related counters
> mentioned in below URL.
> http://www.sql-server-performance.com/performance_monitor_counters_sql_server.asp
>
> Thanks
> Hari
> SQL Server MVP
>
>
> "WR" <wilsonrey@.gmail.com> wrote in message
> news:1156167157.496825.260490@.h48g2000cwc.googlegroups.com...
> > Thank you for your advise. The server actually runs a point of sale
> > system and some customize software too. My concern is that the memory
> > usage is always high, generally running at 70 of the memory. I read
> > that SQL is not very good releasing memory after a service runs, and
> > that it will only release it when a programa needs it. I don't want to
> > wait until Windows sends a low memory warning for SQL release the
> > memory.
> > If you recommend 1 GB, then my next question is: Can the SQL server
> > service be reprogram to restart one a day in the middle of the day? so,
> > it will release the memory that is hugging?
> >
> >
> > WR wrote:
> >> I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> >> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> >> connections running at all times. I want to limit the amount of memory
> >> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> >> server. How much memory is advise to let SQL use in this case? 50%, 60%
> >> of the total memory of the server?
> >
Gb of RAM. One of the databases is taking 1GB of space and it has 8
connections running at all times. I want to limit the amount of memory
that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
server. How much memory is advise to let SQL use in this case? 50%, 60%
of the total memory of the server?Hi,
If the server is dedicated for SQL Server then I will go with dynamic memory
allocation. If you have any other application running in the same server
apart from SQL Server then probably limit the SQL Server memort by 1 GB or
so...
Thanks
Hari
SQL Server MVP
"WR" <wilsonrey@.gmail.com> wrote in message
news:1156132604.617900.25730@.h48g2000cwc.googlegroups.com...
>I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> connections running at all times. I want to limit the amount of memory
> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> server. How much memory is advise to let SQL use in this case? 50%, 60%
> of the total memory of the server?
>|||Thank you for your advise. The server actually runs a point of sale
system and some customize software too. My concern is that the memory
usage is always high, generally running at 70 of the memory. I read
that SQL is not very good releasing memory after a service runs, and
that it will only release it when a programa needs it. I don't want to
wait until Windows sends a low memory warning for SQL release the
memory.
If you recommend 1 GB, then my next question is: Can the SQL server
service be reprogram to restart one a day in the middle of the day? so,
it will release the memory that is hugging?
WR wrote:
> I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> connections running at all times. I want to limit the amount of memory
> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> server. How much memory is advise to let SQL use in this case? 50%, 60%
> of the total memory of the server?|||Hi,
Why do you want an outage in the middle of the day. Let SQL Server takes 1
GB RAM and use it for its own purpose.
The rest of the memory will be used for operating system and other
applications.You do not require a service restart.
Incase if you are experiancing slow performance; try monitoring the using
the memory related counters
mentioned in below URL.
http://www.sql-server-performance.com/performance_monitor_counters_sql_server.asp
Thanks
Hari
SQL Server MVP
"WR" <wilsonrey@.gmail.com> wrote in message
news:1156167157.496825.260490@.h48g2000cwc.googlegroups.com...
> Thank you for your advise. The server actually runs a point of sale
> system and some customize software too. My concern is that the memory
> usage is always high, generally running at 70 of the memory. I read
> that SQL is not very good releasing memory after a service runs, and
> that it will only release it when a programa needs it. I don't want to
> wait until Windows sends a low memory warning for SQL release the
> memory.
> If you recommend 1 GB, then my next question is: Can the SQL server
> service be reprogram to restart one a day in the middle of the day? so,
> it will release the memory that is hugging?
>
> WR wrote:
>> I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
>> Gb of RAM. One of the databases is taking 1GB of space and it has 8
>> connections running at all times. I want to limit the amount of memory
>> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
>> server. How much memory is advise to let SQL use in this case? 50%, 60%
>> of the total memory of the server?
>|||Hello,
Thank you again for your information. I gets I was having too much
cafeine that day before I sent the email. What I meant to say what to
restart SQL once a day in the middle of the night.
Any way, I will follow your advise to your advise and monitor the
memory, still I would like to be able to not to have SQL taking all
that memory at all times. (I know, I am hard head) ;-)
Hari Prasad wrote:
> Hi,
> Why do you want an outage in the middle of the day. Let SQL Server takes 1
> GB RAM and use it for its own purpose.
> The rest of the memory will be used for operating system and other
> applications.You do not require a service restart.
> Incase if you are experiancing slow performance; try monitoring the using
> the memory related counters
> mentioned in below URL.
> http://www.sql-server-performance.com/performance_monitor_counters_sql_server.asp
>
> Thanks
> Hari
> SQL Server MVP
>
>
> "WR" <wilsonrey@.gmail.com> wrote in message
> news:1156167157.496825.260490@.h48g2000cwc.googlegroups.com...
> > Thank you for your advise. The server actually runs a point of sale
> > system and some customize software too. My concern is that the memory
> > usage is always high, generally running at 70 of the memory. I read
> > that SQL is not very good releasing memory after a service runs, and
> > that it will only release it when a programa needs it. I don't want to
> > wait until Windows sends a low memory warning for SQL release the
> > memory.
> > If you recommend 1 GB, then my next question is: Can the SQL server
> > service be reprogram to restart one a day in the middle of the day? so,
> > it will release the memory that is hugging?
> >
> >
> > WR wrote:
> >> I am running SQL 2000 in a Windows Server 2000. The server only has 1.5
> >> Gb of RAM. One of the databases is taking 1GB of space and it has 8
> >> connections running at all times. I want to limit the amount of memory
> >> that SQL uses, beucase SQLSVR.EXE is taking 1+ Gb of the memory of the
> >> server. How much memory is advise to let SQL use in this case? 50%, 60%
> >> of the total memory of the server?
> >
Friday, March 23, 2012
How migrate msdb database from SQL 7.0 to SQL 2K
Since by detaching and attaching user databases from SQL 7.0 to SQL 2K, it can be migrated but how to migrate msdb database from 7.0 to 2K since above process will not work? Any suggestion are acceptable..
Thanks!Take a Full Backup Of MSDB database and restore it. That's the simplest way.
For more Info: See BOL .
Hope this Helps .
-Varad|||The model and msdb databases can only be restored from backups created on a Microsoft SQL Server 2000 server. Restore of backups of these databases made on SQL Server version 7.0 or earlier is not supported.|||Then how can one upgrade msdb database from 7.0 to 2000 if it has hundreds of DTS packages? Is there easier method of this migration..|||I think there is some difference between Upgrading the Server and Migrating the database from one server to another server.
Before migrating I think you have to apply the upgrade on Sql 7.0 and then use any migrating scheme.
May be this is of some help:
Upgrading Databases from SQL Server 7.0(bol)
Thanks!Take a Full Backup Of MSDB database and restore it. That's the simplest way.
For more Info: See BOL .
Hope this Helps .
-Varad|||The model and msdb databases can only be restored from backups created on a Microsoft SQL Server 2000 server. Restore of backups of these databases made on SQL Server version 7.0 or earlier is not supported.|||Then how can one upgrade msdb database from 7.0 to 2000 if it has hundreds of DTS packages? Is there easier method of this migration..|||I think there is some difference between Upgrading the Server and Migrating the database from one server to another server.
Before migrating I think you have to apply the upgrade on Sql 7.0 and then use any migrating scheme.
May be this is of some help:
Upgrading Databases from SQL Server 7.0(bol)
How MERGE few databases to big one
Hi All,
I have to merge few different databases to one big common database
I mean about structure (tables, procedures, users, roles etc.) and
data. May you suggest, help me how I should do this. How start? Create
brand new database or relay on one old and add difference from other?
Regards
Actually merging them is an option. The architecture should depend on other
factors such as how to maintain speed and integrity. If one of the tables in
another database is actually a subset of a table in the first database - for
example customers and customer address detail, you may get better results
moving it because you can use the database to create primary and foreign keys
and thus maintain the integrity with constraints. If on the other hand, you
don't need this, you can simply join the tables from each database to make
your query:
Example Select * from database1.dbo.table1 inner join database2.dbo.table2
on table1.id=table2.id. And finally, you should consider your server
hardware. Can you get better results if you spread your non-clustered
indexes over one raid, clustered on a second raid and log files on a third,
or do you have just two raids or only one - or will a clustered system work
because you have lots of hardware?
The question you ask should be more specific.
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hi All,
> I have to merge few different databases to one big common database
> I mean about structure (tables, procedures, users, roles etc.) and
> data. May you suggest, help me how I should do this. How start? Create
> brand new database or relay on one old and add difference from other?
> --
> Regards
>
|||Hello,
Thanks, I mean how marge database on the physical level (as dba) not
developer. I'd like move all object from old databases to new (tables,
procedures, users, roles...) and then sql developers can change
schema (key, constraints, references etc.)
Do you know which tool can help me with this process. I'm sure i will
have problem with procedures and hardcoded old database names like
select * from old_db
I have to change
select * from new_db
and so on.
How automate this task, I have a lot of procedures, views and manually
changing will be difficult.
Regards,
anxcomp
|||It will depend on what kind of databases you are importing but in general,
there is an import wizard built into SQL Server that allows you to bring over
tables and views... if the databases are not sql (.mdf extension).
Otherwise, if you have SQL, you should backup your database, detach it,
physically move the files (.mdf and .ldf and be careful, you may have some
..ndf associated as well - <filegroups>)... that is, physically move the files
to the new server and reattach them. Again, lots of right clicking here...
right click "database" in the solution explorer on the server and select
tasks... there are a bunch of them.
But I suspect you are moving database from sources other than sql.
Probably the best way to do this is to create an empty database on your
source server, right click the database (as above) when you make it and try
the import wizard out. If is fairly self-explanatory. It won't move
everything but will automate much of what you are trying to do.
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>
|||To be sure, here are some links
attach and detach http://msdn2.microsoft.com/en-us/library/ms189625.aspx
import wizard http://msdn2.microsoft.com/en-us/library/ms140052.aspx
import from excel http://support.microsoft.com/kb/321686
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>
I have to merge few different databases to one big common database
I mean about structure (tables, procedures, users, roles etc.) and
data. May you suggest, help me how I should do this. How start? Create
brand new database or relay on one old and add difference from other?
Regards
Actually merging them is an option. The architecture should depend on other
factors such as how to maintain speed and integrity. If one of the tables in
another database is actually a subset of a table in the first database - for
example customers and customer address detail, you may get better results
moving it because you can use the database to create primary and foreign keys
and thus maintain the integrity with constraints. If on the other hand, you
don't need this, you can simply join the tables from each database to make
your query:
Example Select * from database1.dbo.table1 inner join database2.dbo.table2
on table1.id=table2.id. And finally, you should consider your server
hardware. Can you get better results if you spread your non-clustered
indexes over one raid, clustered on a second raid and log files on a third,
or do you have just two raids or only one - or will a clustered system work
because you have lots of hardware?
The question you ask should be more specific.
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hi All,
> I have to merge few different databases to one big common database
> I mean about structure (tables, procedures, users, roles etc.) and
> data. May you suggest, help me how I should do this. How start? Create
> brand new database or relay on one old and add difference from other?
> --
> Regards
>
|||Hello,
Thanks, I mean how marge database on the physical level (as dba) not
developer. I'd like move all object from old databases to new (tables,
procedures, users, roles...) and then sql developers can change
schema (key, constraints, references etc.)
Do you know which tool can help me with this process. I'm sure i will
have problem with procedures and hardcoded old database names like
select * from old_db
I have to change
select * from new_db
and so on.
How automate this task, I have a lot of procedures, views and manually
changing will be difficult.
Regards,
anxcomp
|||It will depend on what kind of databases you are importing but in general,
there is an import wizard built into SQL Server that allows you to bring over
tables and views... if the databases are not sql (.mdf extension).
Otherwise, if you have SQL, you should backup your database, detach it,
physically move the files (.mdf and .ldf and be careful, you may have some
..ndf associated as well - <filegroups>)... that is, physically move the files
to the new server and reattach them. Again, lots of right clicking here...
right click "database" in the solution explorer on the server and select
tasks... there are a bunch of them.
But I suspect you are moving database from sources other than sql.
Probably the best way to do this is to create an empty database on your
source server, right click the database (as above) when you make it and try
the import wizard out. If is fairly self-explanatory. It won't move
everything but will automate much of what you are trying to do.
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>
|||To be sure, here are some links
attach and detach http://msdn2.microsoft.com/en-us/library/ms189625.aspx
import wizard http://msdn2.microsoft.com/en-us/library/ms140052.aspx
import from excel http://support.microsoft.com/kb/321686
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>
How MERGE few databases to big one
Hi All,
I have to merge few different databases to one big common database :)
I mean about structure (tables, procedures, users, roles etc.) and
data. May you suggest, help me how I should do this. How start? Create
brand new database or relay on one old and add difference from other?
--
RegardsActually merging them is an option. The architecture should depend on other
factors such as how to maintain speed and integrity. If one of the tables in
another database is actually a subset of a table in the first database - for
example customers and customer address detail, you may get better results
moving it because you can use the database to create primary and foreign keys
and thus maintain the integrity with constraints. If on the other hand, you
don't need this, you can simply join the tables from each database to make
your query:
Example Select * from database1.dbo.table1 inner join database2.dbo.table2
on table1.id=table2.id. And finally, you should consider your server
hardware. Can you get better results if you spread your non-clustered
indexes over one raid, clustered on a second raid and log files on a third,
or do you have just two raids or only one - or will a clustered system work
because you have lots of hardware?
The question you ask should be more specific.
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hi All,
> I have to merge few different databases to one big common database :)
> I mean about structure (tables, procedures, users, roles etc.) and
> data. May you suggest, help me how I should do this. How start? Create
> brand new database or relay on one old and add difference from other?
> --
> Regards
>|||Hello,
Thanks, I mean how marge database on the physical level (as dba) not
developer. I'd like move all object from old databases to new (tables,
procedures, users, roles...) and then sql developers can change
schema (key, constraints, references etc.)
Do you know which tool can help me with this process. I'm sure i will
have problem with procedures and hardcoded old database names like
select * from old_db
I have to change
select * from new_db
and so on.
How automate this task, I have a lot of procedures, views and manually
changing will be difficult.
--
Regards,
anxcomp|||It will depend on what kind of databases you are importing but in general,
there is an import wizard built into SQL Server that allows you to bring over
tables and views... if the databases are not sql (.mdf extension).
Otherwise, if you have SQL, you should backup your database, detach it,
physically move the files (.mdf and .ldf and be careful, you may have some
.ndf associated as well - <filegroups>)... that is, physically move the files
to the new server and reattach them. Again, lots of right clicking here...
right click "database" in the solution explorer on the server and select
tasks... there are a bunch of them.
But I suspect you are moving database from sources other than sql.
Probably the best way to do this is to create an empty database on your
source server, right click the database (as above) when you make it and try
the import wizard out. If is fairly self-explanatory. It won't move
everything but will automate much of what you are trying to do.
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>|||To be sure, here are some links
attach and detach http://msdn2.microsoft.com/en-us/library/ms189625.aspx
import wizard http://msdn2.microsoft.com/en-us/library/ms140052.aspx
import from excel http://support.microsoft.com/kb/321686
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>sql
I have to merge few different databases to one big common database :)
I mean about structure (tables, procedures, users, roles etc.) and
data. May you suggest, help me how I should do this. How start? Create
brand new database or relay on one old and add difference from other?
--
RegardsActually merging them is an option. The architecture should depend on other
factors such as how to maintain speed and integrity. If one of the tables in
another database is actually a subset of a table in the first database - for
example customers and customer address detail, you may get better results
moving it because you can use the database to create primary and foreign keys
and thus maintain the integrity with constraints. If on the other hand, you
don't need this, you can simply join the tables from each database to make
your query:
Example Select * from database1.dbo.table1 inner join database2.dbo.table2
on table1.id=table2.id. And finally, you should consider your server
hardware. Can you get better results if you spread your non-clustered
indexes over one raid, clustered on a second raid and log files on a third,
or do you have just two raids or only one - or will a clustered system work
because you have lots of hardware?
The question you ask should be more specific.
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hi All,
> I have to merge few different databases to one big common database :)
> I mean about structure (tables, procedures, users, roles etc.) and
> data. May you suggest, help me how I should do this. How start? Create
> brand new database or relay on one old and add difference from other?
> --
> Regards
>|||Hello,
Thanks, I mean how marge database on the physical level (as dba) not
developer. I'd like move all object from old databases to new (tables,
procedures, users, roles...) and then sql developers can change
schema (key, constraints, references etc.)
Do you know which tool can help me with this process. I'm sure i will
have problem with procedures and hardcoded old database names like
select * from old_db
I have to change
select * from new_db
and so on.
How automate this task, I have a lot of procedures, views and manually
changing will be difficult.
--
Regards,
anxcomp|||It will depend on what kind of databases you are importing but in general,
there is an import wizard built into SQL Server that allows you to bring over
tables and views... if the databases are not sql (.mdf extension).
Otherwise, if you have SQL, you should backup your database, detach it,
physically move the files (.mdf and .ldf and be careful, you may have some
.ndf associated as well - <filegroups>)... that is, physically move the files
to the new server and reattach them. Again, lots of right clicking here...
right click "database" in the solution explorer on the server and select
tasks... there are a bunch of them.
But I suspect you are moving database from sources other than sql.
Probably the best way to do this is to create an empty database on your
source server, right click the database (as above) when you make it and try
the import wizard out. If is fairly self-explanatory. It won't move
everything but will automate much of what you are trying to do.
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>|||To be sure, here are some links
attach and detach http://msdn2.microsoft.com/en-us/library/ms189625.aspx
import wizard http://msdn2.microsoft.com/en-us/library/ms140052.aspx
import from excel http://support.microsoft.com/kb/321686
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>sql
How MERGE few databases to big one
Hi All,
I have to merge few different databases to one big common database
I mean about structure (tables, procedures, users, roles etc.) and
data. May you suggest, help me how I should do this. How start? Create
brand new database or relay on one old and add difference from other?
RegardsActually merging them is an option. The architecture should depend on other
factors such as how to maintain speed and integrity. If one of the tables i
n
another database is actually a subset of a table in the first database - for
example customers and customer address detail, you may get better results
moving it because you can use the database to create primary and foreign key
s
and thus maintain the integrity with constraints. If on the other hand, you
don't need this, you can simply join the tables from each database to make
your query:
Example Select * from database1.dbo.table1 inner join database2.dbo.table2
on table1.id=table2.id. And finally, you should consider your server
hardware. Can you get better results if you spread your non-clustered
indexes over one raid, clustered on a second raid and log files on a third,
or do you have just two raids or only one - or will a clustered system work
because you have lots of hardware?
The question you ask should be more specific.
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hi All,
> I have to merge few different databases to one big common database
> I mean about structure (tables, procedures, users, roles etc.) and
> data. May you suggest, help me how I should do this. How start? Create
> brand new database or relay on one old and add difference from other?
> --
> Regards
>|||Hello,
Thanks, I mean how marge database on the physical level (as dba) not
developer. I'd like move all object from old databases to new (tables,
procedures, users, roles...) and then sql developers can change
schema (key, constraints, references etc.)
Do you know which tool can help me with this process. I'm sure i will
have problem with procedures and hardcoded old database names like
select * from old_db
I have to change
select * from new_db
and so on.
How automate this task, I have a lot of procedures, views and manually
changing will be difficult.
Regards,
anxcomp|||It will depend on what kind of databases you are importing but in general,
there is an import wizard built into SQL Server that allows you to bring ove
r
tables and views... if the databases are not sql (.mdf extension).
Otherwise, if you have SQL, you should backup your database, detach it,
physically move the files (.mdf and .ldf and be careful, you may have some
.ndf associated as well - <filegroups> )... that is, physically move the fil
es
to the new server and reattach them. Again, lots of right clicking here...
right click "database" in the solution explorer on the server and select
tasks... there are a bunch of them.
But I suspect you are moving database from sources other than sql.
Probably the best way to do this is to create an empty database on your
source server, right click the database (as above) when you make it and try
the import wizard out. If is fairly self-explanatory. It won't move
everything but will automate much of what you are trying to do.
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>|||To be sure, here are some links
attach and detach http://msdn2.microsoft.com/en-us/library/ms189625.aspx
import wizard http://msdn2.microsoft.com/en-us/library/ms140052.aspx
import from excel http://support.microsoft.com/kb/321686
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>
I have to merge few different databases to one big common database
I mean about structure (tables, procedures, users, roles etc.) and
data. May you suggest, help me how I should do this. How start? Create
brand new database or relay on one old and add difference from other?
RegardsActually merging them is an option. The architecture should depend on other
factors such as how to maintain speed and integrity. If one of the tables i
n
another database is actually a subset of a table in the first database - for
example customers and customer address detail, you may get better results
moving it because you can use the database to create primary and foreign key
s
and thus maintain the integrity with constraints. If on the other hand, you
don't need this, you can simply join the tables from each database to make
your query:
Example Select * from database1.dbo.table1 inner join database2.dbo.table2
on table1.id=table2.id. And finally, you should consider your server
hardware. Can you get better results if you spread your non-clustered
indexes over one raid, clustered on a second raid and log files on a third,
or do you have just two raids or only one - or will a clustered system work
because you have lots of hardware?
The question you ask should be more specific.
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hi All,
> I have to merge few different databases to one big common database
> I mean about structure (tables, procedures, users, roles etc.) and
> data. May you suggest, help me how I should do this. How start? Create
> brand new database or relay on one old and add difference from other?
> --
> Regards
>|||Hello,
Thanks, I mean how marge database on the physical level (as dba) not
developer. I'd like move all object from old databases to new (tables,
procedures, users, roles...) and then sql developers can change
schema (key, constraints, references etc.)
Do you know which tool can help me with this process. I'm sure i will
have problem with procedures and hardcoded old database names like
select * from old_db
I have to change
select * from new_db
and so on.
How automate this task, I have a lot of procedures, views and manually
changing will be difficult.
Regards,
anxcomp|||It will depend on what kind of databases you are importing but in general,
there is an import wizard built into SQL Server that allows you to bring ove
r
tables and views... if the databases are not sql (.mdf extension).
Otherwise, if you have SQL, you should backup your database, detach it,
physically move the files (.mdf and .ldf and be careful, you may have some
.ndf associated as well - <filegroups> )... that is, physically move the fil
es
to the new server and reattach them. Again, lots of right clicking here...
right click "database" in the solution explorer on the server and select
tasks... there are a bunch of them.
But I suspect you are moving database from sources other than sql.
Probably the best way to do this is to create an empty database on your
source server, right click the database (as above) when you make it and try
the import wizard out. If is fairly self-explanatory. It won't move
everything but will automate much of what you are trying to do.
--
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>|||To be sure, here are some links
attach and detach http://msdn2.microsoft.com/en-us/library/ms189625.aspx
import wizard http://msdn2.microsoft.com/en-us/library/ms140052.aspx
import from excel http://support.microsoft.com/kb/321686
Regards,
Jamie
"anxcomp@.gmail.com" wrote:
> Hello,
> Thanks, I mean how marge database on the physical level (as dba) not
> developer. I'd like move all object from old databases to new (tables,
> procedures, users, roles...) and then sql developers can change
> schema (key, constraints, references etc.)
> Do you know which tool can help me with this process. I'm sure i will
> have problem with procedures and hardcoded old database names like
> select * from old_db
> I have to change
> select * from new_db
> and so on.
> How automate this task, I have a lot of procedures, views and manually
> changing will be difficult.
> --
> Regards,
> anxcomp
>
Wednesday, March 21, 2012
How many pages in a table?
Hello, everyone:
How to calculate or estimate the pages or a table? I always heard someone said their databases have many pages increase one day. What does it mean?
Thanks
ZYTwhat does "page" mean? i have heard of databases, tablespaces, and tables, but not pages
can you give more information?|||Look at sp_spaceused
It converts pages to KB.
Just take that part out and you should have what you asked for|||R937: Pages are part of the physical implementation of Microsoft SQL Server (and also of Sybase). While this isn't absolutely correct, you can think of pages as the database engine's "atomic unit" of storage.
Yitongzhang: Calculating the pages used by a table is a slippery kind of thing because it gets pretty far down into how the SQL engine stores data. There are several kinds of pages, some used for data, some for indicies, some for blobs (TEXT and IMAGE columns), and some for log space. Until you really understand how these pages are used, it doesn't make much sense to just count them directly...
Using the sp_spaceused procedure gives you a commonly accepted way to measure table size. You could also study Inside SQL Server (http://www.amazon.com/Inside-Microsoft-Server-2000-CD-ROM/dp/0735609985/ref=pd_bbs_sr_3/104-8575354-0303117?ie=UTF8&s=books&qid=1182263258&sr=1-3) for more details on how tables are stored, and what pages are important for your own purposes and measurements.
-PatP|||thanks, pat, that does sort of ring a bell now
(by the way, and i realize this is really minor, but the handle is r937, not R937, thanks)|||thanks, pat, that does sort of ring a bell now
(by the way, and i realize this is really minor, but the handle is r937, not R937, thanks)
sql server is not case sensitive by default.sql
How to calculate or estimate the pages or a table? I always heard someone said their databases have many pages increase one day. What does it mean?
Thanks
ZYTwhat does "page" mean? i have heard of databases, tablespaces, and tables, but not pages
can you give more information?|||Look at sp_spaceused
It converts pages to KB.
Just take that part out and you should have what you asked for|||R937: Pages are part of the physical implementation of Microsoft SQL Server (and also of Sybase). While this isn't absolutely correct, you can think of pages as the database engine's "atomic unit" of storage.
Yitongzhang: Calculating the pages used by a table is a slippery kind of thing because it gets pretty far down into how the SQL engine stores data. There are several kinds of pages, some used for data, some for indicies, some for blobs (TEXT and IMAGE columns), and some for log space. Until you really understand how these pages are used, it doesn't make much sense to just count them directly...
Using the sp_spaceused procedure gives you a commonly accepted way to measure table size. You could also study Inside SQL Server (http://www.amazon.com/Inside-Microsoft-Server-2000-CD-ROM/dp/0735609985/ref=pd_bbs_sr_3/104-8575354-0303117?ie=UTF8&s=books&qid=1182263258&sr=1-3) for more details on how tables are stored, and what pages are important for your own purposes and measurements.
-PatP|||thanks, pat, that does sort of ring a bell now
(by the way, and i realize this is really minor, but the handle is r937, not R937, thanks)|||thanks, pat, that does sort of ring a bell now
(by the way, and i realize this is really minor, but the handle is r937, not R937, thanks)
sql server is not case sensitive by default.sql
Monday, March 19, 2012
How many databases/codebases?
Hi,
I have a question about SQL Server 2005.
Suppose we have a hospitals application where the patients records and all other records are the stored. The solution is a hosting one. Here are three options:
- We have one single database for all institutions (Hospitals) then we need to keep an ID for every institution say institution ID. If we need to rollback the transactions for one institution how can we do that while not rolling back for others? Also, every institution may have slightly different business rules i.e. 80% of the rules and data is same for every institution where as 20% business rules and data may be specific to the institution e.g. if institution is located in Canada instead of US. What I meant to say, every instituion has some data this is not in the base database but we need to add this data specifically for this institution to the base database (i.e. 80% common part) What is the best way / recommendataion to resolve these issues? Another example could be taxes, i.e. tax system in Canada, US and EU is very much different. Can we handle it in the same code base?
- The 2nd option is that we have a separate database for every institution. This will give rise to maintenace issues e.g. if a bug is fixed for one customer then the same bugfix has to be fixed for every customer, say 4000 customers. Then it will be very difficult to maintain the code base.
- The third option could be that the base database is same for every institution and in addition to base database there is one additional database for every institution which has the 20% rules/data that vary. But this option may run into problems if the rule/data is implemented in base database already has rules for this type of transactions, there will be a conflict and we need to manage feature list for every customer and first see if you execute in the base database, if not then use the institution specific database. Again this will raise maintenence issues.
What is industry practice or recommendation and why? Is there any material on the web or on the microsoft web site that gives guidance on these / similar issues.
Your cooperation will be appreciated.
Thanks,
Paraclete
http://msdn2.microsoft.com/en-us/library/ms151198.aspx
http://www.databaseanswers.org/data_models/index.htm
How many databases can i have in sql server 2000?
Hi, my name's Carlos and i have a question...
I need to know if there is a limit in the number of databases that i an have
in sql server 2000 and if there is a difference in sql server 2005.
Thanks.
Carlos,
See:
2000
http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
2005
Same I believe.
HTH
Jerry
"Carlos Lpez." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.
|||32767 DB's per instance
http://sqlservercode.blogspot.com/
"Carlos López." wrote:
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.
|||Hi,
SQL 2000 :- 32767 Databases per SQL Server Instance.
SQL 2005:- 32767 databases per instance.
Thanks
Hari
SQL Server MVP
"Carlos Lpez." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.
|||Thaks a lot.
Your help was very fast & exactly.
Thnks.
"Hari Prasad" wrote:
> Hi,
> SQL 2000 :- 32767 Databases per SQL Server Instance.
> SQL 2005:- 32767 databases per instance.
> Thanks
> Hari
> SQL Server MVP
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
>
>
|||Thaks a lot.
Your help was very fast & exactly.
:-)
"Jerry Spivey" wrote:
> Carlos,
> See:
> 2000
> http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
> 2005
> Same I believe.
> HTH
> Jerry
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
>
>
|||Thaks a lot.
Your help was very fast. :-)
"SQL" wrote:
[vbcol=seagreen]
> 32767 DB's per instance
> http://sqlservercode.blogspot.com/
>
> "Carlos López." wrote:
I need to know if there is a limit in the number of databases that i an have
in sql server 2000 and if there is a difference in sql server 2005.
Thanks.
Carlos,
See:
2000
http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
2005
Same I believe.
HTH
Jerry
"Carlos Lpez." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.
|||32767 DB's per instance
http://sqlservercode.blogspot.com/
"Carlos López." wrote:
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.
|||Hi,
SQL 2000 :- 32767 Databases per SQL Server Instance.
SQL 2005:- 32767 databases per instance.
Thanks
Hari
SQL Server MVP
"Carlos Lpez." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.
|||Thaks a lot.
Your help was very fast & exactly.
Thnks.
"Hari Prasad" wrote:
> Hi,
> SQL 2000 :- 32767 Databases per SQL Server Instance.
> SQL 2005:- 32767 databases per instance.
> Thanks
> Hari
> SQL Server MVP
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
>
>
|||Thaks a lot.
Your help was very fast & exactly.
:-)
"Jerry Spivey" wrote:
> Carlos,
> See:
> 2000
> http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
> 2005
> Same I believe.
> HTH
> Jerry
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
>
>
|||Thaks a lot.
Your help was very fast. :-)
"SQL" wrote:
[vbcol=seagreen]
> 32767 DB's per instance
> http://sqlservercode.blogspot.com/
>
> "Carlos López." wrote:
How many databases can i have in sql server 2000?
Hi, my name's Carlos and i have a question...
I need to know if there is a limit in the number of databases that i an have
in sql server 2000 and if there is a difference in sql server 2005.
Thanks.Carlos,
See:
2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
2005
Same I believe.
HTH
Jerry
"Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||32767 DB's per instance
http://sqlservercode.blogspot.com/
"Carlos López." wrote:
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||Hi,
SQL 2000 :- 32767 Databases per SQL Server Instance.
SQL 2005:- 32767 databases per instance.
Thanks
Hari
SQL Server MVP
"Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||Thaks a lot.
Your help was very fast & exactly.
Thnks.
"Hari Prasad" wrote:
> Hi,
> SQL 2000 :- 32767 Databases per SQL Server Instance.
> SQL 2005:- 32767 databases per instance.
> Thanks
> Hari
> SQL Server MVP
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> > Hi, my name's Carlos and i have a question...
> > I need to know if there is a limit in the number of databases that i an
> > have
> > in sql server 2000 and if there is a difference in sql server 2005.
> >
> > Thanks.
>
>|||Thaks a lot.
Your help was very fast & exactly.
:-)
"Jerry Spivey" wrote:
> Carlos,
> See:
> 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
> 2005
> Same I believe.
> HTH
> Jerry
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> > Hi, my name's Carlos and i have a question...
> > I need to know if there is a limit in the number of databases that i an
> > have
> > in sql server 2000 and if there is a difference in sql server 2005.
> >
> > Thanks.
>
>|||Thaks a lot.
Your help was very fast. :-)
"SQL" wrote:
> 32767 DB's per instance
> http://sqlservercode.blogspot.com/
>
> "Carlos López." wrote:
> > Hi, my name's Carlos and i have a question...
> > I need to know if there is a limit in the number of databases that i an have
> > in sql server 2000 and if there is a difference in sql server 2005.
> >
> > Thanks.
I need to know if there is a limit in the number of databases that i an have
in sql server 2000 and if there is a difference in sql server 2005.
Thanks.Carlos,
See:
2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
2005
Same I believe.
HTH
Jerry
"Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||32767 DB's per instance
http://sqlservercode.blogspot.com/
"Carlos López." wrote:
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||Hi,
SQL 2000 :- 32767 Databases per SQL Server Instance.
SQL 2005:- 32767 databases per instance.
Thanks
Hari
SQL Server MVP
"Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||Thaks a lot.
Your help was very fast & exactly.
Thnks.
"Hari Prasad" wrote:
> Hi,
> SQL 2000 :- 32767 Databases per SQL Server Instance.
> SQL 2005:- 32767 databases per instance.
> Thanks
> Hari
> SQL Server MVP
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> > Hi, my name's Carlos and i have a question...
> > I need to know if there is a limit in the number of databases that i an
> > have
> > in sql server 2000 and if there is a difference in sql server 2005.
> >
> > Thanks.
>
>|||Thaks a lot.
Your help was very fast & exactly.
:-)
"Jerry Spivey" wrote:
> Carlos,
> See:
> 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
> 2005
> Same I believe.
> HTH
> Jerry
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> > Hi, my name's Carlos and i have a question...
> > I need to know if there is a limit in the number of databases that i an
> > have
> > in sql server 2000 and if there is a difference in sql server 2005.
> >
> > Thanks.
>
>|||Thaks a lot.
Your help was very fast. :-)
"SQL" wrote:
> 32767 DB's per instance
> http://sqlservercode.blogspot.com/
>
> "Carlos López." wrote:
> > Hi, my name's Carlos and i have a question...
> > I need to know if there is a limit in the number of databases that i an have
> > in sql server 2000 and if there is a difference in sql server 2005.
> >
> > Thanks.
How many databases can i have in sql server 2000?
Hi, my name's Carlos and i have a question...
I need to know if there is a limit in the number of databases that i an have
in sql server 2000 and if there is a difference in sql server 2005.
Thanks.Carlos,
See:
2000
http://msdn.microsoft.com/library/d...br />
8dbn.asp
2005
Same I believe.
HTH
Jerry
"Carlos Lpez." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||32767 DB's per instance
http://sqlservercode.blogspot.com/
"Carlos López." wrote:
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an ha
ve
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||Hi,
SQL 2000 :- 32767 Databases per SQL Server Instance.
SQL 2005:- 32767 databases per instance.
Thanks
Hari
SQL Server MVP
"Carlos Lpez." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||Thaks a lot.
Your help was very fast & exactly.
Thnks.
"Hari Prasad" wrote:
> Hi,
> SQL 2000 :- 32767 Databases per SQL Server Instance.
> SQL 2005:- 32767 databases per instance.
> Thanks
> Hari
> SQL Server MVP
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
>
>|||Thaks a lot.
Your help was very fast & exactly.
:-)
"Jerry Spivey" wrote:
> Carlos,
> See:
> 2000
> http://msdn.microsoft.com/library/d... />
s_8dbn.asp
> 2005
> Same I believe.
> HTH
> Jerry
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
>
>|||Thaks a lot.
Your help was very fast. :-)
"SQL" wrote:
[vbcol=seagreen]
> 32767 DB's per instance
> http://sqlservercode.blogspot.com/
>
> "Carlos López." wrote:
>
I need to know if there is a limit in the number of databases that i an have
in sql server 2000 and if there is a difference in sql server 2005.
Thanks.Carlos,
See:
2000
http://msdn.microsoft.com/library/d...br />
8dbn.asp
2005
Same I believe.
HTH
Jerry
"Carlos Lpez." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||32767 DB's per instance
http://sqlservercode.blogspot.com/
"Carlos López." wrote:
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an ha
ve
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||Hi,
SQL 2000 :- 32767 Databases per SQL Server Instance.
SQL 2005:- 32767 databases per instance.
Thanks
Hari
SQL Server MVP
"Carlos Lpez." <CarlosLpez@.discussions.microsoft.com> wrote in message
news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
> Hi, my name's Carlos and i have a question...
> I need to know if there is a limit in the number of databases that i an
> have
> in sql server 2000 and if there is a difference in sql server 2005.
> Thanks.|||Thaks a lot.
Your help was very fast & exactly.
Thnks.
"Hari Prasad" wrote:
> Hi,
> SQL 2000 :- 32767 Databases per SQL Server Instance.
> SQL 2005:- 32767 databases per instance.
> Thanks
> Hari
> SQL Server MVP
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
>
>|||Thaks a lot.
Your help was very fast & exactly.
:-)
"Jerry Spivey" wrote:
> Carlos,
> See:
> 2000
> http://msdn.microsoft.com/library/d... />
s_8dbn.asp
> 2005
> Same I believe.
> HTH
> Jerry
> "Carlos López." <CarlosLpez@.discussions.microsoft.com> wrote in message
> news:E789E737-642C-4E63-B65F-03BF02806662@.microsoft.com...
>
>|||Thaks a lot.
Your help was very fast. :-)
"SQL" wrote:
[vbcol=seagreen]
> 32767 DB's per instance
> http://sqlservercode.blogspot.com/
>
> "Carlos López." wrote:
>
how many databases can be set up in one Sql server instance
I am using sqlserver to its limitation ,So I am concerning how many
databases can be created in one Sql server instance. Anyboday know
this issue ? I am grateful for your answer>I am using sqlserver to its limitation, So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue? I am grateful for your answer
Databases per instance of SQL Server: 32,767
SQL Server 2005 Books Online > Maximum Capacity Specifications:
http://msdn2.microsoft.com/en-us/library/ms143432.aspx
Tom
http://kbupdate.info/ | http://suppline.com/|||I have a client with 6287 databases on a pretty small box and it works fine.
Note that most third party tools roll over and die when you try them against
such a server.
TheSQLGuru
President
Indicium Resources, Inc.
"csonnet" <haiming.chen@.gmail.com> wrote in message
news:1182844134.925881.299380@.o11g2000prd.googlegroups.com...
>I am using sqlserver to its limitation ,So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue ? I am grateful for your answer
>
databases can be created in one Sql server instance. Anyboday know
this issue ? I am grateful for your answer>I am using sqlserver to its limitation, So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue? I am grateful for your answer
Databases per instance of SQL Server: 32,767
SQL Server 2005 Books Online > Maximum Capacity Specifications:
http://msdn2.microsoft.com/en-us/library/ms143432.aspx
Tom
http://kbupdate.info/ | http://suppline.com/|||I have a client with 6287 databases on a pretty small box and it works fine.
Note that most third party tools roll over and die when you try them against
such a server.
TheSQLGuru
President
Indicium Resources, Inc.
"csonnet" <haiming.chen@.gmail.com> wrote in message
news:1182844134.925881.299380@.o11g2000prd.googlegroups.com...
>I am using sqlserver to its limitation ,So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue ? I am grateful for your answer
>
Labels:
anyboday,
concerning,
created,
database,
databases,
instance,
knowthis,
limitation,
manydatabases,
microsoft,
mysql,
oracle,
server,
sql,
sqlserver
how many databases can be set up in one Sql server instance
I am using sqlserver to its limitation ,So I am concerning how many
databases can be created in one Sql server instance. Anyboday know
this issue ? I am grateful for your answer
>I am using sqlserver to its limitation, So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue? I am grateful for your answer
Databases per instance of SQL Server: 32,767
SQL Server 2005 Books Online > Maximum Capacity Specifications:
http://msdn2.microsoft.com/en-us/library/ms143432.aspx
Tom
http://kbupdate.info/ | http://suppline.com/
|||I have a client with 6287 databases on a pretty small box and it works fine.
Note that most third party tools roll over and die when you try them against
such a server.
TheSQLGuru
President
Indicium Resources, Inc.
"csonnet" <haiming.chen@.gmail.com> wrote in message
news:1182844134.925881.299380@.o11g2000prd.googlegr oups.com...
>I am using sqlserver to its limitation ,So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue ? I am grateful for your answer
>
databases can be created in one Sql server instance. Anyboday know
this issue ? I am grateful for your answer
>I am using sqlserver to its limitation, So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue? I am grateful for your answer
Databases per instance of SQL Server: 32,767
SQL Server 2005 Books Online > Maximum Capacity Specifications:
http://msdn2.microsoft.com/en-us/library/ms143432.aspx
Tom
http://kbupdate.info/ | http://suppline.com/
|||I have a client with 6287 databases on a pretty small box and it works fine.
Note that most third party tools roll over and die when you try them against
such a server.
TheSQLGuru
President
Indicium Resources, Inc.
"csonnet" <haiming.chen@.gmail.com> wrote in message
news:1182844134.925881.299380@.o11g2000prd.googlegr oups.com...
>I am using sqlserver to its limitation ,So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue ? I am grateful for your answer
>
Labels:
anyboday,
concerning,
created,
database,
databases,
instance,
knowthis,
limitation,
manydatabases,
microsoft,
mysql,
oracle,
server,
sql,
sqlserver
how many databases can be set up in one Sql server instance
I am using sqlserver to its limitation ,So I am concerning how many
databases can be created in one Sql server instance. Anyboday know
this issue ? I am grateful for your answer>I am using sqlserver to its limitation, So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue? I am grateful for your answer
Databases per instance of SQL Server: 32,767
SQL Server 2005 Books Online > Maximum Capacity Specifications:
http://msdn2.microsoft.com/en-us/library/ms143432.aspx
--
Tom
http://kbupdate.info/ | http://suppline.com/|||I have a client with 6287 databases on a pretty small box and it works fine.
Note that most third party tools roll over and die when you try them against
such a server.
--
TheSQLGuru
President
Indicium Resources, Inc.
"csonnet" <haiming.chen@.gmail.com> wrote in message
news:1182844134.925881.299380@.o11g2000prd.googlegroups.com...
>I am using sqlserver to its limitation ,So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue ? I am grateful for your answer
>
databases can be created in one Sql server instance. Anyboday know
this issue ? I am grateful for your answer>I am using sqlserver to its limitation, So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue? I am grateful for your answer
Databases per instance of SQL Server: 32,767
SQL Server 2005 Books Online > Maximum Capacity Specifications:
http://msdn2.microsoft.com/en-us/library/ms143432.aspx
--
Tom
http://kbupdate.info/ | http://suppline.com/|||I have a client with 6287 databases on a pretty small box and it works fine.
Note that most third party tools roll over and die when you try them against
such a server.
--
TheSQLGuru
President
Indicium Resources, Inc.
"csonnet" <haiming.chen@.gmail.com> wrote in message
news:1182844134.925881.299380@.o11g2000prd.googlegroups.com...
>I am using sqlserver to its limitation ,So I am concerning how many
> databases can be created in one Sql server instance. Anyboday know
> this issue ? I am grateful for your answer
>
Monday, March 12, 2012
How long register the Databases without access?
Hi Friends...
I want to know if exist a possibility to check who was the last user in
acceding some databases, and how time passed after it.
I need to know this, because i have more than 100 databases on a clustered
server and i supposed that more than 20 are unused.
Thanks all!
Hi
Not possible unless you switch on extensive auditing like C2 in SQL Server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
news:15369103-F255-402F-A148-FEA183AEA2D3@.microsoft.com...
> Hi Friends...
>
> I want to know if exist a possibility to check who was the last user in
> acceding some databases, and how time passed after it.
> I need to know this, because i have more than 100 databases on a clustered
> server and i supposed that more than 20 are unused.
> Thanks all!
>
I want to know if exist a possibility to check who was the last user in
acceding some databases, and how time passed after it.
I need to know this, because i have more than 100 databases on a clustered
server and i supposed that more than 20 are unused.
Thanks all!
Hi
Not possible unless you switch on extensive auditing like C2 in SQL Server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
news:15369103-F255-402F-A148-FEA183AEA2D3@.microsoft.com...
> Hi Friends...
>
> I want to know if exist a possibility to check who was the last user in
> acceding some databases, and how time passed after it.
> I need to know this, because i have more than 100 databases on a clustered
> server and i supposed that more than 20 are unused.
> Thanks all!
>
How long register the Databases without access?
Hi Friends...
I want to know if exist a possibility to check who was the last user in
acceding some databases, and how time passed after it.
I need to know this, because i have more than 100 databases on a clustered
server and i supposed that more than 20 are unused.
Thanks all!Hi
Not possible unless you switch on extensive auditing like C2 in SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
news:15369103-F255-402F-A148-FEA183AEA2D3@.microsoft.com...
> Hi Friends...
>
> I want to know if exist a possibility to check who was the last user in
> acceding some databases, and how time passed after it.
> I need to know this, because i have more than 100 databases on a clustered
> server and i supposed that more than 20 are unused.
> Thanks all!
>
I want to know if exist a possibility to check who was the last user in
acceding some databases, and how time passed after it.
I need to know this, because i have more than 100 databases on a clustered
server and i supposed that more than 20 are unused.
Thanks all!Hi
Not possible unless you switch on extensive auditing like C2 in SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
news:15369103-F255-402F-A148-FEA183AEA2D3@.microsoft.com...
> Hi Friends...
>
> I want to know if exist a possibility to check who was the last user in
> acceding some databases, and how time passed after it.
> I need to know this, because i have more than 100 databases on a clustered
> server and i supposed that more than 20 are unused.
> Thanks all!
>
How long register the Databases without access?
Hi Friends...
I want to know if exist a possibility to check who was the last user in
acceding some databases, and how time passed after it.
I need to know this, because i have more than 100 databases on a clustered
server and i supposed that more than 20 are unused.
Thanks all!Hi
Not possible unless you switch on extensive auditing like C2 in SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
news:15369103-F255-402F-A148-FEA183AEA2D3@.microsoft.com...
> Hi Friends...
>
> I want to know if exist a possibility to check who was the last user in
> acceding some databases, and how time passed after it.
> I need to know this, because i have more than 100 databases on a clustered
> server and i supposed that more than 20 are unused.
> Thanks all!
>
I want to know if exist a possibility to check who was the last user in
acceding some databases, and how time passed after it.
I need to know this, because i have more than 100 databases on a clustered
server and i supposed that more than 20 are unused.
Thanks all!Hi
Not possible unless you switch on extensive auditing like C2 in SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
news:15369103-F255-402F-A148-FEA183AEA2D3@.microsoft.com...
> Hi Friends...
>
> I want to know if exist a possibility to check who was the last user in
> acceding some databases, and how time passed after it.
> I need to know this, because i have more than 100 databases on a clustered
> server and i supposed that more than 20 are unused.
> Thanks all!
>
Wednesday, March 7, 2012
How is 4GB Max Database size applied?
Is the 4GB Database size calculated by totalling up the size of all the databases in an instance OR against each individual DB in an instance (e.g. you can have an unlimited number of DB each up to 4GB in size)?
TIA
Antony
TIA
Antony
Hi Antony,
It is calculated based on individual databases and includes only user data. You can have as many 4 GB database as your HD allows and as is reasonable maintainable within the other Express limits of 1 CPU and 1 GB of memory.
Mike
|||Whats is the size of the other version of sql 2005
Subscribe to:
Posts (Atom)