Cant find SMSS

After installing the evaluation edition of MSSQL Enterprise 2005 I can not find SSMS. I know I installed the client tools upon installation. It's not showing up on in the menu, where is the location for the executable file.

Is SSMS even distriubted with the evaluation edition?

If not, is it possible to download it from somwhere...

Did you get any warnings while setup cheked your computer configuration?

Did you specify client tools installation during setup?

P.S. This question suits http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=95&SiteID=1 forum better.

|||

SSMS is part of the evaluation edition. To see a report of what's installed go to Add/Remove Programs, select the entry for "Microsoft SQL Server 2005", select "Change", then select "Report". Under "Common Components" you'll want to see something like this:

Workstation Components
[Version: 9.00.1399.06 Edition: Evaluation Edition Patch level: 9.00.1399.06 Language: English (United States)]

If you see this and still don't think you have SSMS installed, close the report. On the "Change" dialog you should see an entry for Workstation Components, select it and press "Next". This will launch the component in maintenance mode. Just follow the dialogs. When you get to the feature tree be sure to select Management Tools under the Client Components node.

SSMS is installed to %ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\sqlwb.exe

|||Thanks for your reply::

I got the evauation to work when I downloaded the DVD image and burnt it to disk, and did a fresh install...

I'm now in the process of converting my MySQL talbles over to MSSQL... weeee fun... SSIS takes some of the headake away!|||Excellent!

Can't connect from ASP.Net 2.0 to SQL2000 after installing SQL2005

Hey guys,
I have a web application in ASP.Net 2.0 that needs to connect to a local
SQL2000 DB. After I installed SQL2005 this web app stopped working. I get
the following inner exception:
{"An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)"}
So after unsuccessfully googling I'm at least pretty sure about the
following: My web app thinks it's talking to a SQL2005 server. That one by
default uses shared memory when local. I think SQL2000 uses TCP/IP.
Who can tell me what I have to do so that my ASP.Net 2.0 web app properly
connects to SQL2000? Among the ideas on Google there were cliconfg.exe,
using <clear /> in the <connectionStrings> area in web.config and a couple
more. But none of them worked.
Thanks a lot, ChristophI'm having a very similar error, only mine connects locally but not remotely.
I was able to change the error slightly by putting the referencing the
database by domain and db, myMachine/myDB.
If it helps I looked at my log and it gave an error of 17187 which seems to
be a file in use, full disk, or low memory. Still researching. If I find it
I'll let you know. If you find the answer would you please post it so I can
try it too?
--
---
Magic is not in the hands of the magician but in the mind of the audience.
Animadverto est verus
"Christoph Wienands" wrote:
> Hey guys,
> I have a web application in ASP.Net 2.0 that needs to connect to a local
> SQL2000 DB. After I installed SQL2005 this web app stopped working. I get
> the following inner exception:
> {"An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified)"}
> So after unsuccessfully googling I'm at least pretty sure about the
> following: My web app thinks it's talking to a SQL2005 server. That one by
> default uses shared memory when local. I think SQL2000 uses TCP/IP.
> Who can tell me what I have to do so that my ASP.Net 2.0 web app properly
> connects to SQL2000? Among the ideas on Google there were cliconfg.exe,
> using <clear /> in the <connectionStrings> area in web.config and a couple
> more. But none of them worked.
> Thanks a lot, Christoph
>
>