I need to max out on RAM somewhere around 3 to 4 GB and I am using SQL 2000. Standard SQL 2000 RAM is limited to 2 GB. SQL Enterprise 2000 is maxed out around 32GB and it cost is $1K. I need to purchase a Windows based SQL package but I can't find the specs on SQL Standard 2003 (which is ~$700) to compare.
What is the Max RAM for SQL Standard 2003?
Which is a better purchase relative to RAM?
What O/S is recommended as this also limits RAM usage?
We are upgrading a production database server to new hardware. The server is currently running SQL Server 2000 Standard Edition. We are thinking about installing SQL Server 2000 Enterprise Edition, however that would mean the test server (2000 Standard) and production server (2000 Enterprise) have different edtions of SQL Server. How much of a risk does this present? Later in the year we would upgrade test to SQL Server 2000 EE, but for a couple of months the environments would be different.
I have kind of an urgent need here. I need to know if there is a dll file or registry key or something of that nature that I can query on to find out if my SQL 2000 installations are Enterprise or Standard.
I understand I can do this using query analyser, but that will not work with my reporting tool (this is for reporting numbers of SQL installations in our very large enterprise for Microsoft license compliance).
I'm after some advice, I am looking for the best way to do this:
I have a SQL 2000 Clustered Virtual Instance which is of course Enterprise Edition as it is clustered. I need to upgrade to 2005, but dont need the 2005 Enterprise features, Standard will do, as this supports clustering.
The restrictions are that you cant upgrade 200Ent to 2005Std.
As this is a fairly complex environment, it has a default instance running on node 1 and a named instance running on node 2 I dont particularly want to uninstall both 2000 instances, and then install new 2005 instances
So is it possible to upgrade to 2005 ent, and then downgrade to standard. I have seen a suggestion without any details, that there is an undocumented sp, sp_update_resume, that might do this. Does anyone know about this
Or does anybody have any other suggestions. (the names of the instances have to be the same, as the existing instances)
Hi, One of our main servers running on SQL Server 2000 Enterprise edition which has transactional replications on it which replicates to other servers running on the SQL Server 2000 Enterprise edition as well.
Due to Hardware problems the server is being migrated to a new machine but the client has installed SQL Server 2000 standard edition on the new machine.
We will be using a two processor cpu with 4GB RAM and we are also not planning about clustering. Is there any problem if i migrate the server in Standard Edition will the replications work properly between Standard and Enterprise editions.
What other complications can be there if i switch over to standard edition from enterprise edition
I am looking for some recommendations for memory sizing and options for a SQL 2000 Cluster. This is a two node cluster built on Windows 2003 ENT SP1 (x86). Both the nodes have the following hardware:
- 4 x Dual Core AMD Processors - 16 GB Memory - EMC Shared Disk
We are running six SQL 2000 instances and don't expect each of these instances to use more than 1.7 GB of memory. All these instances are going to support BizTalk 2004 Databases. I already have /PAE enabled on the nodes. I am looking for the following answers:
- Do I need to enable AWE on all the instances even if the instances ? Currently, we don't have that enabled and we have seen some issues regarding excessive paging even when there is physical memory available. The DBAs think that we don't need to enable AWE. I am bit confused on this one.
- We normally run 3 instances on each node and would like size the cluster in such a way that it can take six instances in case of a node failure
Will it be possible to do an in-place upgrade from SQL 2000 Server Enterprise SP4 32 bit running on top of 64 bit Windows 2003 Enterprise , clustered, to SQL 2005 Enterprise 64 bit? The 32 bit SQL 2000 to 64 bit SQL 2005 in place upgrade seems questionable to me... Anybody tried anything like this?
Hi there Our ISP hosts our data on SQL Server Enterprise, but I also going to host the databases on my local machine. As it's just local would Standard edition do? If I migrate the databases over, will it work? Thanks in advance.
I am currently running SQL Server 2000 Standard on my production system, and I am looking to upgrade the system to Windows 2000 Adv. Server. I would also like to upgrade SQL Server 2000 Standard to SQL Server 2000 Enterprise to utilize more than 2GB of memory. Can anyone tell me what is the best way to upgrade the system, and please provide some feedback on your experiences with the upgrade. Thanks in advance.
We got SQL Server 2000 Standard Edition SP3 running on Windows 2003 Standard Edition server.
Now, we would like to apply windows 2003 SP2 to the Operating System.
We are concerned that whether windows 2003 SP2 is compatible with SQL server 2000 (SP3)?
I was looking at the application compatibility chart for Windows 2003 SP2.Among them Microsoft SQL Server Standard (2000) was listed but with no Service pack details. And also does Standard means standard edition there?
My Question - Is windows 2003 server SP2 compatible with SQL Server 2000 (SP3) Standard Edition? And what if I plan to apply SP4 to Sql Server ?
How do SQL 2000 service packs play a role in upgrading? That is, can SQL 2000 Standard with no Service Packs(SP) be upgraded to SQL 2005 Standard, or does SQL 2000 Standard have to have a certain service pack??
Here I need some help or suggestions for the following topic...
I am using SQL server 2000 enterprise edition installed on the machine. Now I wanted to change the edition from enterprise to standard. There are around 4 user databases exists on the server. What are the areas I have to take care while doing this? Could I do as normal installation? No log shipping implemented on the server.
Is SQL Server 2000 Standard an option for a web application ? OR Only Enterprise version should be used for a web application because the standard version cannot support fully a web application?
is SQL Clustering possible with Windows 2003 Standard Edition? I have read, we need Enterprise Edition but it is too expensive. is there any alternate solution?
Does anyone know if it is possible to go from the Enterprise edition of SQL, back to Standard?
In other words, Enterprise Edition is installed, but what we really want is Standard. Is there any way around this, other than uninstalling and reinstalling SQL?
if one has purchased enterprise edition of sql server, could he install the standard version instead of the enterprise one without violating software license?
How are you, I was wondering if I could uninstall and reintall sql server standard and upgrade to enterprise edition.
What i mean..
We have 10 computers running sql server standard. We want to upgrade them to enterprise edition bc there are another 10 machines with enterprise.
Would we have to uninstall standard edition before installing enterprise. Or could we just install enterprise edition over standard
Has anyone done this? Compatibilty issue?? We are doing it remotly as well, some machines in NC, some in Vegas, some in Cali. So all will be done through RDC.
I am trying to do a new install on Windows Server 2003 R2 (32 bit). I have a disk (DVD) that contains SQL 2005 Standard edition in two folders, Disk 1 and Disk 2. It also has SP1 in a third folder.
First, it will not auto-play. I can find the "splash.hta" file, and when I run it, I get the splash screen that says SQL 2005 install, disk 1 of 2. If I use the options that I was told to by my electronic medical record software company, the installation begins and goes ok. It installs about 2/3 of the components, and then says "Please insert disk 2." I do not have a second disk!!
I even tried copying each folder, Disk 1 and Disk 2 to two separate CDs and tried to install that way. I still get "Please insert disk 2" and the installation will not complete?
What's the best/easiest method to upgrade from Standard Edition to Enterprise Edition and still keep the databases in tact?
My thoughts were to: 1)Backup databases 2)Detach User Databases 3)Uninstall Standard 4)Install Enterprise 5)Restore Master and msdb 6)Reattach the User Databases
Recently, I worked on installing SQL Server 2000 into a clustered environement. I installed the Standard edition, tested it, and everything works fine. However, in reading some information on Enterprise Edition from Microsoft, I see where it says to install Enterprise Edition when using a clustered, or failover, environement. Can anyone give me a layman's explanation as to why this is? Everything is functioning just fine with the Standard Edition installed.
I really don't want to re-install if I don't have to.
Does any one know if the Standard or Enterprise version of SQL Server 2K allows Maintenance Procedures like "DBCC CHECKDB REPAIR_REBUILD" to execute with users logged in, without the requirment of single user mode on the Database?
I'm setting up a new system and want to do a cluster. We have Win2k3 Enterprise already. My question is do you have to have enterprise edition of SQL2K to do clustering w/ win2k3?
I have a question. I want to migrate from mySql to Sql Server, and I should decide which version will I use. The problem is that I need partitioning, and it is included only in the Enterprise version. But the Enterprise version costs 5 times more than the standard and the workgroup version. Is it worth to spend so much money only for the partitioning? Also, maybe I am wrong, and the partitioning is also included in the Standard version?
Mustrum Ridcully writes "Sitting here at work trying to figure a way to find wether SQL server is Enterprise or Standard edition. Submitting this question won't probably help much as I have to deliver report in about 30min. Nevertheless, somebody might benefit from this information in the future.
