Link to home
Start Free TrialLog in
Avatar of NullableAnswer
NullableAnswer

asked on

Licensing and techncal questions for using SSMS 2008 to connect to SQL Server 2005.

Currently our dept is using SQL Server 2005.  The company doesn't want to spend money on another copy of Visual Studio 2005 for debugging.  I notice SSMS for SQL Server 2008 has debug tools built in (something lacking in SSMS for SQl Server 2005).

The company has licenses for both SQL Server 2005 Standard & SQL Server 2008 Standard.
Our dept is still using 2005.

Are there any technical issues with installing SSMS 2008 on development workstation to gain access to debug tools built into SSMS 2008 (missing in SSMS 2005)?  The workstation will be accessing SQL Server 2005 exclusively.

Are there any licensing issues related to deploying SSMS 2008 to workstations that will connect to SQL Server 2005?  It is my understanding that with SQL Server 2005/2008 Standard you can deploy "workstation tools" to an unlimited number of machines.
ASKER CERTIFIED SOLUTION
Avatar of Anthony Perkins
Anthony Perkins
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of NullableAnswer
NullableAnswer

ASKER

I am aware of that.  

Are you saying using SSMS 2008 and connecting to SQL Server 2005 instance I won't get intelisense or T-SQL Debugger?
Yes, I am, not to mention a few other incompatibilities.
To anyone researching this unfortonately it looks like acperkins is right.

Despite SSMS 2008 having T-SQL debugger it won't work if the code you attempt to debug is connecting to SQL 2005 instances.

Did some research with trial version based on acperkins response and got this error message:
Cannot execute script.
Unable to start the Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)

So looks like if you have a SQL 2005 instance your only debug options are Visual Studio 2005 or upgrading the instance to 2008.
>>Despite SSMS 2008 having T-SQL debugger it won't work<<
Somehow you are confusing SSMS 2008 with MS SQL Server 2008.  It is MS SQL Server 2008 that has the debugging options.  SSMS is just the client interface, so since the back-end does not support it you are SOL.
Read up on Brad's column here:
Management Studio Improvements in SQL Server 2008
http://www.simple-talk.com/sql/learn-sql-server/management-studio-improvements-in-sql-server-2008/

The relevant part:

Subject: Which SSMS 2008 Features Work with SQL Server 2005
Posted by: bradmcgehee (view profile)
Posted on: Monday, August 18, 2008 at 1:23 AM
Message: It's hit and miss. Some of the new features work, but other don't. For example, the T-SQL Debugger and Intellisense won't work with 2005. On the other hand, replacing 2005 SSMS with 2008 SSMS won't hurt you (you won't loose functionality), so moving your workstation to SSMS 2008 is not a problem

...
Subject:  SSMS2008 cannot replace SSMS2005 for some components
Posted by:  Anonymous (not signed in)
Posted on:  Tuesday, August 26, 2008 at 1:33 PM
Message:  >>
bradmcgehee wrote:It's hit and miss. Some of the new features work, but other don't. ... On the other hand, replacing 2005 SSMS with 2008 SSMS won't hurt you (you won't loose functionality), so moving your workstation to SSMS 2008 is not a problem.
<<
In fact, SSMS2008 cannot work with 2005 Integration Services, or Reporting Services (and perhaps more) so you WILL need SSMS2005 around for as long as you need to reference earlier SqlServer components.