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

On Wed, 23 May 2012 15:20:35 -0400, "eternal-september"
<JoeSulla (AT) roadrunner (DOT) com> wrote:

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

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.

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/

"eternal-september" <JoeSulla (AT) roadrunner (DOT) com> wrote

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

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.

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.

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.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

Erland Sommarskog wrote:

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.

Bob Barrows (reb01501 (AT) NOyahooSPAM (DOT) com) writes:
Yes, but there are things in SSMS that requires SSIS: Copy Databse Wizard,
Export/Import Wizard, Maintenance Plans.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

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

Bob Barrows (reb01501 (AT) NOSPAMyahoo (DOT) com) writes:
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.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

"Tony Toews" <ttoews (AT) telusplanet (DOT) net> wrote

Thanks

"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote

Thanks, I did as you said.