Help - setup Sql Server 2000 on server on network

Hello -
I have a VB6 application that is hooked up to a Sql Server database on my
workstation computer. I will be distributing this application and have to
install Sql Server 2000 on a server. I have never set up Sql Server on a
network server before. Please tell me if the following steps are correct:
1. Set up Windows 2000 Server operating system on the machine (they want me
to use a separate computer from our other servers).
2. Connect to the network.
3. Install Sql Server 2000 on the machine.
4. Copy the MDF and LDF files from my workstation computer to Sql Server
2000 on the server into the ../MSSQL/Data file.
According to my logic (or lack thereof, as the case may be), my application
should be able to connect to this database from any computer in the
organization via a connection string (which is located in my application)
like the following:
"Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=MyDatabase;Data
Source=NewServerThatSqlServerWasJustInst
alledOn"
Any comments and suggestions will be greatly appreciated!
--
SandySandy,
It basically sounds like you're trying to move a SQL database from one
instance of SQL Server to another and then connect to that new instance via
your client application. That is not an issue as long as the client
application has the necessary connection information/string to the new
instance and the network connectivity is present. However, there may be
some issues with security as any logins will not be transfered because they
are stored in the Master system database and not in the end-user database
(only contains the db users). As such you may want to view the Microsoft KB
article #246133.
HTH
Jerry
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
> Hello -
> I have a VB6 application that is hooked up to a Sql Server database on my
> workstation computer. I will be distributing this application and have to
> install Sql Server 2000 on a server. I have never set up Sql Server on a
> network server before. Please tell me if the following steps are correct:
> 1. Set up Windows 2000 Server operating system on the machine (they want
> me
> to use a separate computer from our other servers).
> 2. Connect to the network.
> 3. Install Sql Server 2000 on the machine.
> 4. Copy the MDF and LDF files from my workstation computer to Sql Server
> 2000 on the server into the ../MSSQL/Data file.
> According to my logic (or lack thereof, as the case may be), my
> application
> should be able to connect to this database from any computer in the
> organization via a connection string (which is located in my application)
> like the following:
> "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> Info=False;Initial Catalog=MyDatabase;Data
> Source=NewServerThatSqlServerWasJustInst
alledOn"
> Any comments and suggestions will be greatly appreciated!
> --
> Sandy|||Hi Jerry -
Thanks for your response! You are correct; that's essentially what I want
to do. I just wanted to make sure I had my steps correct and that I wasn't
forgetting anything.
In looking at my "list" again, I did forget that I have to be sure to put
the log on a separate drive on the server.
Anything else I may have overlooked?
Thanks for bringing the security issue to my attention!
Sandy
"Jerry Spivey" wrote:

> Sandy,
> It basically sounds like you're trying to move a SQL database from one
> instance of SQL Server to another and then connect to that new instance vi
a
> your client application. That is not an issue as long as the client
> application has the necessary connection information/string to the new
> instance and the network connectivity is present. However, there may be
> some issues with security as any logins will not be transfered because the
y
> are stored in the Master system database and not in the end-user database
> (only contains the db users). As such you may want to view the Microsoft
KB
> article #246133.
> HTH
> Jerry
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
>
>