Multable database on one machine

Total newbie question i know.
The company i just started working for has SQL 2000 installed on four
machines. Is there any info i can get about putting all database on one
machine, Then having an application server running the apps (Great Plains
7.5, Sharepoint, track-it, and a custom made database)
Thanks
LeeYes, you can have multiple databases on the same machine, and on the same
instance of SQL Server. Your limitations are: (a) two databases can't have
the same name, or expect their data/log files to have the same path, and (b)
the available resources on the server. If it's a low-powered box it may
perform acceptably hosting one application's database
As for the right way to perform the consolidation, if you are comfortable
that it is the right move, there are several options. Andrew Kelly has
posted this list of KB articles that should help you out:
http://tinyurl.com/up5ok
"Lee J" <faked@.fc.com> wrote in message
news:ejg6to$5ap@.dispatch.concentric.net...
> Total newbie question i know.
> The company i just started working for has SQL 2000 installed on four
> machines. Is there any info i can get about putting all database on one
> machine, Then having an application server running the apps (Great Plains
> 7.5, Sharepoint, track-it, and a custom made database)
> Thanks
> Lee
>|||Great, Thank you, I am looking to be buying some new blade servers
"Aaron Bertrand [MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:u7yEr9QCHHA.5064@.TK2MSFTNGP02.phx.gbl...
> Yes, you can have multiple databases on the same machine, and on the same
> instance of SQL Server. Your limitations are: (a) two databases can't
> have the same name, or expect their data/log files to have the same path,
> and (b) the available resources on the server. If it's a low-powered box
> it may perform acceptably hosting one application's database
> As for the right way to perform the consolidation, if you are comfortable
> that it is the right move, there are several options. Andrew Kelly has
> posted this list of KB articles that should help you out:
> http://tinyurl.com/up5ok
>
> "Lee J" <faked@.fc.com> wrote in message
> news:ejg6to$5ap@.dispatch.concentric.net...
>> Total newbie question i know.
>> The company i just started working for has SQL 2000 installed on four
>> machines. Is there any info i can get about putting all database on one
>> machine, Then having an application server running the apps (Great Plains
>> 7.5, Sharepoint, track-it, and a custom made database)
>> Thanks
>> Lee
>|||Wow, I don't think I've come across anyone successfully running SQL Server
on a blade, but hey, all the best.
Actually I'm sitting with Geoff at PASS and he said that, unfortunately, he
has seen this, and it didn't work out too well. But again, all the best.
If it works out, please let us know. :-)
"Lee J" <faked@.fc.com> wrote in message
news:ejg8fo$5s5@.dispatch.concentric.net...
> Great, Thank you, I am looking to be buying some new blade servers
>
> "Aaron Bertrand [MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:u7yEr9QCHHA.5064@.TK2MSFTNGP02.phx.gbl...
>> Yes, you can have multiple databases on the same machine, and on the same
>> instance of SQL Server. Your limitations are: (a) two databases can't
>> have the same name, or expect their data/log files to have the same path,
>> and (b) the available resources on the server. If it's a low-powered box
>> it may perform acceptably hosting one application's database
>> As for the right way to perform the consolidation, if you are comfortable
>> that it is the right move, there are several options. Andrew Kelly has
>> posted this list of KB articles that should help you out:
>> http://tinyurl.com/up5ok
>>
>> "Lee J" <faked@.fc.com> wrote in message
>> news:ejg6to$5ap@.dispatch.concentric.net...
>> Total newbie question i know.
>> The company i just started working for has SQL 2000 installed on four
>> machines. Is there any info i can get about putting all database on one
>> machine, Then having an application server running the apps (Great
>> Plains 7.5, Sharepoint, track-it, and a custom made database)
>> Thanks
>> Lee
>>
>|||well, thats good to know, i am just in the discovery stage.
what kind of specs do you recommed?
My most heavly used database is on a dual 1GHz intel with 2GB of RAM. The
blades i was looking at were dual 1.8 xeons with 2GB.
this kind has landed on my lap
"Aaron Bertrand [MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OQi6PFRCHHA.4908@.TK2MSFTNGP03.phx.gbl...
> Wow, I don't think I've come across anyone successfully running SQL Server
> on a blade, but hey, all the best.
> Actually I'm sitting with Geoff at PASS and he said that, unfortunately,
> he has seen this, and it didn't work out too well. But again, all the
> best. If it works out, please let us know. :-)
>
>
> "Lee J" <faked@.fc.com> wrote in message
> news:ejg8fo$5s5@.dispatch.concentric.net...
>> Great, Thank you, I am looking to be buying some new blade servers
>>
>> "Aaron Bertrand [MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>> news:u7yEr9QCHHA.5064@.TK2MSFTNGP02.phx.gbl...
>> Yes, you can have multiple databases on the same machine, and on the
>> same instance of SQL Server. Your limitations are: (a) two databases
>> can't have the same name, or expect their data/log files to have the
>> same path, and (b) the available resources on the server. If it's a
>> low-powered box it may perform acceptably hosting one application's
>> database
>> As for the right way to perform the consolidation, if you are
>> comfortable that it is the right move, there are several options.
>> Andrew Kelly has posted this list of KB articles that should help you
>> out:
>> http://tinyurl.com/up5ok
>>
>> "Lee J" <faked@.fc.com> wrote in message
>> news:ejg6to$5ap@.dispatch.concentric.net...
>> Total newbie question i know.
>> The company i just started working for has SQL 2000 installed on four
>> machines. Is there any info i can get about putting all database on one
>> machine, Then having an application server running the apps (Great
>> Plains 7.5, Sharepoint, track-it, and a custom made database)
>> Thanks
>> Lee
>>
>>
>

Mulitiple DBs

Folk
I have multiple SQL SERVERs over 15 Servers. I have couple of test machines. I don't want to go to every machine and add evry single registration of every servers in mmc. that just way too much work. can i import an mmc console from one machine to another
if yes , how can i do it
Thank
GirishI exported registry keys under
HKEY_CURRENT_USER\Software\Microsoft\MSSQLServer\SQLEW\Registered
Servers X
when I did it last time on MSSQL7
Bart Simpson
Last time
On Tue, 2 Mar 2004 08:36:07 -0800, Girish
<anonymous@.discussions.microsoft.com> wrote:
>Folks
>I have multiple SQL SERVERs over 15 Servers. I have couple of test machines. I don't want to go to every machine and add evry single registration of every servers in mmc. that just way too much work. can i import an mmc console from one machine to another ?
>if yes , how can i do it ?
>Thanks
>Girish

Mulitiple DBs

Folks
I have multiple SQL SERVERs over 15 Servers. I have couple of test machines.
I don't want to go to every machine and add evry single registration of eve
ry servers in mmc. that just way too much work. can i import an mmc console
from one machine to another
?
if yes , how can i do it ?
Thanks
GirishI exported registry keys under
HKEY_CURRENT_USER\Software\Microsoft\MSS
QLServer\SQLEW\Registered
Servers X
when I did it last time on MSSQL7
Bart Simpson
Last time
On Tue, 2 Mar 2004 08:36:07 -0800, Girish
<anonymous@.discussions.microsoft.com> wrote:

>Folks
>I have multiple SQL SERVERs over 15 Servers. I have couple of test machines. I don'
t want to go to every machine and add evry single registration of every servers in m
mc. that just way too much work. can i import an mmc console from one machine to ano
the
r ?
>if yes , how can i do it ?
>Thanks
>Girish

MSSQL7 and WinXP

Hi!
We're closer to a solution to our problem with slow machines on a MSDE
database (two weeks ago).
We now have one standalone machine that runs MSSQL7, SP4 (SP4 was
installed after it did not work without it).
The computer has been freshly set up with WinXPPro, MSSQL7 and our
application. All current Windowsupdates applied afterwards.
OK, what we have now:
1) Extremely quick resutls when using osql
2) Extremely slow startup time of our application. (Delphi, using ADO as
connection)
The reason for 2) is (or rather one effect of it) can be seen in the error
log:
--8<--
2004-06-17 15:14:19.43 spid5 Startet Datenbank 'Patient'.
2004-06-17 15:14:19.43 spid5 Opening file C:\MSSQL7\data\Patient.mdf.
2004-06-17 15:14:19.43 spid5 Opening file
C:\MSSQL7\data\Patient_log.LDF.
2004-06-17 15:14:20.01 spid14 Closing file C:\MSSQL7\data\Stammdaten.mdf.
2004-06-17 15:14:20.01 spid14 Closing file
C:\MSSQL7\data\Stammdaten_log.LDF.
--8<--
Sections like this one are repeated *quite* often, read: immediately
afterwards. Several times. For approx.10 seconds per database. (which
makes about 10-20 retries).
We then noticed that this machine has hyperthreading enabled, which we
disabled. The entries in the log file were reduced to a more sensible
amount, still it happens more often than on other machines with our
software and MSSQL7 or MSDE.
Question: What else can we do? Is there something with respect to
hyperthreading that can still interfere? Have others also seen multiple
repeating entries in the log files and have a clue as to where they come
from?
Thanks for reading,
Stefan
See the BOL for information concerning the AUTO_CLOSE option. It appears to
me that you have that enabled (the default for MSDE) and the database server
is closing the database after all connected clients are disconnected.
Jim
"Stefan M. Huber" <looseleaf@.gmx.net> wrote in message
news:opr9qpvxj0s9ddfw@.news.individual.de...
> Hi!
> We're closer to a solution to our problem with slow machines on a MSDE
> database (two weeks ago).
> We now have one standalone machine that runs MSSQL7, SP4 (SP4 was
> installed after it did not work without it).
> The computer has been freshly set up with WinXPPro, MSSQL7 and our
> application. All current Windowsupdates applied afterwards.
> OK, what we have now:
> 1) Extremely quick resutls when using osql
> 2) Extremely slow startup time of our application. (Delphi, using ADO as
> connection)
> The reason for 2) is (or rather one effect of it) can be seen in the error
> log:
> --8<--
> 2004-06-17 15:14:19.43 spid5 Startet Datenbank 'Patient'.
> 2004-06-17 15:14:19.43 spid5 Opening file C:\MSSQL7\data\Patient.mdf.
> 2004-06-17 15:14:19.43 spid5 Opening file
> C:\MSSQL7\data\Patient_log.LDF.
> 2004-06-17 15:14:20.01 spid14 Closing file
C:\MSSQL7\data\Stammdaten.mdf.
> 2004-06-17 15:14:20.01 spid14 Closing file
> C:\MSSQL7\data\Stammdaten_log.LDF.
> --8<--
> Sections like this one are repeated *quite* often, read: immediately
> afterwards. Several times. For approx.10 seconds per database. (which
> makes about 10-20 retries).
> We then noticed that this machine has hyperthreading enabled, which we
> disabled. The entries in the log file were reduced to a more sensible
> amount, still it happens more often than on other machines with our
> software and MSSQL7 or MSDE.
> Question: What else can we do? Is there something with respect to
> hyperthreading that can still interfere? Have others also seen multiple
> repeating entries in the log files and have a clue as to where they come
> from?
> Thanks for reading,
> Stefan
>
|||On Fri, 18 Jun 2004 09:44:47 -0700, Jim Young <thorium48@.hotmail.com>
wrote:

> See the BOL for information concerning the AUTO_CLOSE option. It appears
> to me that you have that enabled (the default for MSDE) and the database
> server is closing the database after all connected clients are
> disconnected.
Thanks for the pointer. However, I wonder, why this happens when only one
single client wants to connect at startup. I'll check that next time I am
at work. Thanks.
Stefan
"Mobile launchers are more difficult to detect because they move
around, unlike fixed launchers."
-- Katie Couric, NBC News

MSSQL Server connectivity

Hi,

I have two Windows machines in the Local Area Network. One of the machines has MSSQL Enterprise Server 8.0 installed whereas the other has MSSQL Server 2005 installed. When I try to establish the connectivity between these two servers, I can not do so. When I try to look up Network servers, the two machines can't see each other. How can I make them talk to each other? Is there some type of driver or some such thing to be installed which can help the matter?

Please let me know.

Need a bit more information to help you:

Are the instances default or named?
Do you have any firewall software running on either server?
What is the error msg you're getting?
Can you use SQLCMD to connect to the remote server?

|||

Thanks for the response.

Answers to your questions:

1. The MSSQL Server instances are the default ones.

2. I don't think I have a firewall running on the servers.

3. When I go to SQL Server Management Studio and try to register the server by looking on the network, I can not find my other machine with Enterprise Manager 8.0. So I don't get any error, but I can not see the machine either.

4. Login failed for user 'xyz'.
HResult 0x2746, Level 16, State 1
TCP Provider: An existing connection was forcibly closed by the remote host.

Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.

This is the error that I see on the command prompt.

Here's what I suggest: You may want to go through my answers above, but I think I don't know much about this new SQL version? Can you quickly list a set of steps I can follow to connect from SQL Server 2005 to another machine having SQL Enterprise Manager 8.0 running on it? Thanks in advance.

|||

Enterprise Manager has nothing to do with remote connectivity. This is what I understand you're doing:

Machine 1: Running SQL Server 2000, default instance

Machine 2: Running SQL Server 2005, default instance

From Machine 2 running SQL Server Management Studio you want to connect to Machine 1.

First, make sure that Machine 1 is setup to accept remote connections. This is documented in Books Online for SQL Server 2000.

You'll want to make sure you're providing the correct credentials: Windows or SQL Server depending on how the instance is configured.

|||

Hi Dan,

Thanks for the response. However, we somehow managed to do the connectivity between the 2 servers. Apparently, the SQL user which we were using to establish the connectivity did not work initially. We dropped and recreated the user and then it went through fine. Don't know why it did not connect initially.

I have another problem though. And I would really appreciate if someone could help with this real quick.

So, there's this MSSQL 2005 installed on a new machine, which has 40 G on C Drive and 250+ G on a D Drive. But all of my C Drive has been taken up by "tempdb.mdf". It has taken up nearly 26 G of space on this drive. Why should that be the case? I know that this is a System database that gets created when one installs MSSQL Server, but I have never seen it this big. Is there a problem with the installation that I can fix? Please let me know.

Thanks.

|||This is certainly suspicious. I'm not expert on tempdb so I recommend you post this issue to http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1. Someone there will certainly be able to help you.

MSSQL Server connectivity

Hi,

I have two Windows machines in the Local Area Network. One of the machines has MSSQL Enterprise Server 8.0 installed whereas the other has MSSQL Server 2005 installed. When I try to establish the connectivity between these two servers, I can not do so. When I try to look up Network servers, the two machines can't see each other. How can I make them talk to each other? Is there some type of driver or some such thing to be installed which can help the matter?

Please let me know.

Need a bit more information to help you:

Are the instances default or named?
Do you have any firewall software running on either server?
What is the error msg you're getting?
Can you use SQLCMD to connect to the remote server?

|||

Thanks for the response.

Answers to your questions:

1. The MSSQL Server instances are the default ones.

2. I don't think I have a firewall running on the servers.

3. When I go to SQL Server Management Studio and try to register the server by looking on the network, I can not find my other machine with Enterprise Manager 8.0. So I don't get any error, but I can not see the machine either.

4. Login failed for user 'xyz'.
HResult 0x2746, Level 16, State 1
TCP Provider: An existing connection was forcibly closed by the remote host.

Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.

This is the error that I see on the command prompt.

Here's what I suggest: You may want to go through my answers above, but I think I don't know much about this new SQL version? Can you quickly list a set of steps I can follow to connect from SQL Server 2005 to another machine having SQL Enterprise Manager 8.0 running on it? Thanks in advance.

|||

Enterprise Manager has nothing to do with remote connectivity. This is what I understand you're doing:

Machine 1: Running SQL Server 2000, default instance

Machine 2: Running SQL Server 2005, default instance

From Machine 2 running SQL Server Management Studio you want to connect to Machine 1.

First, make sure that Machine 1 is setup to accept remote connections. This is documented in Books Online for SQL Server 2000.

You'll want to make sure you're providing the correct credentials: Windows or SQL Server depending on how the instance is configured.

|||

Hi Dan,

Thanks for the response. However, we somehow managed to do the connectivity between the 2 servers. Apparently, the SQL user which we were using to establish the connectivity did not work initially. We dropped and recreated the user and then it went through fine. Don't know why it did not connect initially.

I have another problem though. And I would really appreciate if someone could help with this real quick.

So, there's this MSSQL 2005 installed on a new machine, which has 40 G on C Drive and 250+ G on a D Drive. But all of my C Drive has been taken up by "tempdb.mdf". It has taken up nearly 26 G of space on this drive. Why should that be the case? I know that this is a System database that gets created when one installs MSSQL Server, but I have never seen it this big. Is there a problem with the installation that I can fix? Please let me know.

Thanks.

|||This is certainly suspicious. I'm not expert on tempdb so I recommend you post this issue to http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1. Someone there will certainly be able to help you.