where do sql server components reside 1

[charlotte49er]

Please help me understand where SQL server can best be configured. Our sys admin guy has said that we are getting a database server along with a SAN. Will the "database server" run only the SQL server software while the actual database resides on the SAN? Is the database usually on the same machine as the software? As you can tell, I'm getting shoved into this so any help is greatly appreciated as to this is physically set up.

 

[mrdenny]

Here's how it basically works. A SAN is a huge, fast hard drive. It's connected to the physical server via fiber cables. The SQL Software it self will be installed on the server. By SQL Software I mean the binaries that make up the SQL Server, SQL Agent, etc. The only things that will be stored on the SAN is the database files that hold the data. The mdf and ldf files.

When a SAN is configured on a server it shows up on the server as a regular hard drive. From the DBA side of things you don't really care that it's a SAN, or a SCSI array, or an IDE drive etc. They all show up the same in My Computer, and SQL works with them all the same.

Does that answer your questions?

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[charlotte49er]

Yes, and it was in plain english. Thanks a lot. So now that I have that straight let me throw a couple of follow-up questions at you. So the engine, utilities, etc. for SQL Server will reside on the database server. How much space does this typically require? Secondly, would it be okay to (i.e., we don't have the money so we're trying to make do with what we've got) load an instance of SQL Server as a test environment for a production site and also run a separate instance for internal use on the same machine? Is there anything that raises a red flag with that approach? Thanks again.

 

[mrdenny]

The Tools them selves are fairly small. I usually install the OS and the SQL tools on a 8-10 Gig partation, which should leave a few gig left over. I'd say the install without the database files is a couple of hundred Megs tops.

There's no problem running a test instance and production instance on the same box. It's not the preferred config since if you have a long running query on the test instance it will effect production, but it can be (and often is) done.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[SQLBill]

Just remember to document what you are doing and to make sure you keep the test database for testing purposes only.

That way if you ever come under review for licensing issues, you will be able to show that one database is a test bed and you haven't violated the licenses by using it as production.

-SQLBill

Posting advice: FAQ481-4875

 

[charlotte49er]

We are going to have a separate db server that will reside in the DMZ and will be solely dedicated as a production database. We only have one other db machine so we are wanting it to pull double duty (serve as a test server for the aforementioned db server and as a production db server for our internal operations) unless there are some serious flaws in that thinking which it sounds like there aren't. Assuming we implement under this configuration, what we would end up with are SQL files (mdf & ldf) for three separate databases physically residing on the SAN while the SQL Server binaries run on the separate db servers. Have I got it about right?

 

[SQLBill]

Is the SAN connected to both servers? Usually a SAN is connected to one server only.

Pick one of your servers. Is the C drive on that server or another one? Of course it's on that server. A SAN drive is the same, but it's 'virtually' a part of the server.

Now you can have the SAN attached to the server in the DMZ and make a network connection to it for the other server, but SQL Server does not like using networked storage for it's data files. And what happens when the server with the SAN is offline?

-SQLBill

Posting advice: FAQ481-4875

 

[mrdenny]

You should be able to connect the SAN to more than one server. Anthough that depends on the SAN vendor. Products like EMC and HP Sans can have dozzens to hundreds of servers connected to them.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[charlotte49er]

Believe it or not I actually have a nice looking diagram! Thanks to both of you for all of your help.