Is using a named instance better over using a default instance?

If you were asked to install SQL 2005 on a machine, would u install a default instance or a named one? And why would u choose one over the other? Also, r there any issues with using a default instance?

Thank you for all your help.

Named instances allow for somewhat better server management -the names could reflect the SQL version. In an enviroment with lots of servers, various migration projects in play, and future upgrades, a simple way to know about the server is quite valuable.

For example:

Instance Name: LON_ACCT_Std05
Instance Name: NYC_HR_Ent05
Instance Name: DEN_INV_Exp05
Instance Name: LAX_ORD_Dev00

|||In addition, there is only one default instance on a machine. If you want to install multiple instances of SQL Server including 2000 and 2005, the rest should be named instances. Otherwise, setup will complain.|||

The other thing to think about is that the default instance name, MSSQLSERVER, is merely the defaul "named instance". No difference at all, but as pointed out, naming them allows you to describe them a bit.

Thanks,
Sam Lester (MSFT)

Is this an installation problem??

I am using the Server Installation strategy, the install is complete (I
think), I have deployed my reports but when I try to view any report I am
getting this error. I have already installed the Oracle Client software
(9.2), and the data source is deployed. Any else get this error before?
HELP!!
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'entpar1- SCARDBA'.
(rsErrorOpeningConnection) Get Online Help
System.Data.OracleClient requires Oracle client software version 8.1.7 or
greater.Did you get a solution? We're having the same problem since we've installed
the oracle db on the reporting services server.
Regards
Antoon
"OriginalStealth" wrote:
> I am using the Server Installation strategy, the install is complete (I
> think), I have deployed my reports but when I try to view any report I am
> getting this error. I have already installed the Oracle Client software
> (9.2), and the data source is deployed. Any else get this error before?
> HELP!!
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Cannot create a connection to data source 'entpar1- SCARDBA'.
> (rsErrorOpeningConnection) Get Online Help
> System.Data.OracleClient requires Oracle client software version 8.1.7 or
> greater.
>

Is there necessary remove named instance alias after...

Hi,
I was told by someone that after install clustering SQL Server 2000 named
instance, it must remove that before installation made the alias. Is that
necessary? What if I leave the alias named instance in the server?
Thanks!
-Chen
Hi Chen,
I hope I'm understanding your question correctly.
It seems that you have installed a SQL 2000 Named Instance on a Windows
2003 Cluster. This requires an alias using Named Pipes for setup to run
properly.
Your question appears to be, do you have to remove it?
Technically, no, you don't have to remove the alias. However, cluster, sql
agent, and other local applications will continue to connect to SQL using
Named Pipes. There isn't an issue with this, but if you have an
application that specifically needs to use TCP, you will want to remove the
alias, or at least change it to TCP.
Hope that helps!
Donna Lambert
Microsoft PSS
SQL Server Support

is there any way to get isqlw running under sql 2005 install

I regulary would have 4 or 5 separate sessions of isqlw running.. and it is much less overhead than running multiple sql server managment sessions and also much better in the way the windows tile... the new interface sucks in my opinion ..

thanks in advance

ok to answer my own question

get the following files off of an old 2000 install and put them somewhere in your path

I put them in the winnt directory

1/30/2006 10:38a 352,828 isqlw.exe
1/30/2006 10:38a 401,984 sqlqry.dll
1/30/2006 10:38a 279,104 pfutil80.dll
1/30/2006 10:39a 414,272 pfclnt80.dll
1/30/2006 11:11a <DIR> ..

now put the following file in the directory as shown also from an existing 2000 install

Directory of E:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033

10/14/2005 03:44a 16,088 PFCLNT90.rll
1 File(s) 16,088 bytes

(all should be ok as you are not replacing any files in 2005 these are all addition files pulled over from 2000)

now isqlw works on my machine...

if you want to get it working from external tools in the sql server managemtn window you also have to add the following rll's in

Directory of E:\WINNT\Resources\1033

01/30/2006 11:12a 28,672 pfclnt80.rll
01/30/2006 11:23a 147,456 pfutil80.rll
01/30/2006 11:23a 184,320 sqlqry.rll
01/30/2006 11:24a <DIR> ..
01/30/2006 11:24a <DIR> .
01/30/2006 11:24a 245,760 isqlw.rll
4 File(s) 606,208 bytes

still cannot figure out how to get it to pass the database and u/pw in so you don't have to enter those when launching isqlw from the sql server management studio there seems to be no option for thse parameters

Is there any requirement to install the client component of RS?

Hi all,
I only install the client component of reporting service,
at the beginning, when it is install the support file, it
always failed with only an 'error' message. No other
messages.
I check the log file. There is
Internet Information Services 5.0 (IIS) or later is either
not installed, or it is configured in a way that is
incompatible with a Reporting Services installation.
ASP.NET version 1.1 is not installed or is not registered
with your Web server. ASP.Net is required for the Report
Server and the Report Manager components.
and in the stlog file, I notice
<Prerequisite Name="IsIISInstalled" Checked="Metabase"
Item="/" Found="Can not open metabase" Expected="No error"
Result="Fail" />
To only install the client component, should I install IIS
and ASP1.1 and how do I check that every thing is OK to
install it.
Thanks.
Lindayou need Visual studio.Net 2003 and .Net framework 1.1
IIS is not required
"YUKON2005" <anonymous@.discussions.microsoft.com> a écrit dans le message de
news:38d201c471e9$c199d760$a501280a@.phx.gbl...
> Hi all,
> I only install the client component of reporting service,
> at the beginning, when it is install the support file, it
> always failed with only an 'error' message. No other
> messages.
> I check the log file. There is
> Internet Information Services 5.0 (IIS) or later is either
> not installed, or it is configured in a way that is
> incompatible with a Reporting Services installation.
> ASP.NET version 1.1 is not installed or is not registered
> with your Web server. ASP.Net is required for the Report
> Server and the Report Manager components.
> and in the stlog file, I notice
> <Prerequisite Name="IsIISInstalled" Checked="Metabase"
> Item="/" Found="Can not open metabase" Expected="No error"
> Result="Fail" />
> To only install the client component, should I install IIS
> and ASP1.1 and how do I check that every thing is OK to
> install it.
> Thanks.
> Linda
>|||Thank you!
I will check it.
:)