I performed a database restore this morning from a backup that I had created yesterday - the database was backed up to a file, not a backup device.
After the restore completed, the database was left in a LOADING status. I checked the log and it stated 'Bypassing recovery for database X because it is marked in load. I used the enterprise tools (all tasks/restore database) to do the restore.
I asked one of our senior dba's for help, and he followed the same process I did and it worked fine for him.
Any idea why my database was left in a loading status? The database was fine prior to the restore.
I Restored the database from Backup with a Different database Name. I got a message the Restore Database was successful. Still the database has Loading Status. Can you let me know what I have to take that status.
I asked this question before but never received a decent answer. When a restore fails, what are the steps to re-start the restore? This should be a very common issue and for the life of me I have been unable to find it in BOL or the MS site! Please let me in on the secret!!
I am trying to build a test environment for our production server. I backedup and restored all my databases. I had to copy the jobs too, so I backedup and restored msdb database. When I try to change any of the jobs, I get the following message.
"Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server."
I have no clue what this message is about. Can someone please provide me with some clues about how I can modify my jobs and get my test environment to work.
I need some data from msdb.dbo.sysjobs and msdb.dbo.sysjobhistory but I need it from a backup file.
I don't need to restore the msdb database, I just need some data from the backup. Everytime I try to restore it under some innocuous name like bills_db it tells me msdb is in use.
Is there a way to restore this db to some other name and retrieve data from it?
I BACKED MSDB TO A DEVICE AND THEN RAN THE FOLLOWING CODE ON ANOTHER SERVER:
RESTORE FILELISTONLY FROM DISK = 'd:mssql7ackupcomplete_bak.bak' RESTORE DATABASE Test_MSDB FROM DISK = 'd:mssql7ackupcomplete_bak.bak' WITH MOVE 'MSDBData' TO 'd:mssql7datamsdbDATA.mdf', MOVE 'Northwind_log' TO 'd:mssql7datamsdbLOG.ldf'
I get the following error: (Why are the logical and physical name referring to master database?)
LogicalName PhysicalName Type ...1 -------------- ------------------------- ----------- ...2 continued master F:MSSQL7DATAMASTER.MDF D ...3 below mastlog F:MSSQL7datamastlog.ldf L ...4
Server: Msg 3234, Level 16, State 2, Line 3 File 'MSDBData' is not a database file for database 'Test_MSDB'. Server: Msg 3013, Level 16, State 1, Line 3 Backup or restore operation terminating abnormally.
------------------------------------------------------------------------- QUESTION? -- WILL BACKING UP MSDB AND RESTORING IT TO ANOTHER SERVER MOVE ALL MY JOBS AS WELL? IF NOT HOW DO I MOVE MY JOBS FROM ONE SERVER TO ANOTHER?
I have a server attached to a SAN, all user db's are on the SAN, master, tempdb, and msdb are on the local machine. We will be replacing the machine (not the SAN) to a newer sql server. Our plan was to create the new server with same name, deattach current user db's,backup master and msdb, then connect new server with same name an IP to SAN. I then wanted to restore the master and msdb db's to the new machine, and attach the user db's. We are running log shipping to a stand-by server in this configuration. I was thinking I could let last tran log backup and copy occur, and then let the last restore happen on the standby. I would then shut down the agent. Should I not be able to restore the MSDB and master to the new server (as long as all file folder locations are the same) and be ready to go? Or are there issues when restoring the Master and MSDB to a new server from a different server.
I have inherited a SQLS erver 2000 instance where the client neverimplemented a backup startegy for the "master" and "msdb" databases.MSDB is now showing errors and my only option for a restore is from atape backup of the server.Any thoughts..
Suddenly one day I found some corruptions have occurred in my SQL Server 2012 installation. Because my 'msdb' has been marked SUSPECT/CORRUPT; hence no new work can be done as per my schedules.
I have gone about trying to repair it. I followed this article here: [URL] [the region 'Create new MSDB Database'].
I am facing some sizeable difficulties in doing this on my own. Steps 1. & 2. I have done. I am now stuck at step no. 3.My instance name is SQLEXPRESS. So, when I give,
SQLCMD -E -S<SQLEXPRESS> -dmaster -Q"EXEC sp_detach_db msdb"Â [as per the article], what I get is:
The System cannot find the file specified.
So I am stuck at that point. What's with the 'cannot find file specified'? The stored procedure, or the mdf, ldf files for my msdb? What is it?Also, if and when I am through with step no. 3 I would like to know about steps 5. & 6. also which are soon to follow [like how to do them correctly, safely and from where, the different options]. This is a huge priority for me to get my sql server up and running again because I can't do my other coding works without it. Everything is stalled. Slowly reaching the desperation, SOS mode..
I'm new to this forum but was wondering if you could advise me on getting the DB back to an accessible state. I tried restoring the DB but unfortunately I don't have enough disk space. The error message appeared instantly informing me of the lack of disk space. Now it says its in (Loading state) and I cannot access the DB. Is there anyway I can manually change it back??
I am trying to restore my msdb database after rebuilding my RAID, and reinstalling sql. I can restore my user databases fine, but my msdb gives me error 3132: The media set for database msdb' has 2 family members but only 1 are provided. All members must be provided.
I really don't want to lose all my jobs, so any help would be appreciated. thanks.
hi, I already have jobs in the sql server agen. I want to copy all these jobs to another sql server, What is the best way to do it. here what I am thinking to do 1. Back up the msdb from the sql server which has the jobs 2. restore msdb into the sql server where I need to create the jobs.
I got an error message, 15089 cannot change the 'single user' option of a database while another user is in the database.
But no one is in except me.? thanks for your input
I am trying to restore my msdb database after rebuilding my RAID, and reinstalling sql. I can restore my user databases fine, but my msdb gives me error 3132: The media set for database msdb' has 2 family members but only 1 are provided. All members must be provided.
I just performed a normal database backup to disk, and i was able to restore the other db's i backed up the exact same way... I really don't want to lose all my jobs, so any help would be appreciated. thanks.
SQL_PROD: production server with SQL Server 2005 SQL_TEST: test server with SQL Server 2005 What we are trying to do:
We are testing our backup and recovery procedures. To do so we are using the backups from SQL_PROD and restoring them on SQL_TEST. We are restoring: all user databases, master database, msdb database and model database. The issue we are experiencing:
I think we've hit a kink in our recovery procedures concerning msdb database in the context of a recovery on another machine (SQL_TEST in this case).
We include msdb in our nightly backups so that, in the event of server loss, our maintenance plans and jobs get restored.
On SQL_TEST (after a recovery), the maintenance plans and jobs do get restored but the problem is that they reference the SQL_PROD server (server's name, disks, etc...). Deleting the jobs and maintenance plans from SQL_TEST we got no errors and the jobs and plans disappeared from beneath the Maintenance Plans and Jobs nodes. Doing a refresh on the nodes, the €śdeleted€? plans and jobs reappear beneath their respective nodes! Upon the second deletion (and any consecutive delete) we get the error:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) ... The SELECT permission was denied on the object 'sysmaintplan_plans', database 'msdb', schema 'dbo'. (Microsoft SQL Server, Error: 229)
Clicking on "Show technical details" reveals this:
... Server Name: SQL_PROD Error Number: 229 Severity: 14 State: 5 Line Number: 1 ...
Note that SQL_PROD is being referenced in the error message!
This morning I took a look at SQL_PROD€™s Maintenance Plans and Jobs (the source of the msdb backup) and surprise surprise: THEY WERE ALL GONE!!! This is a MAJOR BUG!!! Deleting a job or a plan on one server should not have the effect of deleting it from a different server (regardless of the origins of the msdb database). Is this a known bug? Or is it considered €śnormal€? behavior?
My questions are:
How do we delete the maintenance plans and jobs from SQL_TEST without deleting them from SQL_PROD? What is the proper/recommended method to backup and restore maintenance plans and jobs (in fact msdb)? Is it by scripting things and recreating them on the recovery server in an empty msdb or is there a way to restore msdb properly from the crashed server? Thanks for your help.
Late last Sunday I had to do an emergency rebuild of our SQL Server (v2012). In my haste, I neglected to restore the MSDB and MODEL DBs, and am instead using those which came with the fresh SQL install -- which obviously don't contain my jobs and maintenance plans. Would there be any problem/conflicts with me restoring those DBs this weekend?
I have a weekly job that runs to execute msdb.dbo.sp_delete_backup_history on history older than 7 days on a server that is a log-shipping destination server. However, I have now noticed after putting a new deadlock alert, that this job causes RESTORE LOG jobs for all 6 of my log-shipped databases, which run every minute, to deadlock.
I am not concerned with the fact that the RESTORE LOG jobs are then chosen as the deadlock victims, as they will simply re-run in the next minute anyways.
What I would like to do though is to somehow lock all the tables being cleared by sp_delete_backup_history, so that the restore jobs are forced to wait or fail without causing a deadlock to appear. I was wondering if I could do this via setting the job which runs sp_delete_backup_history to use serializable isolation level, or would that cause other problems/issues? If not that, would setting the deadlock priority level to high prevent deadlocks, or just simply force the restore log jobs to be chosen as the victim?
The main thing is that I would like to stop being "annoyed" by the deadlock messages being generated.
HiI am trying to copy a 20 GB database from server 1 to 2. I took a fullbackup, copied to server2 and restored ( ready for use) using EM.After the message restore completed, I see the database's status as LOADING.We are on Sql Server 2000 (8.00.818) on Windows 2000 Adv Servers.I ran dbcc on the source DB and it returned no errors. I tried the command'restore db with recovery ' which didnot help. I get an message saying thatthe data file is only partially restored.. It seems the last resort is tochange the status in system tables.Any ideas?ThanksRagu
we have a reporting database that needs to be refreshed every week. I normally get a big backup file (50GB) from our business partner very Sunday morning; I have setup a job to restore the database once I got the backup file. The restore job normally will take about 4 or 5 hours to finish, but sometime it may take much longer (more than 10 hours). We knew there is some kind of disk storage contention going on the SAN. When this problem happens the system guy always try to pick my db restore process to be the victim. I hate to kill a job when it has 90% done, but I have no way to tell the restore progress status. Does someone know if I can query database restore progress information from any DMVs?
We are upgrading from SQL 2008 R2 to 2014. I have a 2008 SSIS package converted in VS 2013 and deployed to MSDB as package deployment model. It ran ok from an agent job. However, after I converted the same package into project deployment model, converted the connection manager to project model, deployed the project (with the package) to SSISDB and applied environment variable for its configuration, the agent job failed for not able to acquire connection to what used to be the connection manager.Â
Both agent jobs run understand the same account on the server. The account has access to the databases that are connected in the packages. The job/packages has been running ok on 2008 R2 accessing the same db for years.Â
The environment variable for the connection string is defined as "Data Source=ServerABC;Initial Catalog=DB123;Provider=SQLNCLI11;Impersonation Level=Impersonate;"
Why can't the job connect to the database when it runs a package from SSISDB?
What is the best way to restore a database from a folder of backups (including full, diff and log backups) without using the backup history in msdb?
I have a restore process that restores all backups on a regular schedule in order to fully verify their integrity. To do this, I use the backup history in msdb on each server that I'm monitoring. I had a thought the other day that I would be in trouble if I lost msdb. Then my backup history would only be as good as the last backup of msdb.
What I'd like to do is read a folder of backup files and generate a restore script up to a specified time. Would I use RESTORE HEADERONLY to do this? If so, would I use PowerShell to traverse each file in the folder?
I recently installed MSDE on a laptop. I then restored several databases from backup files without problem. However, one database is constantly stuck at the grey colour displaying the (Loading) message.
Why won't this database restore ? It is of course the most important database and I only have the one backup file.
This only appears to fail on his server. Do I need to uninstall MSDE and start over ?
Hi friends, please help me with my urgent needs. I have created a job. This job contains 6 steps. All steps are sql querries. In step no:3 i have an if condition in the script. When the condition becomes true i have to run the script. That is ok. But the problem is when the condition becomes falls i have to go to the step no 6 and at the same time the status of step no:3 should be like "failed". can you help me please Please this is an urgent reqirement.
I have seen this before. A 2000 restore fails, leaving the database thinking it is being restored but the restore job failed and errors when it is restarted. EM is clueless. I believe there is a proc to reset some flag. Can you share it with me???
I am extracting data from SQL Server 2005 to flat file destination. I am using SQL Command to specify the data selection query. One of my query uses Replicate function to derive a column value. When I execute this package it fails with the error "Data conversion failed. The data conversion for column "value" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page".
The reason for the problem is that, it is taking the InputColumnWidth of the flat file destination as 8000 and I specified the OutputColumnWidth as 4.
If I change the OutputColumnWidth to 8000, it is working without any error but resulting in the column width of 8000.
I tried using DerivedColumn Transformation's Type cast and DataConversion Transformation but still I am getting the same error in the respective Transformation components.
i want to restore a database but not the log file. the backup has the data and log files in it. i tried doing a search for this but kept finding examples about restoring backups that dont have log files. i want to do the opposite.
I had to restore a database late this afternoon. I have the database set to FULL recovery. Database backups are performed nightly and transaction log backups are performed every other hour. I decided to perform a point-in-time restore. When I restored this way everything seems to go ok and it finishes. Then the database is grayed and says "Loading". Although I tried 4 separate times, one time allowing over an hour, the grayed out database and "Loading" never goes away.
Freaking out I deleted the "Loading" database (didn't delete logs and backup files) and tried a manual restore from the previous night's backup file. It attached and restored properly and was ready to go in 2 minutes.
Of course I wanted to get the transaction log files restored too, since it had work from earlier today. So I tried another restore via point-in-time and got the same old messages. Currently, the database is running with the previous night's backup restored but the users aren't too keen on having to do 5 hours worth of work to catch up to the previous transaction log backup come Monday morning.
Other postings I know have asked about this error message, but none has quite been my particular experience.
Using Visual Studio 2005 I have developed an aspx (.NET 2.0) web page, which has embedded in it, a Report Viewer object. Clicking a button calls the Reporting Services report and populates the Report Viewer object. This web-page works fine when run from Visual Studio.
Once deployed to the Web Server however, the web page produces the 401 error message.
I can also run the report fine, when running it directly from the Reporting Services Report Manager, so I know I have the proper permissions on RS itself - it fails only when I try calling the report from the ASP page.