|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 5:54 PM
Points: 525,
Visits: 617
|
|
While the problem is a simple one, I am sure every one of us has a story when we spent hours if not days on something completely trivial only to say at the end: Duh! Thank you for sharing your experience, I am sure you saved some folks a lot of frustration.
|
|
|
|
|
UDP Broadcaster
      
Group: General Forum Members
Last Login: Wednesday, January 02, 2013 12:15 PM
Points: 1,443,
Visits: 711
|
|
Changing the compatibility level without checking to see if something else broke could be a recipe for disaster; not really sure if this is a viable solution, I think the answer to this is a little misleading.
Compatibiltiy level can effect many other things within the application, so I would proceed with caution!
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Yesterday @ 3:41 AM
Points: 140,
Visits: 474
|
|
Yes you are right. But we can do one thing change the compatibility level to 90 and then perform the operation and again change the compatibility to 80..
This problem i have faced as we have migrated from SQL Server 2000 to 2005 but the compatibility level remains the same, so it wont make any harm as such
--Divya
|
|
|
|