| Author |
Topic |
|
DBADave
Constraint Violating Yak Guru
366 Posts |
 Posted - 2005-10-07 : 12:17:58
|
| I've read the documents regarding how many processors and how much memory each edition of SQL Server can handle. What I would like to know is will I see a performance gain with using SQL Server 2000 Enterprise Edition on a server with 4 processors and 4GB memory (2GB OS and 2GB SQL) vs. using SQL Server Standard Edition. Will EM better handle 4 procs than Standard?Thanks, Dave |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2005-10-07 : 12:30:58
|
| I think you mean EE, and no I don't believe so. And you should not manage the memory they way you have layed out. Let SQL Server manage all of it.Brett8-)Hint: Want your questions answered fast? Follow the direction in this linkhttp://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx |
 |
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2005-10-07 : 13:02:10
|
| You are correct. I meant EE. Regarding the memory, 2GB OS and 2GB SQL Server is what I will get with Standard Edition so SQL Server will be managing the memory. If I choose Enterprise Edition I may not enable the 3GB memory initially. If that's the case by default it can only handle 2GB (actually a little less to be technical).Thanks, Dave |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-10-07 : 13:13:36
|
| There is no performance difference between the two versions. If you want to take advantage of any of the features in EE or use the extra hardware that EE supports, then I'd go with EE. Otherwise, just use SE.Tara |
|
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2005-10-07 : 14:48:31
|
| Thanks Tara. There is a small chance we may explore using log shipping for DR. If we do, then EE would be needed. Unfortunately it's too early for me to know if we will be pursuing this option and my knowledge of log shipping isn't too great. It looks like a good DR approach, but I haven't investigated any potential issues involving log shipping.Dave |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-10-07 : 15:06:13
|
| It is an excellent DR solution. We use it between our two sites. Tlogs every 15 minutes. We then use clustering for problems at the one site. The two solutions together get your pretty close to a bunch of 9s.Tara |
|
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2005-10-07 : 15:18:43
|
| How do you handle SQL Server configuration changes. Do you have procedures indicating that any change to a production server must immediately be made to the server at the DR site?Dave |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-10-07 : 15:25:27
|
| Log shipping handles everything inside the database. Everything outside of that is copied over within 2 business days.Tara |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-10-08 : 04:40:14
|
"pretty close to a bunch of 9s." - now you're getting all technical Tara!Kristen |
|
|
|
scullee
Posting Yak Master
103 Posts |
Posted - 2005-10-08 : 04:55:19
|
| You can do log shipping without EE, you just have to do it manually with scripts (you can find them on this site if you search). The only thing i can think that EE will give you is indexed views being automatically included in query plans without hints. Its a lot of $$$ for not much return if you only have the 4gb ram. |
|
|
|
|
4 Procs & 4GB Memory - SQL Enterprise or Standard?