August 9, 2007 at 9:59 am
Our current backup strategy uses a stored procedure and a cursor to go through all our databases and optimise and backup them up one at a time.
This works fine for SQL2000 and SQL2005 but not for databases that have Full Text indexing on them.
When we use a cursor for these types of databases, the backups completes ok but we receive the following warning:
Warning: Failed to change the status to PAUSE for full-text catalog "MyTextCatalog" (5) in database "MYDATABASE" (7). Error: 0x8001010e(The application called an interface that was marshalled for a different thread.).
Couple of questions:
- Does anyone know why these databases dont like a cursor?
- Does anyone know what this warning means?
- Can we ignore the warning or does it jeopardise the integrity of our backups being taken?
thanks
wendy
August 9, 2007 at 11:34 pm
I'm not clear on what you're trying to accomplish...
Full text index on SQL 2000 are not backed up as part of the database backup, SQL 2005 they are.
Are you taking this into account in your script/cursor?
Worst case you may want to script the drop/create/populate of the full-text indexes as well, thankfully full-text indexing on SQL 2005 is incredibly fast (compared to SQL 2000 on the same hardware).
Joe
August 13, 2007 at 7:57 am
I am trying to back up my databases with no warnings...
My cursor just does the standard BACKUP DATABASE command, obviously with SQL2000 it doesnt include full-text indexes in the backup but with SQL2005 it does and that is why we are only getting this error when we backup our SQL2005 databases.
We get this error even when we do a log or diff backup of the database, so droping/creating/populating every time isnt an option.
SQL2005 will try and pause the fulltext indexing before a backup, I need to know the consquences of this pause failing, as per my error message.
Is this harmless or are their consequences of this not being stopped prior to a backup??
wendy
August 13, 2007 at 8:05 am
Wendy - your backups are no good if you can't restore from them. Have you tested one of your backups by restoring to a test database area? What results? Not that I'm trying to make you answer your own question, but it's not my job on the line if your restore fails.
It sounds like the sole issue standing is the impact of the 'failure to change status to pause'. Am I correct?
August 13, 2007 at 8:14 am
yes, I have tested restoring them and it works successfully.
What I dont know is, if someone was using the full text indexes at the time of backup would there be an impact on the data integrity at restore time?
In fact on an opposite note, does anyone know the impact of these being paused successfully during backups when users are using them? Does it kick them out?
yes, the sole issue is what do these warnings actually mean and what are their impact??
thanks
w
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply