Yes. That doesn't really help - the COTS vendor won't provide support for R2. It's a somewhat old version and they are trying to get the customer to upgrade. In fact the application is already on extended support - but only on SQL 2005 or 2008. They have already done some things to try to move it back - I arrive on site Monday to see what those "some" things are and see if we can complete it.
On Fri, Dec 13, 2013 at 5:29 PM, Jeff Steward <[email protected]> wrote: > Have you tried setting the compatibility level of the database to 2008? > > http://technet.microsoft.com/en-us/library/bb933794.aspx > > -Jeff > > > On Fri, Dec 13, 2013 at 3:25 PM, Kevin Lundy <[email protected]> wrote: > >> Hi All >> >> I have a client that upgraded a database from 2008 to 2008 R2. It took a >> while, but eventually their primary application proved to be incompatible. >> They get a fail because they didn't read the compatibility guide and didn't >> adequately test. But that is why they are now a client. >> >> I know you can't restore to an older version. >> >> I've found a few references to using Enterprise Manager "Generate >> Scripts" with some advanced options. I've tested on some simple databases. >> >> Has anyone done this on a fairly large complex database? Aware of any >> constraints, issues, etc? >> >> How about alternative methods or tools? I've seen a couple of references >> to using Redgate tools - I have a call into them. >> >> Thanks >> Kevin >> > >
