I've SQL Server 2008 Express installed. I've just download and installed SQL Server 2005 Express, but I changed the name of instance into SQLEXPRESS2005 (I added 2005 at the end to avoid conflicting names).
Unfortunately, when I try to access the 2005 instance either using the SQL Server Management Studio or the VWD 2008 Express (Database Explorer window), I don't see it.
I just disk-recovered my system, so I lost many of my files. But, before that, I had both versions, one having 2005 as instance name.
So here are the summary of the issues:
I was able to download and install successfully the Express 2005
When I try to connect to a server, I only see.\SQLEXPRESS as option (there's no SQLEXPRESS2005)
When I try to connect from the VWD, I get the Server not found ERROR!
I can see the SQL SERVER 2005 icon on the Control Panel window. But, when I try to
uninstall it, I get a error message telling that this program is not found
When do Start -> All Programs, I can see the The Microsoft SQL Server 2005 folder
It's really strange as I was successfully able to install both versions before I experienced problem with my system.
Thanks for helping.
Do you see the service for the SQLEXPRESS2005 instance? If it isn't there then the instance doesn't exist and you'll need to reinstall.
Related
I have a very fundamental and basic SQL question. Using Microsoft SQL Server Management Studio Express, how do I create my first Server? For that matter, how would I create it using any other required software tool?
I took a look at Sql Server Configuration Manager and I saw SQLEPRESS running as a SQL Server. But when I added that in to the start up widow for MSSM Studio Express, as the server name, it threw an error saying it cannot be found or does not exist. It seems that this is not the right kind of server.
To connect to the local instance of SQLEXPRESS, you will need localhost as the server name.
This is a fairly comprehensive guide on how to create a database once you have connected. All the steps won't apply to using SQL Express, but the gist of it is there.
In Object Explorer, connect to an instance of the SQL Server Database
Engine and then expand that instance.
Right-click Databases, and then
click New Database. In New Database, enter a database name.
To create
the database by accepting all default values, click OK; otherwise,
continue with the following optional steps.
Based on this comment:
Trying .\SQLEXPRESS in SQL Server Management Studio Express throws an error that says that "This version of Microsoft SQL Server Management Studio Express can only be used to connect to SQL Server 2005 servers". So this is the problem, I think.
.\SQLEXPRESS is the correct server name, but you have the wrong version of client tools (SQL Server Management Studio). To find out the version of SQL you are connecting to, there are a number of suggestions here: https://www.mssqltips.com/sqlservertip/1140/how-to-tell-what-sql-server-version-you-are-running/
But since you can't connect yet the easiest thing to do is go searching for sqlserver.exe, right click, properties, version. If you have multiple version you need take note of the folder that it's in and check the SQLExpress one. You can also check in services.
Once you've worked out the version, download and install just the management tools for that version.
I always seem to battle with this so on my new Windows 7 dev PC build, I thought I'd try and get it right!
Do you install VS 2008 first and then SQL Server 2005 developer or the other way around? And for either way, are there any special options/settings that have to be enabled/disabled?
I've just take an Acronis image of my PC, configured IIS for use with SQL Server 2005 (see below) and proceed to install SQL Server 2005 developer. It's warned about SQL Server 2005 needing SP3 (no problem) but it's also warned about VS 2005 not been compatible. Can I ignore this and go ahead and install VS 2008?
Cheers, Rob.
PS. The page to configure IIS features for use with SQL Server 2005 is http://support.microsoft.com/default.aspx/kb/920201
I always install in the following order
IIS
Windows Installer
Sql Server
VS any version
whenever i tried to go the other way, i always faced a problem approx thrice i faced this problem. Usually some components becomes missing in other way
When I try to create a new Maintenance Plan in SQL Server, I get the following warning:
The action you attempted to perform on
a remote instance of SQL Server has
failed because the action requires a
SQL Server component that is not
installed on the remote computer. To
proceed, install SQL Server 2005
Management Tools on the remote
computer, and then try again. For more
information, see "How to: Install SQL
Server 2005 (Setup)" in SQL Server
2005 Books Online, or find the article
on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083
. (ObjectExplorer)
However, the tools are installed, AFAIK. I'm connecting to the local machine. Here's a screenshot of both the error message alongside SQL Server telling me it won't install the management tools because they are already there.
(previous step here)
Any ideas?
Ah - nevermind on this. The response is simply a bit misleading. It's only complaining about part of what I was asking to install. When I decided to progress, it did in fact install some things.
I applied SQL Server 2005 SP2 and marked all the components to be updated, including Client tools, but the version in the Help -> About box still has version 1399, while the server does indeed had 3042.
I then re-applied SP2 to only Client tools, and everything ran successfully (again, first time did too) but still, no version update for management studio.
Now, I just applied SP3 with everything successfully, but still management studio version did not get updated.
How can I update it? Or at least how can I uninstall just Management studio so I can install it from a newer DVD?
Thanks.
If you go to Control Panel > Add Remove programs and then choose the appropriate SQL Server installation, this will start the typical install wizard for SQL Server.
You can then select the specific components that you wish to uninstall.
If you are having difficulties with SQL Server 2005 Service Pack 3 may I suggest that you visit the SQL Server Central forums as there are a wealth of resources for SQL Server SP3. It was actually due to user demand from this forum that resulted in there even being an SP3 release.
http://www.sqlservercentral.com/Forums/Forum146-1.aspx
Let me know how you get on.
Cheers, John
I got the Error in sql server sp3 installation log which caused this:
Error Number : 29538
Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
Hate to answer my own question, but I had to manually un-install Client Tools, re-install them using SQL Server 2005 setup, and THEN apply the updates.
It wasn't working by just trying to apply updates over the existing original installation.
And i mention un-installing using the SQL Server 2005 Setup because trying to do it from the Add/Remove Programs dialog won't let you or will give you trouble.
I'm trying to do a SQL Server 2008 setup and I've been given a Cross Language Installation failure. More specifically:
Rule "cross language installation: failed.
the Setup language is different than the language of existing SQL Server features. To continue, use SQL Server Setup installation media of the same language as the installed SQL Server features.
I do not have SQL Server Express installed and I browsed through "Add or Remove Programs" and was unable to find anything that looked like it was a previous version of SQL.
Any tips?
I restarted the setup after facing the same problem, and I realized that man should not close the installation center till the setup process is completed. If you leave it open it will work.
Ensure that you have uninstalled all of your old SQL Server versions. Also you must restart the installer if you have not done that when you began installation.
All I had to do was exit the installer and start the process again. For some reason it worked the second time around.
I had the same problem today when installing SQL Server 2008 Express on a computer that has never had an instance of SQL Server installed.
I found that "Microsoft SQL Server 2005 Backward compatibility" was installed. I removed this via Add/Remove Programs and was able to successfully install SQL Server 2008 Express afterwards.
Change the Current Windows Language interface for the needed language you want to install.
That will make it possible for the Installer to launch the Localized version.
If you've previously installed SQL on the machine (or apparently some RedGate tools) have you checked for any SQL detritus in the registry?
If not then the MS forums have details of some reg keys to look out for, and some of the links are worth following for advice on what to delete from the registry.
On my installation of Sql Server 2008 Express, this was caused by having Sql Server 2005 Express Tools installed while trying to install 2008. Uninstalling 2005 Tools fixed the problem. I was able to keep Sql Server 2005 Express, including Sql Server 2005 Backward compatability; only had to nuke tools.