Install the default or named instance

[eternal-september]

I want to install sqlserver 2008.

Presently I'll only use it locally along with vs2010 for web development.

Some day I may look for a host to put it on the web but not for a while.

My questions are:

1): Should I install a default or named instance?

2) What is the advantage of each?

3) Got any other advice?

Thanks

[Tony Toews]

On Wed, 23 May 2012 15:20:35 -0400, "eternal-september"

Post by eternal-september
I want to install sqlserver 2008.
Presently I'll only use it locally along with vs2010 for web development.
Some day I may look for a host to put it on the web but not for a while.
1): Should I install a default or named instance?

I would think a named instance just in case you decide to install more
copies of SQL Server <version> <year> later.

Post by eternal-september
2) What is the advantage of each?

From what little I've seen you have to do a little extra work with the
connect string. Which wouldn't hurt you at all and would be a very
small learning experience.

Post by eternal-september
3) Got any other advice?

No because I don't have much real experience like Erland. If he
disagrees with me I'd be strongly tempted to go with his advice.
<smile>

Tony

[Joe Sulla]

Post by Tony Toews
On Wed, 23 May 2012 15:20:35 -0400, "eternal-september"

Post by eternal-september
I want to install sqlserver 2008.
Presently I'll only use it locally along with vs2010 for web development.
Some day I may look for a host to put it on the web but not for a while.
1): Should I install a default or named instance?

I would think a named instance just in case you decide to install more
copies of SQL Server <version> <year> later.

Post by eternal-september
2) What is the advantage of each?

From what little I've seen you have to do a little extra work with the
connect string. Which wouldn't hurt you at all and would be a very
small learning experience.

Post by eternal-september
3) Got any other advice?

No because I don't have much real experience like Erland. If he
disagrees with me I'd be strongly tempted to go with his advice.
<smile>
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

Thanks

[Joe Sulla]

"eternal-september" <***@roadrunner.com> wrote in message news:jpjda6$mvj$***@dont-email.me...
I want to install sqlserver 2008.

Presently I'll only use it locally along with vs2010 for web development.

Some day I may look for a host to put it on the web but not for a while.

My questions are:

1): Should I install a default or named instance?

2) What is the advantage of each?

3) Got any other advice?

I'm the original poster (fixed OE).

One more question:

4) What features should I select.
I don't know what many are for.
The database will be used to control login and store a picture gallery.
No more than that.
I don't want on my machine anything I do not require.
Do I need:
Business Intelligence Development Studio.
Client Tool Connectivity
Client tool backward compatability
Sql client connectivity SDK
Integeration servicesmicrosoft sync framework
Integration services

Thanks

[Erland Sommarskog]

Post by eternal-september
1): Should I install a default or named instance?

Go with the default. Which means that you get a default instance,
unless you install Express Edition, in which case you get a named
instance called SQLEXPRESS.

Post by eternal-september
2) What is the advantage of each?

The ability to have named instance exists to permit multiple instances
on a machine. The reason there are default instances are legacy -
named instances were introduced in SQL 2000.

Post by eternal-september
Business Intelligence Development Studio.
Client Tool Connectivity
Client tool backward compatability
Sql client connectivity SDK
Integeration servicesmicrosoft sync framework
Integration services

I would recommend that you select all but BIDS. To be honest I don't
know what "Client tool backward compatability" is, but it will not
fill up your disk.

You may think that you don't need Integration Services, but suddenly
you want to export or import data. Although I am completely illiterate
in SSIS, I always install it.

[Bob Barrows]

Post by Erland Sommarskog

Post by eternal-september
1): Should I install a default or named instance?

Go with the default. Which means that you get a default instance,
unless you install Express Edition, in which case you get a named
instance called SQLEXPRESS.

Post by eternal-september
2) What is the advantage of each?

The ability to have named instance exists to permit multiple instances
on a machine. The reason there are default instances are legacy -
named instances were introduced in SQL 2000.

Post by eternal-september
Business Intelligence Development Studio.

aka BIDS

Post by Erland Sommarskog
I would recommend that you select all but BIDS.
You may think that you don't need Integration Services, but suddenly
you want to export or import data. Although I am completely illiterate
in SSIS, I always install it.

BIDS is needed to create SSIS packages, so if you need SSIS, you probably
need BIDS, unless you plan to develop packages on a different machine.

[Erland Sommarskog]

Post by Bob Barrows
BIDS is needed to create SSIS packages, so if you need SSIS, you probably
need BIDS, unless you plan to develop packages on a different machine.

Yes, but there are things in SSMS that requires SSIS: Copy Databse Wizard,
Export/Import Wizard, Maintenance Plans.

[Bob Barrows]

Post by Erland Sommarskog

Post by Bob Barrows
BIDS is needed to create SSIS packages, so if you need SSIS, you
probably need BIDS, unless you plan to develop packages on a
different machine.

Yes, but there are things in SSMS that requires SSIS: Copy Databse
Wizard, Export/Import Wizard, Maintenance Plans.

Just to clarify: I was not disputing that he might need SSIS. My point was
that he might need BIDS in addition to SSIS.

[Erland Sommarskog]

Post by Bob Barrows

Post by Erland Sommarskog
Yes, but there are things in SSMS that requires SSIS: Copy Databse
Wizard, Export/Import Wizard, Maintenance Plans.

Just to clarify: I was not disputing that he might need SSIS. My point was
that he might need BIDS in addition to SSIS.

Yes, I understood that, but I pointed out that you can use SSIS without
knowning that you need SSIS. And without needing BIDS.

Of course at some point you might get intrigued and want to play with
SSIS packages for real. But it hasn't happened to me yet.

[Joe Sulla]

Post by Erland Sommarskog

Post by eternal-september
1): Should I install a default or named instance?

Go with the default. Which means that you get a default instance,
unless you install Express Edition, in which case you get a named
instance called SQLEXPRESS.

Post by eternal-september
2) What is the advantage of each?

The ability to have named instance exists to permit multiple instances
on a machine. The reason there are default instances are legacy -
named instances were introduced in SQL 2000.

Post by eternal-september
Business Intelligence Development Studio.
Client Tool Connectivity
Client tool backward compatability
Sql client connectivity SDK
Integeration servicesmicrosoft sync framework
Integration services

I would recommend that you select all but BIDS. To be honest I don't
know what "Client tool backward compatability" is, but it will not
fill up your disk.
You may think that you don't need Integration Services, but suddenly
you want to export or import data. Although I am completely illiterate
in SSIS, I always install it.
--
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

Thanks, I did as you said.