Our normal practices for backing up SQL servers is to use the regular SQL backup tools to perform full, differential and transaction log backups and this has always worked fine. Recently we performed ...
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 ...
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 ...
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 ...
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 ...
Delayed durability was announced late in the SQL Server 2014 development cycle, but offers something that many SQL Server professionals have wanted for years—the ability to disable transaction logging ...
SQL Backup Pro 6 features improved “network resilience to recover interrupted backup operations, self-healing log shipping and a new advanced compression algorithm,” Red Gate claims. “Marketing calls ...
The next version of Microsoft’s relational database management system (RDMS) promises to bring immense performance gains to online transactional processing systems. SQL Server 2014 will come with a ...
SQL Server 2014 and the SQL Server Backup to Microsoft Azure Tool both hit their "general availability" milestones today. Earlier this month, the SQL Server 2014 product was at the ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results