Help! My SQL Server Log File is too big!!! Your email has been sent Overgrown transactional log files can turn into real problems if they are not handled properly. Today SQL Server consultant Tim ...
Welcome to this new series -- in this column, I hope to impart some quick, short tips that will help you make quick work of managing and administering your SQL Server databases. First up is an ...
In an earlier blog entry, I talked about “Deprecated” code and I highlighted the fact that the BACKUP LOG WITH NO_LOG and BACKUP LOG WITH TRUNCATE_ONLY statements are no longer allowed in SQL Server ...
With SQL Server 2000, there are myriad choices for backing up your database. Whether your database is small and changes infrequently or very large and changes rapidly, there is a backup strategy to ...
Let's follow up the last column with a step-by-step breakdown shows how the PowerShell script automates SQL Server backups, manages retention, logs activity and verifies data integrity. In my first ...
Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with content, and download exclusive resources. Traditional caching fails to stop "thundering ...
I'm running Backup Exec 9.1 on Window 2000 Advanced Server and during the install I set up BE to use SQL Server 2000 to store its log info instead of MSDE. The database size has grown too large and I ...
A couple of months ago, I wrote an article on how to use PowerShell to back up a database within SQL Server Express Edition. Even though the technique that I described in that post works, the script ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results