March 17, 2009 at 1:14 pm
We have a software vendor that is not supporting SQL 2000 anymore and is requiring us to use SQL 2005. Would you count their application as being SQL 2005 ready if it requires the database to be run in SQL 2000 Compatibility mode?
We cannot believe that this is their requirement. If this would have been specified before we purchased new hardware and software we would have opted for
Server 2008 running SQL 2008 and put the database on it in SQL 2000 mode. What are you thoughts?
March 17, 2009 at 1:22 pm
That's pretty inappropriate unless they're actively working on an upgrade which will come out shortly. VERY shortly.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 17, 2009 at 1:26 pm
They just release the "SQL 2005" version we are using now, and they plan on having a "SQL 2008" version coming out in a few months
March 17, 2009 at 2:25 pm
By my knowledge, the software either requires SQL Server 2005 or has to run in SQL Server 2000 compatibility mode.
If you running SQL Server 2000 since now, you should consider to wait for the SQL Server 2008 requiring 😉 Version.
Greets
Flo
March 17, 2009 at 2:29 pm
We were being required to upgrade ASAP due to them not supporting SQL 2000 anymore. We were trying to wait until SQL 2008 was being supported. From what we see now we could have went with 2008 and just did the 2000 mode. It is just disheartening that a vendor would knowingly do this.
March 17, 2009 at 2:48 pm
Sounds like the vendor has issues. What a stupid way to do business!
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
March 18, 2009 at 12:29 am
David Barnette (3/17/2009)
We were being required to upgrade ASAP due to them not supporting SQL 2000 anymore. We were trying to wait until SQL 2008 was being supported. From what we see now we could have went with 2008 and just did the 2000 mode. It is just disheartening that a vendor would knowingly do this.
I did give you my Kendo Stick (Shinai) so you can beat them up for that ... grr.
I don't know your software .. but if I had any say I would immediately terminate business with such "shaddy" vendors...
I tend to Ignore vendors that tell me stuff that doesn't make sense and my boss backs me up over vendors so it is a ++ :P; at least so far hehe.
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 19, 2009 at 11:56 am
Running an application database in 'compatibility mode' for SQL 2000 is not all that bad. You will still reap the performance and tools gains of the release. You'll just lose out on a few of the dm views is really all that you'll be missing. If the application is 'stable' then what's the big deal ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
March 19, 2009 at 1:32 pm
You lose a lot more than just a few dm's running in "compatability mode".
There is also the EXPENSE. Instead of going ahead and purchasing 2008, they have now had to purchase 2005 and then 2008. That's a lot more $$$.
Then there's the whole design / trust issue. Requiring 2000 compatability mode is a huge red flag (to me at least) that these guys are clueless.
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply