Tell me more ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.
up vote -1 down vote favorite

I have already SQL Server Management Studio 2008R2 on my local machine. I just installed SQL Server Management Studio 2005 and wanted to connect for the first time. After going through the following steps

-> Open SSMS 2005
-> In Connect to SQL Server Dialogue
    -> Servername dropdown(select browse for servers)
    -> Select Network Servers tab
    -> Wait for some time the you will see the SSMS 2008 R2 instance
    -> Database Enginer tree view is expanded
    -> Selected the instance which is showing my computer's name and appended \SQLEXPRESS to it.
-> Selected windows Authentication mode
-> Hit connect button

Then I'm seeing a popup saying

TITLE: Connect to Server
------------------------------

Cannot connect to PAVANKUMARRAO-N\SQLEXPRESS.

------------------------------
ADDITIONAL INFORMATION:

This version of Microsoft SQL Server Management Studio Express can only be used to connect to SQL Server 2000 and SQL Server 2005 servers. (Microsoft.SqlServer.Express.ConnectionDlg)

------------------------------
BUTTONS:

OK
------------------------------

How to connect to SSMS 2005 without uninstalling SSMS 2008 R2?? Please suggest a solution. Thanks in advance.

share|improve this question
3  
Why do you want both SSMS 2005 and SSMS Express 2008 R2? If you want Management Studio Express you should get the most recent version, not the 2005 version. And you aren't going to have much luck using both the full version of SSMS and the Express version. – Aaron Bertrand Jun 22 '12 at 15:36
Just wanted to see whether I'll be getting Copy Database option. You said that execute script in target empty db but on the hosting server why I don't know but I was unable to execute scripts. But it is allowing me to copy, export, create tables. – windson Jun 22 '12 at 15:41
3  
The Copy Database option is missing because it's not supported against Express. It has nothing to do with trying 15 different versions of Management Studio. You could have backed up the database in 30 seconds, why not just do that? – Aaron Bertrand Jun 22 '12 at 15:42
2  
@windson I assume this is something that you're hoping will provide a workaround for the problem presented in the answer to your other question. Unfortunately the issue lies with the server and not the tooling. You'd have to "downgrade" your SQL Server Express version to even attempt this. Given the LOE on that task, why not follow Aaron's advice and backup/restore?? – swasheck Jun 22 '12 at 15:46
2  
So your host does not provide you a way to supply a .bak file other than on their local hard drive? I'm sure there is a way to FTP the file. And if not, then you also got another suggestion: generate a script for the database ("Generate Scripts" is on that very same context menu). This should be especially easy since you've already stated the database is empty. You generate the script on your local database, then you copy and paste it into a query window for the hosted database. Hit F5, voila, you're done! No installing 15 versions of Management Studio trying to work around the "problem." – Aaron Bertrand Jun 22 '12 at 15:52
show 1 more comment

2 Answers

up vote 2 down vote accepted

May be this MSFT Kb will give you some idea

share|improve this answer
1  
Workaround: Install the correct product. – swasheck Jun 22 '12 at 15:47
up vote 8 down vote
+250

Presenting Symptom

You're attempting to connect to a database server (SQL Server 2008 R2) with a previous version's tooling (SQL Server 2005). Unfortunately, SSMS is not particularly forward compatible in this case. The answer to this problem is to install the correct tooling for the product that you're actually using (SSMS for 2008 R2).

Solution to the Presenting Symptom

Use SSMS appropriate for SQL Server 2008 R2.

Actual Problem

Having said that, it appears as though you're attempting a workaround to your initial question which has a perfectly satisfactory answer even though it doesn't get what you want because it is a feature of a SQL Server version that you do not have installed - not the client tools.

Solution to the Actual Problem

Spend less time trying to work around versions in an attempt to use GUI tasks, and follow the advice of the well-known, well-respected users who've attempted to help, through either:

  1. Generating the database scripts since it is reported to be an empty database
  2. Backing up and restoring the database (WITH MOVE, of course if it's going to a different location)
share|improve this answer
+1 Couldn't have put it better myself ;-) – Mr.Brownstone Aug 24 '12 at 19:54

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.