Getting an error in SQL Server 2000 Enterprise manager - Please see in the attached screenshot!
Kindly help how to overcome the issue
You have to install the backward compatibility package. You can download it from here.The file is called SQLServer2005_BCxxx.msi
You're trying to access a SQL Server 2005 instance using SQL Server 2000's Enterprise Manager, which isn't possible.
You need to install a copy of SQL Server Management Studio - the 2008 R2Express version should be fine, or you can dig out the 2005 version
I installed SQL Server 2008 R2. Now I want to install BIDS in this SQL Server. Can I install it from this link:
http://www.microsoft.com/downloads/en/details.aspx?familyid=3C856B93-369F-4C6F-9357-C35384179543&displaylang=en
Is this going to work? Thank you!
BIDS is part of the SQL Server Client Tools which will be visible as one of the options when you try and install SQL Server. There is no real need to install it on the server as you can connect remotely.
You can see it here under 'shared features'. Just select that and untick all the other options when running it on the machine on which you wish to install it.
BIDS is not installed on the SQL Server. It is a development environment that uses Visual Studio. You can install BIDS from your SQL Server 2008R2 installation media, but you can also get the express 2005 version from your link. You should be able to connect to your SQL Server using either approach.
I already had the SQL Server 2008 Express engine installed (just the bit that comes with VS 2008 Express). I then installed SQL Server 2005 Express followed by SQL Server 2005 Management Studio Express, all of which seemed to install OK without any errors. However, when I run SQL Server 2005 Management Studio and enter the Server name as machine name\SQLEXPRESS and click Connect I get the message:
"This version of SQL Management Studio Express can only be used to connect to SQL Server 2000 and 2005 servers".
Presumably the instance name SQLEXPRESS refers to the 2008 version, is the 2005 instance a different name, or is it a different problem? Any ideas please, thanks
You are right that the SQL 2008 Express took the 'SQLEXPRESS' instance name. The 2005 toolset cannot connect to 2008. You need to find out the isntance name under which the 2005 VS installed it's Express. Easiest way is to start the Service Manager (run services.msc)and see the instance name there.
Run "services.msc" and check the service name that is running your SQLServer 2005 Express instance. You should use it, and not "SQLEXPRESS" if it is running your SQLServer 2008 instance.
Btw, SSMS 2008 works beautifully with 2005 instances.
Check this link to download SSMS Express 2008. I'm not sure code completion will work with SQLServer 2005 tho.
When I try to install a new instance of SQL Server 2008 Express on a development machine with SQL 2005 Express already up and running, the install validation fails because the "SQL 2005 Express tools" are installed and I'm told to remove them.
What exactly does that mean?
After reading this article:
http://www.asql.biz/Articoli/SQLX08/Art1_5.aspx
I uninstalled the 2005 version of the SQL Management Studio but received the same error from the 2008 installer during my follow-up attempt.
Updates
1) Uninstalled the SQL 2005 Management Studio only. Received the same error from the 2008 install.
2) Removed all SQL 2005 common components. Received the same error from the 2008 install.
3) Installed the shared components from the SQL 2008 installation program. Received the same error from the 2008 install when trying to install the new SQL 2008 instance.
4) Uninstalled SQL 2008 components, rebooted, re-installed SQL 2005 Management Studio from installation media, rebooted, un-installed SQL 2005 Workstation Components from Control Panel, re-booted.
Installation of SQL 2008 is now proceeding as it should.
Seems likely that if I'd re-booted after update 2 above things would have gone more smoothly. :-(
Although you should have no problem running a 2005 instance of the database engine beside a 2008 instance, The tools are installed into a shared directory, so you can't have two versions of the tools installed. Fortunately, the 2008 tools are backwards-compatible. As we speak, I'm using SSMS 2008 and Profiler 2008 to manage my 2005 Express instances. Works great.
Before installing the 2008 tools, you need to remove any and all "shared" components from 2005. Try going to your Add/Remove programs control panel, find Microsoft SQL Server 2005, and click "Change." Then choose "Workstation Components" and remove everything there (this will not remove your database engine).
I believe the 2008 installer also has an option to upgrade shared components only. You might try that. Good luck!
In my case even after uninstalling all 2005 related components it didn't worked. I had to resort to a brute force way and remove following registry keys
32 Bit OS: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90
64 Bit OS: HKLM\Software\Wow6432Node\Microsoft\Microsoft SQL Server\90
I had to unistall the Workstation Components and SSMS Tools Pack (SSMS Tools Pack is an add-in for Microsoft SQL Server Management Studio (SSMS) including SSMS Express.)
Installation of SQL 2008 is now proceeding as it should.
The problem is that SQL 2008 MS has a bug where connecting to a remote server (say like a service provider collocation) it will always try to open the fist db in the list, and since the possibilities of been ur db the first on the list are really low, it will throw and error and fail to display the list of dbs... which using sql 2005 management studio it just works.
Wished I could use SQL 2008 MS, but looks like as far I connect to remote SQL 2005, SQL 2008 is out of the question on my dev machine :(
Just Remove the the Workstation Components from Add/Remove Programs - SQL Server 2005.
Removing Workstation Components, SQL Server 2008 installation goes well.
Simply remove the Microsoft SQL Server Management Studio Express 2005 from control panel
N.B. These notes are for SQL Server Express 2008 R2 (so Microsoft still haven't made this any easier). I also realise that I complicated things by installing 32-bit SQL Server Express 2005 and 64-bit SQL Server Express 2008.
I followed the steps by Josh Hinman above. Uninstalling the SQL Server Express 2005 "Workstation Components" was not enough. I required an uninstall of the 2005 Management Studio as well.
I also tried the Upgrade route that Josh Hinman suggested by clicking on the 'Upgrade from SQL Server 2000, SQL Server 2005 or SQL Server 2008'. This route never gave me the option of installing the components side-by-side it just went straight through the process of upgrading from 2005 to 2008. It completed successfully - but hadn't actually done anything. Thankfully though it hadn't harmed any existing database instances. So be warned trying that route.
If you currently have Red Gate SQL Toolbelt, you will need to unistall that too before continuing. Somehow it adds a reference to the 2005 version of the SQL Management Studio.
I'am trying to install SQL SERVER developer 2008 R2 alongside SQL SERVER 2005 EXPRESS,
i went to program features, clicked on unistall SQL SERVER 2005 EXPRESS, and only checked, WORKSTATION COMPONENTS, it unistalled: support files, sql mngmt studio
After that installation of sql 2008 r2 developer went ok....
Hopes this helps somebody
I also had to remove the SMSS before it would get past that step.
I've got a problem on an SQL Server 2005 Express instance, and I need to see exactly what is being run, since what I believe is being run works fine when I run it from Management Studio.
It appears that Profiler is not available for SQL Server 2005 Express. When I attempt to run SQL Server 2000 Profiler against the 2005 Express edition, I get the following message : "To Connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO)." However, in searching Express Management Studio for a menu to do something similar to what I need, I can't find anything. I found a third party profiler knock off for Express, but prefer to not to install a client app on my customer's server.
How do you find out what is being run in SQL Server 2005 Express?
I use this sql server profiler. Its free, its open-source.
You can use xSQL Profiler from http://www.xsqlsoftware.com/Product/xSQL_Profiler.aspx
It's free for up to 2 instances.