Comments
Sort by recent activity
Hi ghines,
Both your SQL Backup job and your file import will be battling it out for system resources, especially Disk I/O and CPU. Because of this the performance of your SQL Server and these processes will be greatly reduced.
It doesn't seem like running both processes in your environment simultaneously is very feasible so I would advise scheduling the tasks so they do not coincide.
If you really need to kill a SQL Backup job, the fastest way it to stop/start the SQL Backup Agent service on your SQL Server machine.
You can check if SQL Backup is currently performing a job or about too by opening the SQL Backup GUI and examining the timeline.
This should display all your scheduled jobs so you can plan a window for your file import.
If you do not use the SQL Backup GUI you can run the following to check for currently running backups :
exec master..sqbstatus
I hope this helps. / comments
Hi ghines,
Both your SQL Backup job and your file import will be battling it out for system resources, especially Disk I/O and CPU. Because of this the performance of your SQL Server and these pro...
Hi John,
If you zoom into the timeline using the control just under the menu bar on the top right do your jobs then display correctly?
Please let me know if this helps, / comments
Hi John,
If you zoom into the timeline using the control just under the menu bar on the top right do your jobs then display correctly?
Please let me know if this helps,
Hi,
To answer your first question, you can indeed install SQL Compare from the individual SQL Compare installer or the SQL Toolbelt installer on either a 32 or 64 bit system.
I have e-mailed you a link to the patch requested.
Thanks, / comments
Hi,
To answer your first question, you can indeed install SQL Compare from the individual SQL Compare installer or the SQL Toolbelt installer on either a 32 or 64 bit system.
I have e-mailed you a ...
Hi fatherjack,
The CPU usage is a shared resource so both instances should raise the alert.
You could take a look at the System Processes section for the alert to see which processes are taking up a lot of CPU time.
I hope this helps, / comments
Hi fatherjack,
The CPU usage is a shared resource so both instances should raise the alert.
You could take a look at the System Processes section for the alert to see which processes are taking up ...
Hi Sean,
Yes, it is possible to restore a SQL Server 2005 backup to a SQL Server 2008 instance. SQL Server will run the upgrade steps necessary when the database is brought online. As far as i'm aware changing the compatibility mode isn't necessary to use page level compression etc
You can find out the differences between compatibility level 90 and 100 from Books Online.
When restoring, you can specify physical locations for the logical file groups, the command will be something similar to the following :
EXECUTE master..sqlbackup N'-SQL "RESTORE DATABASE [Filegroup] FROM DISK = ''\\Share\Backups\FileGroup.sqb'' WITH RECOVERY, MOVE ''Test1dat1'' TO ''D:\Data\FilegroupTest1.ndf'', MOVE ''Test1dat2'' TO ''D:\Data\FilegroupTest2.ndf'', MOVE ''test1dat3'' TO ''D:\Data\FilegroupTest3.ndf'', MOVE ''test1dat4'' TO ''D:\Data\FilegroupTest4.ndf'', MOVE ''FileGroupTest_log'' TO ''D:\Data\FilegroupTest_log.LDF''"'
I hope this helps. / comments
Hi Sean,
Yes, it is possible to restore a SQL Server 2005 backup to a SQL Server 2008 instance. SQL Server will run the upgrade steps necessary when the database is brought online. As far as i'm ...
Are you in the context of the database when running the restore?
If you make sure USE [master] is at the top of your script that may do the trick. / comments
Are you in the context of the database when running the restore?
If you make sure USE [master] is at the top of your script that may do the trick.
Hi Mike,
If you check the SQL Backup log file for the restore, are there any messages pertaining to a successful or erroneous restore?
You should be able to find the logs on the restoring server here by default :
%allusersprofile%\Application Data\Red Gate\SQL Backup\Log\<instance name> / comments
Hi Mike,
If you check the SQL Backup log file for the restore, are there any messages pertaining to a successful or erroneous restore?
You should be able to find the logs on the restoring server he...
Hi Mike,
Sorry I presumed you were using version 5.
There isn't a workaround to set different retention periods for each location but we can create a script that will restore the most recent backup file from the network share when there are many files.
I have the code as part of another script so will take me a short while to cut out the right bits.
I will post it here/pm it to you depending on how big it is.
Obviously if there isn't enough space on your network share to hold a few days worth of files we will need to think of something else. / comments
Hi Mike,
Sorry I presumed you were using version 5.
There isn't a workaround to set different retention periods for each location but we can create a script that will restore the most recent backup...
The script can be downloaded from here.
Please note that it won't stay in this location indefinitely, please e-mail support@red-gate.com if it isn't available for download and quote this forum post.
This script will restore a full backup for all databases on the server it is run against, replacing the older database. You can exclude specific databases at the top.
Please let me know if this helps. / comments
The script can be downloaded from here.
Please note that it won't stay in this location indefinitely, please e-mail support@red-gate.com if it isn't available for download and quote this forum post...
If there is only ever 1 backup file on the NAS you could run something like this :
EXECUTE master..sqlbackup N'-SQL "RESTORE DATABASE [Northwind] FROM DISK = ''\\store\Backup\FULL_SQL2005_Northwind_*.sqb'' WITH RECOVERY, REPLACE"'
/ comments
If there is only ever 1 backup file on the NAS you could run something like this :
EXECUTE master..sqlbackup N'-SQL "RESTORE DATABASE [Northwind] FROM DISK = ''\\store\Backup\FULL_SQL2005_...