We have an old app that is running on SQL Server 2005 and the database is set to compatibility level 80 (SQL 2000). Would like to change to level 90 (SQL 2005). If problems surface, can we simply change back to level 80? (assuming we don't make use of any new features). Can the compatibility level be changed back and forth until all problems are worked out? The database will stay on the same server that is running 2005 binaries.
I've searched the code for known problems and believe I've found and corrected them. Good. It's one of the things the upgrade advisor does but it can only check the code inside SQL Server (SP's, functions,
In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.