Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
 Posted - 2009-02-12 : 13:06:10
|
| the meat: Can you install SQl 2005 64 bit Standard Edition on a Windows 2003 Sp2 64 bit Enterprise Edition OS?I can't see why not, but when running the SETUP.EXE, I only have the option on FEATURE SELECTION to install CLIENT COMPONENTS, and DOCUMENTATION, SAMPLES, AND SAMPLE DATABASE. No option to install DATABASE ENGINE, etc.Reading the requirements in BOL[SQL Server 2005 Books Online (September 2007) Hardware and Software Requirements for Installing SQL Server 2005 ], I get:Operating System Requirements (64-Bit)This table shows the operating systems that run the server software from each 64-bit version of SQL Server 2005. For information about how to install SQL Server 2005 on Windows Server 2008, see the list of known issues knowledge base article.The option if the grid shows: Yes4and bulletin 4 says: 4-Tools native/WOW64. For more information on WOW64, see Extended System Support.So, how now? Can I only install tools, abd have to install the DB engine on WOW64? Or only client tools? In which case, I think I need to get the server rebuilt with Standard Edition OS, and go with that.tia*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2009-02-12 : 13:36:41
|
| Should be no problem. I have a SQL 2005 64-bit standard cluster running on a pair of Windows 2003 64-bit servers. Been way too long since I did that install to remember the gory details, though. |
 |
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2009-02-12 : 13:55:45
|
hmm - if that is correct, then I can only assume that the aborted install by the server engineer has left the server in an iffy state. Still, the image from the install clearly only gives me the option for client and documentation. *##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2009-02-12 : 15:05:58
|
| you don't have a client only install CD, do you? It should have a "Servers" directory on it, if it is the full DVD. |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2009-02-12 : 15:52:14
|
| I'm working from the install files provided - no Cd/DVD. Didn't get the files from MSDN myself. must admit, that isn't an option I had considered. I was told they were used for the previous install, before the server had got trashed. This client has been used to having a SQL site license, and have up until now always just gone with Enterprise Edition.*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2009-02-17 : 06:06:27
|
| RESOLVED:Looks like I found the issue – the VL (Volume Licensing) version files have 2 self-extracting exe, and they must be extracted to DIFFERENT locations, (nothing specifying that anywhere in a readme.txt or installation guide). Because I was extracting them to same location, the 2nd exe was overwriting the 1st setup exe with it's own setup.exe. That seems to be an oversight from the provision point of view – a simple readme.txt would have helped (I hope there wasn’t one that I didn’t see).*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
|
|
|
|
|
SQL 2005 64 bit Standard Edition supported OS?