July 17, 2010 at 1:55 am
Hi All
Could somebody tell me "How Can we identify from SQL SERVER SETUP files(Installation CD/DVD) whether it is 32 bit or 64 bit "?
And Same "How Can we identify from SQL SERVER SETUP files(Installation CD/DVD) whether it is Enterprise Edition or Standard Edition "?
Regards
Ghanshyam
July 18, 2010 at 9:53 pm
Well if the installation files are on the cd/dvd - then reading the label on there should get you there 🙂
otherwise - looking at my sql dvd here, i have 2 folders
x86
x64
ia64
x86 would be 32 bit, x64 would be 64 bit?
Have you thought about just running the setup or reading the readme file?
--------------------------
I long for a job where my databases dont have any pesky users accessing them 🙂
July 20, 2010 at 4:02 am
For SQL Server 2008 (and 2008 R2) you cannot tell from looking at the media if you are installing a 32-bit or 64-bit version of SQL Server. Neither can you work out if the media applies to Standard or Enterprise Edition (Or Web, Workgroup, or Data Centre editions).
For Express Edition there are separate 32-bit and 64-bit install media downloads, but other editions have a common media for X86, X64 and Itanium.
If you install to a 32-bit server, then the install program will only ever try to install a 32-bit version of SQL Server. If you install to a Itanium server, then the install program will only ever try to install a Itanium version of SQL Server.
The fun starts with installing on a X64 server. By default, the install program will install a 64-bit version of SQL Server. If you add the /WOW parameter for a command line install, then the install program will install a 32-bit version of SQL Server on a X64 (64-bit) machine.
The edition you install is controlled by the PID value you provide. Some sets of install media come with a PID baked in, but you can override this with your own PID providing it is for a compatible edition of SQL Server. Other sets of install media always require that you supply a PID. You must also supply a PID that is compatible with the media. Even though there are no visible differences between the Web install media and the Standard/Enterprise media, putting a Standard Edition PID into Web media will get rejected.
The fact that you can supply either a Standard Edition or Enterprise Edition PID at install time implies that the edition is baked into some critical binaries. I have not noticed any size difference in the binaries, but I am sure that comparing the contents of the binaries would identify which ones have the edition baked into them, and what the differences are. I find it good practice to put the install media for each edition into separate folders, and include the edition name as part of the folder name.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply