December 1, 2009 at 8:58 pm
we have sql server 2000 on windows server 2003 planning to upgrade to sql server 2008 on windows server 2008 however the application is not compatibile with sql server 2008 & windows server 2008. If we upgrade to sql server 2005 on windows server 2008 would there be any problem from application? Note application is install on separate application server. or should we go for sql server 2005 on windows server 2003? any suggestion would be appreciated.
December 1, 2009 at 9:20 pm
You have already mentioned that the application is not compatible with SQL 2008 and Windows 2008.
It's better to have a word from the same application team about their view on SQL 2005 on windows 2003 or 2008. I have been working on Windows 2008 for a while and the security related enhancements / features need to be tested with your application.
If your application is using the SQL server (physical machine) and storing any config files and so on.., the security settings on Windows 2008 has to be allowing it. I don't think you will have that many issues from SQL 2005 stand point.
But still, SSIS, Database schemas are some areas you need to discuss with the app team.
Any way as always you would be testing it, which would lead you to more problems and solutions.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
December 2, 2009 at 8:16 am
Thanks for the reply! I have another question; we have third party application and do not have any DEV servers and we are planning to setup a TEST environment. Do we need to have SQL Server Developer edition on it or the one we are going to choose on PRODUCTION server?
December 2, 2009 at 8:25 am
Let me ask this first, what is the edition that you are going to have on Production Servers?
Reason, if you are going to implement a Standard edition, I would suggest you may use the Dev edition because of cost factor, but keep in mind, all features that you may be able to utilize in Dev edition will not be available in Standard edition, so you may be testing, works fine but on production box it may not be available to you.
The following link will give you the features comparison in all the editions.
http://msdn.microsoft.com/en-us/library/ms143761(SQL.90).aspx
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
December 2, 2009 at 9:58 am
Bru brings up a great point. The Dev edition is equivalent to Enterprise, with all features enabled. However if you use something like compression, it may not be there in production.
I thought that licensing would allow you to have the standard edition at no cost for a test server if you used it in production and your development clients had CALs.
December 2, 2009 at 8:11 pm
Thanks all! we are planning to have SQL server 2005 enterprise edition and Database Mirroring (Asynchronous/high performance) now we are planning to first test our application and DB Mirroring in a Test environment. For this we are setting up two Test servers one for application testing and other would be use as a TEST mirror server. I have a question do we need to have Enterprise Edition on both of the TEST servers or Developer edition? my understanding is TEST server should have the same edition as Production server. Will there be any problem if we perform our application test and Database mirroring test using Developer edition on TEST servers and install enterprise edition on production server and migrate database and application. Any feed back would be appreciated.
December 2, 2009 at 8:25 pm
Please find this technet article on Database Mirroring.
http://technet.microsoft.com/en-us/library/cc917680.aspx
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply