February 12, 2003 at 9:02 am
Hi All,
I need help making a case for SQL Server 2K and I have about as much tact and political correctness as General Patton with a tank. My group supports and manages(for a fee) various bus. groups within my company. One of these groups has purchase a product called Connectcare. Connectcare is also doing some customization (stored procedure I'm told). I came in late on this and all considerations for hardware and platforms has been decided. Management is hostile to making any changes before installation due to work that has been done.
The decision was 2 servers stage and prod on Win 2K with SQL 7
Here's the case I want to push. I am told that ConnectCare supports SQL Server 7 and 2K. My management pushed for 7.0 because at the time last summer/fall they were under the impression that SQL Server 2K was not being used or supported interally. They were mistaken, we have serveral installations and we support it.
I want to push all new servers install go SQL 2K way. I need to argue vendor product stability, SQL 2K sp3 stability, code transfer(sp that was written by ConnectCare), MS support for SQL 2K (will 7 support go away), ConnectCare's support for SQL 7, the cost of upgrading at a later data to SQL 2K if a new better version comes out, ROI, cost benifit, and anything else you can think of.
After finding out about this product and decision today, I go to the wall with my arguement on Thursday, any ammunition to help me fight my case would be appreciated.
Thanks all
John Zacharkan
John Zacharkan
February 12, 2003 at 1:13 pm
Will support for SQL Server 7 go away?
Yes. Most companies only support the current and one prior version of software. The current SQL Server version is SQL Server 2000 and the one prior is SQL Server 7. SQL Server 6.5 is no longer supported (no Service Packs, patches, etc are available).
When Yukon comes out, expect support for SQL Server 7 to go away within a year.
What kind of license do you already have for SQL Server 2K? SQL Server 7? Would your 2K license cover another server? This could support your point due to cost.
Why have multiple versions of SQL Server? Both have differences in programming and administering. Your DBAs/programmers/developers would have to keep track of the differences in the two versions.
-SQLBill
February 12, 2003 at 1:25 pm
Licensing not an issue here, don't want to touch verions, getting them to migrate, convert 100 + database with full regression testing is on the table. But just because we have legacy databases doesn't mean we need to create new ones - I would rather go forward, and it's not like I'm talking bleeding edge.
I just need something more convincing. I don't need to convince this group - They signed on when I said hi, but my management group lives in fear that the project might be delay if we switch tracks from 7.0 to 2K.
I need to convince them that the vendor switching support and MS support and estimate cost(man hrs & $$) to upgrade later.
quote:
What kind of license do you already have for SQL Server 2K? SQL Server 7? Would your 2K license cover another server? This could support your point due to cost.
Why have multiple versions of SQL Server? Both have differences in programming and administering. Your DBAs/programmers/developers would have to keep track of the differences in the two versions.
-SQLBill
John Zacharkan
John Zacharkan
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply