March 17, 2009 at 7:47 am
Does anybody know if there are any issues with a local developer machine being on SP3 but deploying plain TSQL Stored Procs etc.. to an SP2 test server?
One of the guys here has SP3 but is deploying some plain TSQL SPs (nothing clever) to an SP2 test server?
March 17, 2009 at 7:49 am
depends on the code, if you look at the fix list since RTM there are a lot of things MS fixed in cursors and other issues when running some commands under certain conditions
March 17, 2009 at 7:50 am
Should be fine. After all, finding out whether it will work in production is what test servers are all about.
- 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 17, 2009 at 7:53 am
Cheers guys. That's what I was thinking but I didn't know whether I would be best to rollback to SP2 which is messy!!
The other Devs are all on SP2, but this guys has a new build PC which he put SP3 on.
March 17, 2009 at 7:56 am
our QA servers are usually at a higher build than production. we'll let them run a month or so and then upgrade production every few months to the build that QA is running
March 17, 2009 at 8:05 am
Thanks for the replies.
We are going to live with it as it is so messy to rollback. As I say there is nothing clever like CLR/Complicated TSQL and the test server should pick up any discrepencies in Actual to Expected results.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply