November 1, 2004 at 12:22 am
Hello.
I plan a hardaware upgrate for the company that i work.
Now We have 55 licences for SQL7.
The cost to upgrate the software to SQL2K is 3 times grater than the hardware cost.
I Thing (because tight budget) that is good idea to do this upgrates in two pass.First buy the server and later to buy SQL2K.
I don't know if it is good idea to use SQL 7 on a new Server (2 CPUs , 4Gb ram etc.) with OS WIN2K Server or WIN2K3 Server. Will I have any problem like Performance ,incompatibility or somthing else?
Thank You
November 1, 2004 at 2:19 am
Personally, given the imminent release of SQL2005 I would not upgrade SQL Server just yet.
November 2, 2004 at 2:03 am
... and SQL Server 7, doesnt run on Windows 2003
November 2, 2004 at 2:18 am
Not quite right!
It does run, however it is not supported. See here:
http://www.microsoft.com/sql/howtobuy/windowsnetsupport.asp
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
November 2, 2004 at 3:01 am
SQL 2005 is not due that soon and SQL 2000 is fairly mature
It'll be more expensive than SQL 2000 and I'd wait until the first service pack at least before I deployed it in production
November 3, 2004 at 1:48 am
I would like to add that if everything is working fine on SQL7 and you can install W2K on your new servers then I would limit it your costs to the hardware upgrade.
I would start testing you apps on SQL2005 after the initial release, but not plan roll-out until 6-12 months after release so that any bugs or glitches have had time to surface.
I would start negotiating with whoever controls your budget that by putting off a SQL2000 upgrade until a new fiscal year you are saving money for an upgrade plus a shed load of training for SQL2005.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply