There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
Database showing "loading" msg after restore attempt
I am attempting to restore a backup and have completed similar such events numerous times, without issue, across dozens fo SQL servers but now, when I am attempting to restore a backup, either through EM or QA, it seems to complete (and even provides notification that it has completed successfully), but the Database node in EM continues to show a "loading" message - no matter how long I leave it sitting there, it continues to remain inaccessible and show the loading msg - even following severla attempts at restoration.
I am on SQL 2000
the database is set for full recovery and am forcing the restore from a device, with the first recovery completion state option selected (leave database operational)
I am on SQL 2000
the database is set for full recovery and am forcing the restore from a device, with the first recovery completion state option selected (leave database operational)
Asked:
2
1 Solution
This article briefly mentions the above with regards user dbs:
http://search.microsoft.com/search/results.aspx?st=b&na=88&View=en-us&qu=sql+loading
http://search.microsoft.com/search/results.aspx?st=b&na=88&View=en-us&qu=sql+loading
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
Not sure why your issue is occuring, usually this would occur if you set your restore to run with a NORECOVERY option or if you missed a transaction log out of the restore sequence. You may be able to get it out of a loading state by running:
RESTORE DATABASE <Your DB Name> WITH RECOVERY
Unless there is an issue with the DB this should leave it accessible although you will need to establish if any transaction logs you hoped to apply have been.