August 24, 2004 at 1:08 pm
I am trying to restore a database by kicking off a stored procedure that will restore the database and then add the user as dbo. The Sp that I am using is hard coded for the backup location and the user from a view (from a third party program) inserts the backup file name, database name and the user that they want inserted. This works fine with a database that the backup file is less the 1.5 GB. Anything larger and it fails. The MDF, LDF files are created but it appears that it fails to insert the user in. My first thought was that there was not enough time so I added some spacers to give it more time. That did not help. The database is left in the loading status. I have tried taking out the user insert but that did not help either. ANy light that can be shed on this is greatly appreciated.
August 24, 2004 at 3:08 pm
Probably, buried somewhere in the load, is a SQL Script. It may not be ovious but see if you can find it. Then edit that puppy so that the restor line is something like this.
RESTORE DATABASE DatabaseName WITH RECOVERY
Then drop the current database that is stuck in load status, and rerun until the script completes.
I've run into this before. It something like the KB article below.
http://support.microsoft.com/default.aspx?scid=kb;en-us;272683&Product=sql2k
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
August 24, 2004 at 3:17 pm
I have tried with recovery and that did not help. I will check the KB article that you are pointing to.
August 24, 2004 at 3:22 pm
Why should the size of the backup (which will reflect on the size of the database) make a difference?
August 24, 2004 at 3:35 pm
Then work through norecovery and restart.
Eventually one of them will work. Can you control the running of th scripts?
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
August 25, 2004 at 12:14 am
Stranger things have happened with me during restoring databases.
After installing my cluster and testing recovery I found out, that the larger databases (2Gb) where not restoring, due to a network error, and the smaller databases where doing fine.
This had to do with named pipes communication to the database. After disabling named pipes communication at de database server everything worked fine.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply