Server Explorer - SQL Servers VS 2005 Beta 2

In VS2003 Pro in the Server Explorer I have:
Servers
   Computername
      Crystal Services
      Event Logs
      Management Classes
      Management Events
      Message Queues
      Performance Counters
      Services
      SQL Servers
In VS2005 Team Suite Beta 2 in Server Explorer I have the same as above BUT NO SQL SERVERS
I can use the Data Connections Wizard to connect to the Server and I can see the SQL Server if I create a new ODBC connection from Admin Tools.
I just cannot see SQL Servers in the Server Explorer.
I have ensured that the SQL Server is running, I have formatted the PC and reinstalled SQL & VS2005. I installed SQL 2005 and chose not to install SQL Express during the VS2005 install and still have the same result !
ANY ideas what I need to do to have SQL Servers show under the Computername in the Server Explorer

Answer this question

Server Explorer - SQL Servers VS 2005 Beta 2

TeddyG
Thanks for the reply, it is not really what I wanted to hear though!
IF I do no have access to the SQL Servers I will not be able to do anything with them besides know that they are there.
Also if I add a server eg one that is running SQL 2000, it doesn't show in the Server Explorer either, ie not SQL Browser service fault.
ALSO if I look in the help for "Server Components in Server Explorer" it lists SQL Servers as a node available in Server Explorer.

Could someone please explain how to get the SQL Servers to display under the Server Explorer.

Thanks,
Robin.
losdudechris
As far as I can tell. Visual Studio 2005 Standard eidtion does not have SQL Server 2005 integration capabilities. Thus, no Server Explorer. However. Visual Studio 2005 Professional addition does, including server explorer.

Hope this helps.

edgard

Karl Hilsmann MSFT wrote:
This is a change in functionality for a few reasons, the primary reason is security related. It was kinda bad to list all of the SQL Servers on the network that you could browse.

In VS 2003 by default only the local host is listed on Server Explorer. This, in my opinion, is the ideal balance between security and convinence.
It is absurd to even disable browsing a SQL server running on local host under the excuse of security.

tushars
Visual Studio 2005 Standard edition does have the ability to create Data Connections to SQL Server 2005. Please refer the reply I posted to Robin's post earlier on this thread for instructions to create a data connection.

I hope this helps

Mike Droney [MSFT]
Visual Studio Data
http://blogs.msdn.com/vsdata/
andrey
Hi Robin

To add a SQL Server in Server Explorer in Visual Studio 2005, you must add it to the Data Connections node in Server Explorer.
- Right click on the Data Connections node in Server Explorer and select 'Add Connection'
- If the Choose Data Source dialog appears, choose the 'Microsoft SQL Server' data source and click next
- The Add Connection dialog should now appear. Enter in the Server name (or use the drop down to see the list of SQL Servers available), enter authentication information and select a database name or attach a database file
- Test the connection and click ok
You can now expand the connection in Server Explorer and use the Visual Database Tools for your SQL Server connection.

Another thing to keep in mind is the new Microsoft SQL Server Management Studio Express tool which is in development. It is a graphical management tool for SQL Server 2005 Express instances and can also manage any instances created by any edition of SQL Server 2005. From here you can connect to a SQL Server 2005 instance and navigate through all databases you have rights to. There is a November 2005 Community Technical Preview available for download at:

http://www.microsoft.com/downloads/details.aspx FamilyId=82AFBD59-57A4-455E-A2D6-1D4C98D40F6E&displaylang=en

Please bear in mind that Microsoft SQL Server Management Studio Express - Community Technical Preview November 2005 is unsupported pre-release software.

I hope this helps

Mike Droney [MSFT]
Visual Studio Data
http://blogs.msdn.com/vsdata/

This posting is provided "AS IS" with no warranties, and confers no rights.
MKeeper
This is a change in functionality for a few reasons, the primary reason is security related. It was kinda bad to list all of the SQL Servers on the network that you could browse. SQL Server also realized this and in the SQL Server 2005 version, turn off the SQLBrowse functionality by default.

The solution is to create a data connection for each SQL Server that you wish to view, this authorizes you on the box in the role associated with your logon and allows you to view the server.

Thanks,
Karl
Geir Guldstein
This is really bad, I work on a lot (100+) of databases sql2000, and migrating to version 2005.
Creating database connections for each one is frustrating.
I liked it a lot in 2003.
This is clearly nog thought through.
matthijsbonte
Hi Karl,
So, I have several databases running on the server. Are you saying the plan is to have the user create a separate data conection for each database

Thanks,
Mark Starr

udm330ci

MarcelG wrote:
This is really bad, I work on a lot (100+) of databases sql2000, and migrating to version 2005.
Creating database connections for each one is frustrating.
I liked it a lot in 2003.
This is clearly nog thought through.

I whole-heartedly agree! This is really TERRIBLE news! I cannot understand this and it really puts a kink in my workload! Please bring this back! I can't understand what the Server Explorer is even in place for!

Server Explorer - SQL Servers VS 2005 Beta 2

Answer this question