Activity overview
Latest activity by ehuna
David, that's great news! Thank you for listening to your customers and following up with this early access build of SQL Compare with support for SQL Azure.
As more and more developers find out about Windows Azure and host their data on SQL Azure I'm convinced this will pay off for Red Gate. Thanks! / comments
David, that's great news! Thank you for listening to your customers and following up with this early access build of SQL Compare with support for SQL Azure.
As more and more developers find out ab...
Support for SQL Azure?
The SQL Azure CTP has been released; I received an invitation token and I've been following the labs in the training kit and playing with it.
Right now, there's a lot of manual steps to clean up SQ...
There were no errors. So I tried going through the Log Shipping wizard again and this time was very patient. I let it run overnight and in the morning I had the four checkboxes and all four tasks were completed.
I am setting up log shipping on a production environment where we have a standby system. This standby system is in a different city and we have a VPN between the two systems.
Although we are assured 1 Mbps simetric between the two systems, sometimes it can be a lot slower.
I think a possible feature request for future versions of SQL Backup would be more feedback on the restore status. The restore worked for an hour fine, where every few seconds I could see a few MBs had been transferred.
But when it got to 99% or even 100% of all data being restored, it literally just sat there for hours. A link with more detailed steps or something that would give me the assurance that SQL Backup didn't just die or is not responding would be great.
Otherwise, how would I know how long I should wait before panic kicks in and I have to kill SQL Backup? / comments
There were no errors. So I tried going through the Log Shipping wizard again and this time was very patient. I let it run overnight and in the morning I had the four checkboxes and all four tasks...
Setting up Log Shipping - stuck on "Restore database"
I am setting up Log Shipping using the SQL Backup UI (not the command line or extended stored procs directly).
When I get to the "Performing tasks" step, the first step works, but it now seems stuc...
I meant the log backup is configured by SQL backup. And therefore since the NO TRUNCATE option is not used, the space is recovered automatically (by SQL Server itself indeed). / comments
I meant the log backup is configured by SQL backup. And therefore since the NO TRUNCATE option is not used, the space is recovered automatically (by SQL Server itself indeed).
Thanks Peter, that's excellent info. I will attempt not to shrink the LDF files and see how that goes. Since the space is recovered after every log backup (configured through SQL Backup) we should be ok. / comments
Thanks Peter, that's excellent info. I will attempt not to shrink the LDF files and see how that goes. Since the space is recovered after every log backup (configured through SQL Backup) we shoul...
Peter, thanks for the fast response. I think I understand, but let me be a bit more specific.
Suppose I'm using only the SQL Backup UI to configure my SQL full backups and log shipping.
Is there anything else I need to do to make sure that the logs don't just keep growing every day.
In other words, should I have a manual step to "manually reduce the size of the database log (ldf) files by running DBCC SHRINKFILE or something similar", or does master..sqlbackup do it for me?
If master..sqlbackup doesn't do it, when should I do it and what exact command should I use? (e.g. "DBCC SHRINKFILE ...") / comments
Peter, thanks for the fast response. I think I understand, but let me be a bit more specific.
Suppose I'm using only the SQL Backup UI to configure my SQL full backups and log shipping.
Is there a...
Truncating the logs?
I have a question on whether I should attempt to truncate the SQL logs if I'm using SQL Backup both for full backups and log shipping.
Here's our current setup:
1) Full backup at 2:00 AM.
2) Hourly...
Got it, thanks.
For those having the same question you need a license on any servers where you'll be backing up or restoring data (a full backup or logs).
This means that if you are setting up log shipping, you need at least two licenses: one for your production server (source) and one for the standby (destintion).
The good news is that you don't need licenses for the UI portion, so you could install it in your workstation as well as some Production systems used only for configuration, etc...
Note: this is true today, Red Gate could of course change this any time. / comments
Got it, thanks.
For those having the same question you need a license on any servers where you'll be backing up or restoring data (a full backup or logs).
This means that if you are setting up log ...