Instances in SQL Server 2005

Question

Instances in SQL Server 2005

S Hodkinson

SSCertifiable

Points: 7529
More actions
August 13, 2008 at 9:02 am

#192273

Can anyone point me towards an idiots guide to instances in SQL Server 2005? We are still using SQL Server 2000 and were hoping to bypass SQL Server 2005 and head straight to SQL Server 2008. We have just this one server with SQL Server 2005 which holds a development database; now another supplier wants to use another instance on this server.
Having had no training on 2005 ( I was hanging out for 2008) and not having migrated anything to either 2005 or 2008, I was wondering if there was a simple guide; I have to explain it to Management.
Madame Artois

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Lowell SSC Guru Points: 323518 More actions · Answer 1

from a development standpoint, multiple instances are great for testing; I've had SQL7 as a default instance, SQL2000 and 2005 as named instances, all on the same machine. helpful if you are testing and supporting different database systems.

However, I'd be hard pressed if a vendor told me they needed a separate INSTANCE for their application, as opposed to a separate database....each instance would be duplicating functionality and competing for the server resources, as opposed to simply using the existing service to access a database.

I cannot think of a single reason why an extra instance of 2005 would be helpful. I can think of lots of reasons it would degrade performance, though. Make them explain in detail why they want one, but i would just create a new database on the existing server for them.

you said you are still using 2000, but then said We have just this one server with SQL Server 2005 which holds a development database

does that imply that they want you to install a 2005 instance on a different 2000 machine, or on the same dev server that already has 2005?

Are they really using functionality that is available only in SQL2005, or are they just knee-jerking to use current technology?

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

S Hodkinson SSCertifiable Points: 7529 More actions · Answer 2

As far as I can understand they want to install another instance of 2005 on the server that has 2005, which is what I didn't understand. I'm not sure if they are trying to keep their application away from the dev database but not knowing enough about 2005 I wasn't sure of the architectural implications.

Would an additional instance on the same server have licence implications?

:sick:

Madame Artois

Shabba SSCertifiable Points: 5007 More actions · Answer 3

It seems to be quite common for a 3rd party to request 'their' own sql instance but in reality may not be practical to do so for various reasons. As Lowell has mentioned go back to the 3rd party and ask the question why? One would hope they would respond with justifications for?

There won't be any license implications but you may need to upgrade the hardware to accomodate a further instance.

see http://msdn.microsoft.com/en-us/library/ms143531(SQL.90).aspx for further info. A quick google search and you will find numerous info on instances both default & named.

Cheers,

Mark