Instances of SQL Server have disappeared

Hi,

We had 5 instances of SQL Server running on one of our machines and everything looked to be working fine. Today I installed another instance for a new application and once done and rebooted the new instance didn't show in the SQL Server Enterprise Manager. At this point we decided to uninstall it. After that 4 of the existing instances have diapered as well even though they are running and responding requests from their respective applications.

I did some googling and all I could see is something related to a command called nscontrol but I couldn't find any nscontrol executable on that machine.

Does anyone have any idea what this problem could be?

Thanksnscontrol is related to SQL Notification Services. I don't think that would be part of your solution.

I'm confused why you are installing a new instance of SQL Server for each application?

In any case, are you having any better luck? If not, can you go to the Windows command prompt on the server where SQL Server is running and type in osql -L and see if your instances are all listed? Have you checked your system's event log for any clues? How about the SQL Server error log?

I know that you should be able to run up to 16 instances of SQL Server, so you are probably not hitting that limitation.

Terri|||I'm with Terri. Instead of running 5 instances of SQL Server, why not use 1? And use 5 different databases? Seems like a better solution to me. Probably less overhead too.|||Sorry for not posting sooner, someone here has experienced something similar and the solution was to reregister every instance in Enterprise Manager. We can't explain why this thing happens but looks like this is what had to be done.

With respect to using instances rather then databases, the theory here is that we try to stay away from database administration and delegate it to the groups that actually need that application and databases that is why we give different instances to different groups of people. I hope that this explains somehow our situation.|||Glad you got it sorted out.

Yes, I had done research after you had made that post and read the cases for having multiple instances on the same server. That does make sense. Just keep in mind you can't have more than 16 instances :-)

Terri|||Yes, we knew about 16 instances limit.

Thanks

Instance not showning up

Hello,
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris

> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
David Gugick
Imceda Software
www.imceda.com

Instance not showning up

Hello,
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!
Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
David Gugick
Imceda Software
www.imceda.com
|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris

> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
David Gugick
Imceda Software
www.imceda.com
sql

Instance not showning up

Hello,
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris
> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
--
David Gugick
Imceda Software
www.imceda.com

Instance name already exists

Hello all...
Win2k3 enterprise
SQL 2000
2 nodes
I had 2 instances of SQL installed. I had to run setup to remove clustered
SQL so I could break the disk array and make it larger.
Now, I install instance 1 on node 1 just fine.
But when I run setup on node 2 to install instance 2, it tells me that
instance name already exists.
I thought when I "un-clustered" SQL that both instances would have been
removed. I can see both instance names in C:\program files\Microsoft sql
server\
How do I go about getting rid of the second instance name now, so I can
reinstall it?
Thanks in advance.
Jeff
Hi Jeff,
I would first try to uninstall the second instance the regular way i.e using the setup CD and choosing uninstall (the same way you uninstalled the first instance). If this doesn't work then you will need to manually uninstall
it. For more info, review
HOW TO: Manually Remove SQL Server 2000 Default, Named, or Virtual Instance
http://support.microsoft.com/?kbid=290991
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thank you Uttam,
I had tried the setup cd and it does not recognize the instance for
uninstall (only when I go to install the instance...go figure). But I did
not find the article you mention, so I will try that.
Jeff
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:RaXEsKppEHA.752@.cpmsftngxa06.phx.gbl...
> Hi Jeff,
> I would first try to uninstall the second instance the regular way i.e
using the setup CD and choosing uninstall (the same way you uninstalled the
first instance). If this doesn't work then you will need to manually
uninstall
> it. For more info, review
> HOW TO: Manually Remove SQL Server 2000 Default, Named, or Virtual
Instance
> http://support.microsoft.com/?kbid=290991
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>

instance is invalid

Error message during install:
Instance is invalid.
Just installed SP3a sql2kdesksp3.exe
Hi,
I think there is a instance conflicts. THis occurs if an instance of SQL
Server is already
installed on the target machine. To overcome this issue, you have to specify
the Instance name while running the setup.
Setup.exe INSTANCENAME=<name> SAPWD=<sapassword > /l*v c:\log.txt
Create a verbose log usinfg /l*v so that you can determine if installation
was successful or not.
Thanks
Hari
MCDBA
"hangman" <hangman@.discussions.microsoft.com> wrote in message
news:C0E83B1E-95A6-4016-8D04-D5DA1A0B3765@.microsoft.com...
> Error message during install:
> Instance is invalid.
> Just installed SP3a sql2kdesksp3.exe

Instance

I installed a new instance on SQL 2k, but it is reading
the information about the instance has already installed.
What's "it" in this context? Can you elaborate?
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:12be601c44336$8203f950$a601280a@.phx.gbl...
> I installed a new instance on SQL 2k, but it is reading
> the information about the instance has already installed.
>
|||When you say reading information from albout the already installed instance
what do you mean?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||When I open the new instance the objects of first instance
are available. All the databases and logins.
The directory installation is different and on Data folder
there are master, model, temp and msdb databases. >--
Original Message--
>When you say reading information from albout the already
installed instance
>what do you mean?
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>
|||<anonymous@.discussions.microsoft.com> wrote in message
news:1307601c44344$0b7b17b0$a101280a@.phx.gbl...
> When I open the new instance the objects of first instance
> are available. All the databases and logins.
> The directory installation is different and on Data folder
> there are master, model, temp and msdb databases. >--
Please describe your exact procedure when you "open" the instance. What
client are you using (Enterprise Manager? Query Analyzer? ISQL? OSQL?
something else?), etc. Go into a lot of detail. It's probably something
subtle that you'll catch as you write up the description.
|||SQL 2k Standard
On the first installation of SQL Server was created a
named instance and not a Default instance. Now during the
new instance installation when I try to install a new
instance the screen where the instance is created the
Default Instance option is enable. Then I choose a new
instance. End of installation with successfull.
The mssqlserver service is started and the two instances
are enabled.
The problem is both instance are the same. If I create a
database in the new instance it (the new database) shows
up in the first instance also.
[vbcol=seagreen]
>--Original Message--
><anonymous@.discussions.microsoft.com> wrote in message
>news:1307601c44344$0b7b17b0$a101280a@.phx.gbl...
instance[vbcol=seagreen]
folder
> Please describe your exact procedure when you "open"
the instance. What
>client are you using (Enterprise Manager? Query
Analyzer? ISQL? OSQL?
>something else?), etc. Go into a lot of detail. It's
probably something
>subtle that you'll catch as you write up the description.
>
>.
>
|||Can you verify that you're actually connected to a different instance?
Please run:
SELECT @.@.SERVERNAME
And make sure the instance name is what you think it should be before you
create your database.
<anonymous@.discussions.microsoft.com> wrote in message
news:12ebd01c44354$44fc3630$a001280a@.phx.gbl...[vbcol=seagreen]
> SQL 2k Standard
> On the first installation of SQL Server was created a
> named instance and not a Default instance. Now during the
> new instance installation when I try to install a new
> instance the screen where the instance is created the
> Default Instance option is enable. Then I choose a new
> instance. End of installation with successfull.
> The mssqlserver service is started and the two instances
> are enabled.
> The problem is both instance are the same. If I create a
> database in the new instance it (the new database) shows
> up in the first instance also.
>
> instance
> folder
> the instance. What
> Analyzer? ISQL? OSQL?
> probably something
|||I'm connected to a new instance. And I saw all the objects
that are in old instance. The sa is the same, but I
created a sa with different password.
The default instance was not installed, only the named
instance. Is there some problem ?
Can I install a defaul instance in this moment or it is
only possible during the first SQL Server installation ?
Thanks,
>--Original Message--
>Can you verify that you're actually connected to a
different instance?
>Please run:
>SELECT @.@.SERVERNAME
>And make sure the instance name is what you think it
should be before you[vbcol=seagreen]
>create your database.
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:12ebd01c44354$44fc3630$a001280a@.phx.gbl...
the[vbcol=seagreen]
--[vbcol=seagreen]
you "open"[vbcol=seagreen]
description.
>
>.
>
sql

Instance

I installed a new instance on SQL 2k, but it is reading
the information about the instance has already installed.What's "it" in this context? Can you elaborate?
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:12be601c44336$8203f950$a601280a@.phx.gbl...
> I installed a new instance on SQL 2k, but it is reading
> the information about the instance has already installed.
>|||When you say reading information from albout the already installed instance
what do you mean?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||When I open the new instance the objects of first instance
are available. All the databases and logins.
The directory installation is different and on Data folder
there are master, model, temp and msdb databases. >--
Original Message--
>When you say reading information from albout the already
installed instance
>what do you mean?
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>|||<anonymous@.discussions.microsoft.com> wrote in message
news:1307601c44344$0b7b17b0$a101280a@.phx.gbl...
> When I open the new instance the objects of first instance
> are available. All the databases and logins.
> The directory installation is different and on Data folder
> there are master, model, temp and msdb databases. >--
Please describe your exact procedure when you "open" the instance. What
client are you using (Enterprise Manager? Query Analyzer? ISQL? OSQL?
something else?), etc. Go into a lot of detail. It's probably something
subtle that you'll catch as you write up the description.|||SQL 2k Standard
On the first installation of SQL Server was created a
named instance and not a Default instance. Now during the
new instance installation when I try to install a new
instance the screen where the instance is created the
Default Instance option is enable. Then I choose a new
instance. End of installation with successfull.
The mssqlserver service is started and the two instances
are enabled.
The problem is both instance are the same. If I create a
database in the new instance it (the new database) shows
up in the first instance also.
>--Original Message--
><anonymous@.discussions.microsoft.com> wrote in message
>news:1307601c44344$0b7b17b0$a101280a@.phx.gbl...
>> When I open the new instance the objects of first
instance
>> are available. All the databases and logins.
>> The directory installation is different and on Data
folder
>> there are master, model, temp and msdb databases. >--
> Please describe your exact procedure when you "open"
the instance. What
>client are you using (Enterprise Manager? Query
Analyzer? ISQL? OSQL?
>something else?), etc. Go into a lot of detail. It's
probably something
>subtle that you'll catch as you write up the description.
>
>.
>|||Can you verify that you're actually connected to a different instance?
Please run:
SELECT @.@.SERVERNAME
And make sure the instance name is what you think it should be before you
create your database.
<anonymous@.discussions.microsoft.com> wrote in message
news:12ebd01c44354$44fc3630$a001280a@.phx.gbl...
> SQL 2k Standard
> On the first installation of SQL Server was created a
> named instance and not a Default instance. Now during the
> new instance installation when I try to install a new
> instance the screen where the instance is created the
> Default Instance option is enable. Then I choose a new
> instance. End of installation with successfull.
> The mssqlserver service is started and the two instances
> are enabled.
> The problem is both instance are the same. If I create a
> database in the new instance it (the new database) shows
> up in the first instance also.
>
> >--Original Message--
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:1307601c44344$0b7b17b0$a101280a@.phx.gbl...
> >> When I open the new instance the objects of first
> instance
> >> are available. All the databases and logins.
> >> The directory installation is different and on Data
> folder
> >> there are master, model, temp and msdb databases. >--
> >
> > Please describe your exact procedure when you "open"
> the instance. What
> >client are you using (Enterprise Manager? Query
> Analyzer? ISQL? OSQL?
> >something else?), etc. Go into a lot of detail. It's
> probably something
> >subtle that you'll catch as you write up the description.
> >
> >
> >.
> >|||I'm connected to a new instance. And I saw all the objects
that are in old instance. The sa is the same, but I
created a sa with different password.
The default instance was not installed, only the named
instance. Is there some problem ?
Can I install a defaul instance in this moment or it is
only possible during the first SQL Server installation ?
Thanks,
>--Original Message--
>Can you verify that you're actually connected to a
different instance?
>Please run:
>SELECT @.@.SERVERNAME
>And make sure the instance name is what you think it
should be before you
>create your database.
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:12ebd01c44354$44fc3630$a001280a@.phx.gbl...
>> SQL 2k Standard
>> On the first installation of SQL Server was created a
>> named instance and not a Default instance. Now during
the
>> new instance installation when I try to install a new
>> instance the screen where the instance is created the
>> Default Instance option is enable. Then I choose a new
>> instance. End of installation with successfull.
>> The mssqlserver service is started and the two instances
>> are enabled.
>> The problem is both instance are the same. If I create a
>> database in the new instance it (the new database) shows
>> up in the first instance also.
>>
>> >--Original Message--
>> >
>> ><anonymous@.discussions.microsoft.com> wrote in message
>> >news:1307601c44344$0b7b17b0$a101280a@.phx.gbl...
>> >> When I open the new instance the objects of first
>> instance
>> >> are available. All the databases and logins.
>> >> The directory installation is different and on Data
>> folder
>> >> there are master, model, temp and msdb databases. >--
--
>> >
>> > Please describe your exact procedure when
you "open"
>> the instance. What
>> >client are you using (Enterprise Manager? Query
>> Analyzer? ISQL? OSQL?
>> >something else?), etc. Go into a lot of detail. It's
>> probably something
>> >subtle that you'll catch as you write up the
description.
>> >
>> >
>> >.
>> >
>
>.
>

Instance

I installed a new instance on SQL 2k, but it is reading
the information about the instance has already installed.What's "it" in this context? Can you elaborate?
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:12be601c44336$8203f950$a601280a@.phx
.gbl...
> I installed a new instance on SQL 2k, but it is reading
> the information about the instance has already installed.
>|||When you say reading information from albout the already installed instance
what do you mean?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||When I open the new instance the objects of first instance
are available. All the databases and logins.
The directory installation is different and on Data folder
there are master, model, temp and msdb databases. >--
Original Message--
>When you say reading information from albout the already
installed instance
>what do you mean?
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>|||<anonymous@.discussions.microsoft.com> wrote in message
news:1307601c44344$0b7b17b0$a101280a@.phx
.gbl...
> When I open the new instance the objects of first instance
> are available. All the databases and logins.
> The directory installation is different and on Data folder
> there are master, model, temp and msdb databases. >--
Please describe your exact procedure when you "open" the instance. What
client are you using (Enterprise Manager? Query Analyzer? ISQL? OSQL?
something else?), etc. Go into a lot of detail. It's probably something
subtle that you'll catch as you write up the description.|||SQL 2k Standard
On the first installation of SQL Server was created a
named instance and not a Default instance. Now during the
new instance installation when I try to install a new
instance the screen where the instance is created the
Default Instance option is enable. Then I choose a new
instance. End of installation with successfull.
The mssqlserver service is started and the two instances
are enabled.
The problem is both instance are the same. If I create a
database in the new instance it (the new database) shows
up in the first instance also.

>--Original Message--
><anonymous@.discussions.microsoft.com> wrote in message
> news:1307601c44344$0b7b17b0$a101280a@.phx
.gbl...
instance[vbcol=seagreen]
folder[vbcol=seagreen]
> Please describe your exact procedure when you "open"
the instance. What
>client are you using (Enterprise Manager? Query
Analyzer? ISQL? OSQL?
>something else?), etc. Go into a lot of detail. It's
probably something
>subtle that you'll catch as you write up the description.
>
>.
>|||Can you verify that you're actually connected to a different instance?
Please run:
SELECT @.@.SERVERNAME
And make sure the instance name is what you think it should be before you
create your database.
<anonymous@.discussions.microsoft.com> wrote in message
news:12ebd01c44354$44fc3630$a001280a@.phx
.gbl...[vbcol=seagreen]
> SQL 2k Standard
> On the first installation of SQL Server was created a
> named instance and not a Default instance. Now during the
> new instance installation when I try to install a new
> instance the screen where the instance is created the
> Default Instance option is enable. Then I choose a new
> instance. End of installation with successfull.
> The mssqlserver service is started and the two instances
> are enabled.
> The problem is both instance are the same. If I create a
> database in the new instance it (the new database) shows
> up in the first instance also.
>
>
> instance
> folder
> the instance. What
> Analyzer? ISQL? OSQL?
> probably something|||I'm connected to a new instance. And I saw all the objects
that are in old instance. The sa is the same, but I
created a sa with different password.
The default instance was not installed, only the named
instance. Is there some problem ?
Can I install a defaul instance in this moment or it is
only possible during the first SQL Server installation ?
Thanks,
>--Original Message--
>Can you verify that you're actually connected to a
different instance?
>Please run:
>SELECT @.@.SERVERNAME
>And make sure the instance name is what you think it
should be before you
>create your database.
>
><anonymous@.discussions.microsoft.com> wrote in message
> news:12ebd01c44354$44fc3630$a001280a@.phx
.gbl...
the[vbcol=seagreen]
--[vbcol=seagreen]
you "open"[vbcol=seagreen]
description.[vbcol=seagreen]
>
>.
>

installtion of analytics server

i downloaded proclarity desktop profesional from microsoft website and installed ..

but i am unable to connect to analytics server..does it need separate software or is it my databse..what is pas in that and which user id /password i must give..Is it databse serevr address or any other..

i tried by all means but failed..can u give me other versions of downloads..or help in installing desktop profesional...

its urgent...plzz help me out...

Hi,

You don't need anymore software, you should be able to connect to the ProClarity Server with out any problems. That is with the assumption you can access it via a URL. Normally something like http://SERVERNAME/PAS.

You did install the analytic server?

Hope that helps

Matt

installtion file for SQL CE 2.0 to install in Real PocketPC

HI,

i have one instalation file of SQL CE 2.0 named setup.exe ,i installed that in my desktop it works well.i could not install the same file inside the pocketPC.Can any one give me some information about how to get the installation file of SQL CE 2.0 and how to install that in real pocketPC.Thanks in advance.

Best Regards

Ihsan

Not having worked with SQL CE 2.0 (available here) for a while I would assume that it follows the same pattern as the current verion which is that the installer is to be run on the desktop NOT the device. After running the installer either the runtime dlls or a mobile installer will be available - you should also read the ReadMe and consider installing the books online (available locally after installing the main SQL CE 2.0 installer)

Hope this helps.

Installtion failed

Hi,
I failed to install SQL Server 2005 to my Win2003 server which has AVG antivirus/firewall installed. It still not work even I disable the firewall. Please advice

Here is the error log

2006-11-17 13:45:12.25 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2006-11-17 13:45:12.25 Server (c) 2005 Microsoft Corporation.
2006-11-17 13:45:12.25 Server All rights reserved.
2006-11-17 13:45:12.25 Server Server process ID is 3300.
2006-11-17 13:45:12.25 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-11-17 13:45:12.26 Server This instance of SQL Server last reported using a process ID of 2768 at 11/17/2006 1:45:00 PM (local) 11/17/2006 9:45:00 PM (UTC). This is an informational message only; no user action is required.
2006-11-17 13:45:12.26 Server Registry startup parameters:
2006-11-17 13:45:12.26 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-11-17 13:45:12.26 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-11-17 13:45:12.26 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-11-17 13:45:12.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-11-17 13:45:12.28 Server Detected 2 CPUs. This is an informational message; no user action is required.
2006-11-17 13:45:12.43 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2006-11-17 13:45:12.45 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2006-11-17 13:45:13.48 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2006-11-17 13:45:13.48 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-11-17 13:45:13.48 spid5s Starting up database 'master'.
2006-11-17 13:45:13.51 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-11-17 13:45:13.59 spid5s SQL Trace ID 1 was started by login "sa".
2006-11-17 13:45:13.60 spid5s Starting up database 'mssqlsystemresource'.
2006-11-17 13:45:13.78 spid5s Server name is 'VSMRND'. This is an informational message only. No user action is required.
2006-11-17 13:45:13.78 spid9s Starting up database 'model'.
2006-11-17 13:45:13.85 Server The certificate was successfully loaded for encryption.
2006-11-17 13:45:13.85 spid9s Clearing tempdb database.
2006-11-17 13:45:13.85 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2006-11-17 13:45:13.85 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2006-11-17 13:45:13.87 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2006-11-17 13:45:13.87 Server Dedicated admin connection support was established for listening locally on port 1434.
2006-11-17 13:45:13.87 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-11-17 13:45:13.90 spid5s Starting up database 'msdb'.
2006-11-17 13:45:14.09 spid5s Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
2006-11-17 13:45:14.25 spid9s Starting up database 'tempdb'.
2006-11-17 13:45:14.31 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-11-17 13:45:14.32 spid12s The Service Broker protocol transport is disabled or not configured.
2006-11-17 13:45:14.32 spid12s The Database Mirroring protocol transport is disabled or not configured.
2006-11-17 13:45:14.39 spid12s Service Broker manager has started.
2006-11-17 13:57:11.79 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2006-11-17 13:57:12.34 Server The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required.
2006-11-17 13:57:12.34 Server Error: 17054, Severity: 16, State: 1.
2006-11-17 13:57:12.34 Server The current event was not reported to the Windows Events log. Operating system error = 31(A device attached to the system is not functioning.). You may need to clear the Windows Events log if it is full.
2006-11-17 13:57:12.49 spid12s Service Broker manager has shut down.
2006-11-17 13:57:13.15 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Moved thread to SQL Server Setup & Upgrade. This is a better forum for your post.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||Hi,
To whom may concern, I found the mistake.
The error happens is because I extracted SQL Server 2005 CD 1 and CD2 into two different folder (as I can't extract them into same folder, this will overwritten each other). When I run setup from CD1 folder, I tick SQL Server database engine and workstation component. As Workstation component is in CD2 cause setup unable to locate it.

Install workstation component only using setup.exe under CD2 folder will solve the problem.

HTH

Installing/Configuration

Hi,

I'm

pretty new to this reporting services thing. I've installed it on my PC

and it runs fine. However, other PCs on my LAN can't access the reports

through their browser. I think there is an issue with IIS also involved

because they cannot even browse to the default website on my PC. There

may also be some security related issues as well (with IIS, Reporting

Services and my SQL Server 2005 database).

Is there any step

by step guide on how to configure all these three things properly for

remote access available that anyone can recommend?

Or can anyone give me advice?

Thanks,

Frank

Does the URL use the IP addy or machine name when they try to access the default website? If uses the machine name, try the IP address.

Are you on a workgroup or domain?

Can they ping your machine by name?

Is there an explicit error in the browser other than 404 not found?

What is the security model being used in IIS: Anonymous, IWA (integrated windows authentication)?

These are just a few questions to get us going in the right direction

Installing, creating database, updating schema?

Hi there,

I have a database on my test machine that will need to be installed on users
machines. I would like to create the database with the given schema on the
users machine and also with some suitable default values in the tables. I
note that although I can script the schema so that re-creating the structure
of the database is simple on the users machine, I cannot script the contents
of the tables also (automatically). What I would like to do is take some
kind of "snapshot", save it as a script and then run this script in my
installer. Are there any tools available to do this?

Secondly and related to the above: if I subsequently make changes to the
database schema (adding or removing columns, altering, adding or removing
stored procedures etc.), how do I roll out those changes to a customer? Do
I need to hand code an "upgrade" script, or is there a tool that will
produce a "difference between" script I can run on the customers machine?

Thanks for any tips you can give me about this.

RobinRobin Tucker (idontwanttobespammedanymore@.reallyidont.com) writes:
> I have a database on my test machine that will need to be installed on
> users machines. I would like to create the database with the given
> schema on the users machine and also with some suitable default values
> in the tables. I note that although I can script the schema so that
> re-creating the structure of the database is simple on the users
> machine, I cannot script the contents of the tables also
> (automatically). What I would like to do is take some kind of
> "snapshot", save it as a script and then run this script in my
> installer. Are there any tools available to do this?

SQL Server MVP Vyas Kondreddi has a tool that generates INSERT statements
from a table: http://vyaskn.tripod.com/code.htm#inserts

> Secondly and related to the above: if I subsequently make changes to the
> database schema (adding or removing columns, altering, adding or
> removing stored procedures etc.), how do I roll out those changes to a
> customer? Do I need to hand code an "upgrade" script, or is there a
> tool that will produce a "difference between" script I can run on the
> customers machine?

There are several paths to take. Many people use a third-party tool that
compares two databases and then generates a script. Very popular is
SQL Compare from Red Gate. I have not used this tool myself, though.

A better approach in my opinion, is to have all code under source control.
In this case, your development database is not your master, but the
version-control system is. A basic version-control system will not
provide any update scripts for you, as a version-control system is a
general container for all sorts of code. What you do is that when you
ship, you set a label, and then you can later inquire the VCS for
changes since that label. There are plenty of VCS on the market. Very
popular among Microsoft customers is Visual SourceSafe which is part
of Visual Studio. VSS is not a very good for serious configuraton
management, but it's easy to get started with, and works perfectly OK for
smaller groups.

There are a couple of third-party tools that are specialized for doing
version control on SQL Server. Typically, they sit on top of SourceSafe
or some other generic VCS. Unfortunately, I don't recall any names right
now.

In our shop we use VSS, together with a toolset that includes tools for
loading stored procedures (with a lot of bells and whistles, like
automatic insert of SET NOCOUNT ON, WITH ENCRYPTION (on request),
automatic GRANT, a preprocessor). We also have a tool that builds
update scripts from the checkins in SourceSafe. The tool also maintains
its own tables in the target databases, so that we know in which state
each database is in. This toolset is available as freeware on
http://www.abaris.se/abaperls/. (I uploaded the latest version of it,
just the other day, by the way.)

Judging from your question, you may be best off with something like
SQL Compare in the short run. But if more people get involved with
your work, you should definitely consider to move to a version-
control system. There are a few things to keep in mind with updating
from a model database:

o A development may contain junk code and junk tables from tests and
experiments.
o A table change may be as simple as adding a nullable column, but it
can also be very complex if you are making a major restructiring. A
tool probably needs some help in this case.
o If you have preloaded data that you want to deploy, you need a tool
where you selectively can migrate data.

The way we handle pre-loaded data by the way, is to enter the data in
Excel books, and then we have a tool that generates INSERT files from
the the Excel files. The files does not contain any INSERT statements,
but calls to stored procedures which inserts or updates. The reason we
use Excel is that some of our files are quite complex. and we have
different settings for different customers.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Very interesting. Thanks for your comprehensive reply. I think I will need
to study this question at some length before deciding which approach to
take.

Robin

"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9595F230624F5Yazorman@.127.0.0.1...
> Robin Tucker (idontwanttobespammedanymore@.reallyidont.com) writes:
>> I have a database on my test machine that will need to be installed on
>> users machines. I would like to create the database with the given
>> schema on the users machine and also with some suitable default values
>> in the tables. I note that although I can script the schema so that
>> re-creating the structure of the database is simple on the users
>> machine, I cannot script the contents of the tables also
>> (automatically). What I would like to do is take some kind of
>> "snapshot", save it as a script and then run this script in my
>> installer. Are there any tools available to do this?
> SQL Server MVP Vyas Kondreddi has a tool that generates INSERT statements
> from a table: http://vyaskn.tripod.com/code.htm#inserts
>> Secondly and related to the above: if I subsequently make changes to the
>> database schema (adding or removing columns, altering, adding or
>> removing stored procedures etc.), how do I roll out those changes to a
>> customer? Do I need to hand code an "upgrade" script, or is there a
>> tool that will produce a "difference between" script I can run on the
>> customers machine?
> There are several paths to take. Many people use a third-party tool that
> compares two databases and then generates a script. Very popular is
> SQL Compare from Red Gate. I have not used this tool myself, though.
> A better approach in my opinion, is to have all code under source control.
> In this case, your development database is not your master, but the
> version-control system is. A basic version-control system will not
> provide any update scripts for you, as a version-control system is a
> general container for all sorts of code. What you do is that when you
> ship, you set a label, and then you can later inquire the VCS for
> changes since that label. There are plenty of VCS on the market. Very
> popular among Microsoft customers is Visual SourceSafe which is part
> of Visual Studio. VSS is not a very good for serious configuraton
> management, but it's easy to get started with, and works perfectly OK for
> smaller groups.
> There are a couple of third-party tools that are specialized for doing
> version control on SQL Server. Typically, they sit on top of SourceSafe
> or some other generic VCS. Unfortunately, I don't recall any names right
> now.
> In our shop we use VSS, together with a toolset that includes tools for
> loading stored procedures (with a lot of bells and whistles, like
> automatic insert of SET NOCOUNT ON, WITH ENCRYPTION (on request),
> automatic GRANT, a preprocessor). We also have a tool that builds
> update scripts from the checkins in SourceSafe. The tool also maintains
> its own tables in the target databases, so that we know in which state
> each database is in. This toolset is available as freeware on
> http://www.abaris.se/abaperls/. (I uploaded the latest version of it,
> just the other day, by the way.)
> Judging from your question, you may be best off with something like
> SQL Compare in the short run. But if more people get involved with
> your work, you should definitely consider to move to a version-
> control system. There are a few things to keep in mind with updating
> from a model database:
> o A development may contain junk code and junk tables from tests and
> experiments.
> o A table change may be as simple as adding a nullable column, but it
> can also be very complex if you are making a major restructiring. A
> tool probably needs some help in this case.
> o If you have preloaded data that you want to deploy, you need a tool
> where you selectively can migrate data.
> The way we handle pre-loaded data by the way, is to enter the data in
> Excel books, and then we have a tool that generates INSERT files from
> the the Excel files. The files does not contain any INSERT statements,
> but calls to stored procedures which inserts or updates. The reason we
> use Excel is that some of our files are quite complex. and we have
> different settings for different customers.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||I would recommend you have a look at Innovartis DB Ghost at
http://www.innovartis.co.uk/ It is designed specifically for your
requirement i.e. automated database change management, generation of
upgrade scripts, build verification, database synchronization,
deployment of changes, integration with version control system, handles
schema & data.

John McGrath
SQL Server DBA MCSE

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!sql

Installing WSS2 on SQL server

MS provides information about how to install and run SQL Reporting
side-by-side with WSS2 installed. Are there any changes or special problems
to install WSS2 on a Windows 2003 server running SQL reporting? Thanks
DanThe only recent change is that Report Manager no longer requires session
state to be enabled. You don't need to edit the web.config file after
setting the Application Pool. The only downside to this is that Report
Manager preferences of list vs. details is not kept when session state is
off.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan Slaby" <dslaby@.evergreeninfo.biz> wrote in message
news:OK2V54uSFHA.2812@.TK2MSFTNGP09.phx.gbl...
> MS provides information about how to install and run SQL Reporting
> side-by-side with WSS2 installed. Are there any changes or special
> problems to install WSS2 on a Windows 2003 server running SQL reporting?
> Thanks
> Dan
>|||Will there be any issues if the root does not get extended, but hosted
websites to support SQL reporting do?
Dan
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:uwtYvOvSFHA.3696@.TK2MSFTNGP15.phx.gbl...
> The only recent change is that Report Manager no longer requires session
> state to be enabled. You don't need to edit the web.config file after
> setting the Application Pool. The only downside to this is that Report
> Manager preferences of list vs. details is not kept when session state is
> off.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Dan Slaby" <dslaby@.evergreeninfo.biz> wrote in message
> news:OK2V54uSFHA.2812@.TK2MSFTNGP09.phx.gbl...
>> MS provides information about how to install and run SQL Reporting
>> side-by-side with WSS2 installed. Are there any changes or special
>> problems to install WSS2 on a Windows 2003 server running SQL reporting?
>> Thanks
>> Dan
>|||You just need to make sure that the Reporting Services virtual directories
are in the exclusion list for SP.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan Slaby" <dslaby@.evergreeninfo.biz> wrote in message
news:%23djCK$zSFHA.2872@.TK2MSFTNGP14.phx.gbl...
> Will there be any issues if the root does not get extended, but hosted
> websites to support SQL reporting do?
> Dan
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> news:uwtYvOvSFHA.3696@.TK2MSFTNGP15.phx.gbl...
>> The only recent change is that Report Manager no longer requires session
>> state to be enabled. You don't need to edit the web.config file after
>> setting the Application Pool. The only downside to this is that Report
>> Manager preferences of list vs. details is not kept when session state is
>> off.
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Dan Slaby" <dslaby@.evergreeninfo.biz> wrote in message
>> news:OK2V54uSFHA.2812@.TK2MSFTNGP09.phx.gbl...
>> MS provides information about how to install and run SQL Reporting
>> side-by-side with WSS2 installed. Are there any changes or special
>> problems to install WSS2 on a Windows 2003 server running SQL reporting?
>> Thanks
>> Dan
>>
>

Installing VS .NET after Installing Reporting Services

I installed VS .NET after installing Reporting Services. When I bring up VS,
I don't see the Report Designer choices. What do I need to do to make them
appear?If you installed RS without VS.Net then what you installed is the server
piece. What you need to do now is install the report designer. Rerun setup
and install just the report designer.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bob Sherman" <Bob Sherman@.discussions.microsoft.com> wrote in message
news:BEB7E965-CA6C-434B-A931-2AE7A27EB8F1@.microsoft.com...
> I installed VS .NET after installing Reporting Services. When I bring up
VS,
> I don't see the Report Designer choices. What do I need to do to make them
> appear?
>

Installing the samples after an install

Hi,

I stupidly did not install the samples for 2005 when I installed the dev edition on my machines. Now I would like to. Unfortunately, I can't seem to find a way to do it. The installation process always says I have the documentation installed (I have books online installed). It appears that there is no way to install the samples if you have installed the documentation and workstation items.

Is there somewhere I can download the samples?

Thanks for any help.
]Monty[Do the following:

1) Go to Add/Remove Programs
2) Click on the entry for SQL Server 2005 and click the Change button
3) Select "Workstation Components" and click Next (this will launch the feature in maintenance mode which allows you to add or remove components)
4) Follow the dialogs accepting the defaults.
5) On the "Change or Remove..." dialog select the "Change Installed Components" option.
6) On the "Feature Selection" dialog expand the "Documentation, Samples, and Sample Databases" node.
7) Select the samples you want installed (e.g. Sample Databases and/or Code Samples). Follow the dialogs to the end
- If your installing the Sample Databases you'll be prompted for an instance to connect them to.
- If your installing the Code Samples, this process drops the Code Sample MSI to your machine. You'll need to go to "Start -> All Programs -> Microsoft SQL Server 2005 -> Documentation and Samples -> Samples" and run "Microsoft SQL Server 2005 Samples (English)" to install the actual code samples.

Dan|||Thanks a ton, man.

]Monty[|||

The sample databases and samples can also be downloaded from this site:
http://msdn.microsoft.com/sql/downloads/samples/

Regards,

sql

installing the sample databases and documentation

There are two instances: SQL2005 and SQL2005Express on two different units. While there is Visual Studio 2005 Team Edition also installed on the units have not attempted these component installs through either yet. Have spent the better part of two days, following all the directions having searched help locally, online, technet,and applied their advice respectively. While I've taken out the old instances, downloaded updated ones in both my SQL Server instances they do not show as installed under Programs->SQL Server (whichever instance)->Tutorials ...However they do show installed in Control Panel and they can be found via Explorer (AdWorks DBCI+AdWorks BICI and Express instance on the other unit. Have also download SP2 and installed it, but this has proved of no help. @. My wits' end, any help will be appreciated.

Documentation and sample databases are an option during installation.

Books Online appears as an installed program in Add/Remove Programs but the sample databases do not.

If AdventureWorks was installed with 2005 but did not appear in Object Explorer you can attach it. Attach is on the right-click menu of Databases in Object Explorer.

|||

You can also find the SQL Server 2005 documentation available online at:

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx

It has many great tutorials to get started.

Thanks,
Sam Lester (MSFT)

|||Thank you for your suggestion Lester, however before my initial post had already consulted books online, and downloaded the latest version to stay in sync with the software. Part of my frustration comes from following their directions but failing to achieve similar outcomes. Adventure Works databases are definitely resident on my computer, though not in the same directories in the Explorer file hierarchy indicated by the manuals/instructions. The directions have been exhaustively followed a number of times, replete with uninstalls then reinstalls - all to no avail. This is the case in both units, each with a different operating system and different version of SQL. Am still stymied.

Installing the AdventureWorks Database

I've downloaded and installed the Adventure works database

I follow the instructions give here

http://msdn2.microsoft.com/en-us/library/ms310325.aspx

but this command here:

exec sp_attach_db @.dbname=N'AdventureWorks', @.filename1=N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\AdventureWorks_Data.mdf', @.filename2=N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\AdventureWorks_log.ldf'

results in this error:

"unable to open physical file,................................................. the system can't find the specified file."

AdventureWorks_log.ldf + AdventureWorks_Data.mdf ...................don't exist at this location:

c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\

i'm thinking of reinstalling the whole adventure works DB.

any ideas please

Moving to the SQL Server Setup & Upgrade forum. This may not strictly be a setup problem, but this is probably the best place to start to make sure you have the sample database installed correctly. In any case, this is best suited for one of the SQL Server forums instead of .NET Data Access.

Thanks,
Sarah

Installing SSRS report designer with Visual Studio 2005

I have VS 2005 installed on my workstation. I have Sql Server 2005 on a
database server, and
just installed Reporting Services on a web server.
How do I install the Report Services report designer on my workstation in VS
2005?
thanks,
Bob M..Just place the dick into drive of your computer and start installation.
During the installation, you can choose to install client tool only.
"Bob Murdoch" <ram_re_move_5@.erols.com> wrote in message
news:uwjclTfBIHA.4752@.TK2MSFTNGP04.phx.gbl...
>I have VS 2005 installed on my workstation. I have Sql Server 2005 on a
>database server, and
> just installed Reporting Services on a web server.
> How do I install the Report Services report designer on my workstation in
> VS 2005?
> thanks,
> Bob M..
>|||"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
> Just place the dick into drive of your computer and start installation.
> During the installation, you can choose to install client tool only.
>
Besides the slip of the keyboard, which disk are you referring to? When I
try to use the Sql Server 2005 disk, the Reporting Services option is grayed
out (presumably because I don't have IIS installed on my workstation?).
thanks,
Bob M..|||I do not not what kind of disk your SQL Server2005 is on. I have heard it
may be on 2 CDs or 1 DVD. Mine is from MSDN subscription, which has two
setup.exe - one for the server part and one for client tools part.
Whatever you have, you should install client components only, including
Connectivity components, Management tools, Business Intelligence Development
Studio (this is what you need!), SDK, documentation... You do not need to
install RS for report designing, unless you want to.
"Bob Murdoch" <ram_re_move_5@.erols.com> wrote in message
news:OSnjevfBIHA.2004@.TK2MSFTNGP06.phx.gbl...
> "Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
>> Just place the dick into drive of your computer and start installation.
>> During the installation, you can choose to install client tool only.
> Besides the slip of the keyboard, which disk are you referring to? When I
> try to use the Sql Server 2005 disk, the Reporting Services option is
> grayed out (presumably because I don't have IIS installed on my
> workstation?).
> thanks,
> Bob M..
>