Sql Server 2005 Not Compatible with Windows 10 - sql-server-2005

I had SQL Server 2005 working when I upgraded to Windows 10. Now it won't work. I read that it is not compatible with Windows 8, according to Microsoft. Windows 10 is but the matured version of Windows 8, to me. Is there any way I can get SQL Server 2005 to work with Windows 10?


Have you tried to apply / re-apply SP4? I'm not saying it will work but it works in Windows 8. Not sure what you upgraded from.
This may help .. https://www.youtube.com/watch?v=cj859zcWhEM


uninstall inFlow before upgrading to Windows 10 and then re-install (because of compatibility issues with SQL Server 2005). This is pretty easy and can be done from the START menu by searching “Programs and Features” and once open, choosing to uninstall inFlow Inventory.
Not sure which version of SQL you’re using? You can check the version of SQL Server through the START menu by searching “Programs and Features.” In that window, look for “Microsoft SQL Server” and check the version (it will either be 2005 or 2008 R2). If you’re in 2008 R2 or 2012 you’re golden, no extra steps required).
So bottom line: if you’re planning to take advantage of the upgrade from Windows 7 to Windows 10 that’s great, but take a few minutes to double check your SQL Server version (as noted above) before you upgrade. Most of us won’t be affected but if you don’t, the upgrade could break inFlow and that’s no fun at all!

Related

Can't install SQL Server 2005 on Win10 x64

I'm trying to install SQL Server 2005 on my Win10 x64.
The problem is I can't even select the Database Services and Reporting services I need cause checkbox is disabled.
I had a bit research on this issue but everyone else seems to have problems after the installation began, whereas, I can't even start the progress.
I tried Run program made for previous versions of windows and extract then install sqlncli.msi from SP4 according to this.
Neither of them enable the checkboxes and I'm running out of ideas.
Should I install sp4 without install SQL Server first? Any suggestion would be appreciated.

I had the Visual Studio subscriptions and turns out you can still download the original version of SQL Server 2005 by downloads search(autocomplete won't show it but the search result will).
And the checkboxes are enabled in this version.
If you face problem during the installation, this works for me.

Problem uninstalling SQL Server 2005

I have a problem with SQL Server 2005.
I have a Computer with Windows 7 x64 bits installed and I want to run SQL Server 2005 correctly. The first time I try it, i did the follow:
1) Install SQL Server 2005
2) Install SQL Server 2005 Service Pack 3 x64
And it works!
But now (for reasons that are irrellevant) I need to uninstall all and re-install again to check the steps.
So I went to Add/remove programs of Windows and uninstall all the SQL Server things that I found. After, I did the same steps that I said before, but... it didnt work! What's going on?
I saw that the uninstall of SQL Server 2005 seems that it didnt go well because i can find the instance of SQLExpress... and i read that Service Pack of SQL Server cant uninstall.
But... how can remove ALL SQL Server 2005 things, to start again the installation like i did the first time?
Thanks

If you want to know how to remove the instance you can see here how to do it manually. Another resources is here and here.

Sql server 2005 and windows 7

I have the symptoms in this articles, but I have Windows 7 32 bit, and "Group Policy Management Console" dos not work install due to compatibility problem so I can't follow the tutorial. Can you help me running SQL server 2005 ?
http://support.microsoft.com/kb/941823
Thanks

My life become easy when I install Developer Edition!! obviously Enterprise Edition can't work with Windows 7.
If the client components fail to install, try to use "Change" button in "Add and remove programes"

SQL Server 2005 - clicking on job->Properties yields "New Job" window

Recently, I've started having a problem with my SQL Server 2005 client running on Windows XP where right-clicking on any job and selecting Properties instead brings me to the New Job window. Also, if I select "View History", I get the history for all jobs, instead of the one I right-clicked on.
This happened to me once before, and I found that I hadn't installed a service pack for SQL 2005. Once I installed it, the problem went away, and I haven't seen it in about a year. I haven't run any updates on it since, and I'm not sure what could have caused this.
As a possibly related note, I've tried installing XP Service Pack 3 on my machine twice, and it just hung on my machine(I started running it on Friday before leaving for the weekend, and it hadn't gone more than5-10% when I got back on Monday). I'm not sure if that fact is related at all, but I thought it possible that the XP update somehow overwrote something that SQL 2005 used before hanging.
Any ideas on what could cause this? I've included the current version info that shows up in SQL 2005.
Microsoft SQL Server Management Studio - 9.00.1399.00
Microsoft Analysis Services Client Tools - 2005.090.1399.00
Microsoft Data Access Components (MDAC) - 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML - 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer - 7.0.5730.13
Microsoft .NET Framework - 2.0.50727.1433
Operating System - 5.1.2600
Update: I reinstalled SQL 2005 service pack 2 on my machine and it fixed the problem. I'll have to see if the problem was caused when I tried installing xp sp3.

I would suggest the following path:
Make sure that you have current backups for the server
Try to get a clean install of the XP service pack
Try reinstalling the client tools on the machine
If that fails, try to install (or reinstall) SP2 for SQL Server

SQL Server 2005 and 2008 on same developer machine?

Has anyone tried installing SQL Server 2008 Developer on a machine that already has 2005 Developer installed?
I am unsure if I should do this, and I need to keep 2005 on this machine for the foreseeable future in order to test our application easily. Since I sometimes need to take backup files of databases and make available for other people in the company I cannot just replace 2005 with 2008 as I suspect (but do not know) that the databases aren't 100% backwards compatible.
What kind of issues would arise? Do I need to install the new version with an instance name, will that work? Can I use a different port number to distinguish them?
I found this entry on technet: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3496209&SiteID=17
It doesn't say more than just yes you can do this and I kinda suspected that this was doable anyway, but I need to know if there are anything I need to know before I start installing.
Anyone?

Yes this is possible. You will have to create a named instance not used by another version of SQL Server as per the previous answer and version 3.5 of .Net installed. Works great!!
Here the list of prerequisites:
.NET Framework 3.5 SP1
Windows Installer 4.5
Windows PowerShell 1.0

If you have Visual Studio 2008 installed you will get a validation error and you cannot install SQL server 2008 until you install Visual Studio 2008 SP1. If you don't have Visual Studio 2008 installed it should not be a problem. So if you do have Visual Studio 2008 wait till August 11th since that is the day that Visual Studio 2008 SP1 will ship

I believe that this is perfectly possible. I am currently running both SQL Server 2000 and SQL Server 2005 on my development server while I transfer applications over.
The only thing you will have to do is create a new instance which isn't already being used by SQL Server 2005.
As with anything new, there will probably be some bugs, however, it should generally "just work".

my experience is after having sql sever 2005 and 2008 on same machine SSIS 2005 does not work properly... specially with script task, data flow and sequence container

You could run just SQL 2008 as the single instance and then attach/create databases with compatability level of 2005? The problem with that is that its a theory. Im not 100% positive that if you create a database on 2008 , with a compatability level of 2005, and then detach it, that a SQL 2005 instance is capable of attaching it.
I think its a good enough chance to try though. But I agree with the previous answers, the multiple instance options will work fine.

Unfortunately, it seems SQL Server 2008 Client Tools requires Visual Studio 2008 SP1, and I'm loath to install a beta of this on my main development machine.
I'll wait until SP1 is RTM before I move on.
Edit: Yes, I do have Visual Studio 2008 on this machine, but I'd like to avoid beta installations of debugger applications. They tend to dig themselves too deep in for my taste.

I have try it with negativ result. The 2k8 installation breaks with a mysterious error-message. The installation-protocol looks fine, but it will not work. After this the 2k5 installation was buggy too.
The 2k8 installation was half-ready, so it´s already in controlpane / software, but uninstallation is not possible.
So my result - don´t do it on a productive server / workstation. If you need both versions, use a virtual machine instead.