SQL Server 2000 - Availability whilst restoring logs
I need to ensure users can submit SQL queries (readonly) to a database whilst transaction logs are restored (at 15 minutes intervals.)
Is this possible?
I need to ensure users can submit SQL queries (readonly) to a database whilst transaction logs are restored (at 15 minutes intervals.)
Is this possible?
I am therefore assuming that there is no way to keep a system 'live' for select queries whilst updating it in SQL 2000?
I am currently providing views on some tables held in a SQL 2000 database from SQL Server 2005. The reason I cannot bring this database in to 2005, is that it would then be upgraded and is then incompatable to the application that is using it, and transaction logs being applied.
Ideally, I would add the database to be held in SQL 2005 (without being forced to upgrade it) then just setup log shipping in 2005 (using 2000 logs) . It just doesn't look like it is possible?
Any thoughts how i can set this up would be appreciated.
If you have the same version of SQL Server on both ends of a log shipping configuration, you can use the WITH STANDBY option to be able to access the database in between updates.
Unfortunately in your case, there is complication of differing database formats. Before SQL 2005 can make use of the database files, they must be updated to the SQL 2005 format. This is done the first time the database is recovered under SQL 2005. So, you will not be able to access your log shipping database until both sides are at the same version of SQL Server.