January 8, 2009 at 3:19 pm
For one thing, don't even think about upgrading that server to SQL 2008. So far as I know, that won't do 7.
I'd be inclined to check the service contract on the software and find out how much of the support is supposed to be you, vs how much will be them. If it's all them, consider a low-end server dedicated to their product, and then don't touch it.
- 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
January 8, 2009 at 7:41 pm
Unfortunately (and I do mean that in the sincerest sense) you can load 7.0 data into 2005. When it's loaded it will stay at that compatibility mode unless you change it.
You cannot load 7.0 data into 2008.
As for what will work and what won't. For the most part you can handle it pretty much as you would any 2005 database. I would check with the company and see why they feel that this has to be in 7.0 mode.
I feel your pain though, a forced upon product from SQL 7.0 that you have to load and use. Forget about using MSDE from way back, it's 35GB in size. Most frustrating.
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply