Additional Articles


External Article

How to Identify and Backup the Latest SQL Server Database in a Series

I have to support a third party application that periodically creates a new database on the fly. This obviously causes issues with our backup mechanisms. The databases have a particular pattern for naming, so I can identify the set of databases, however, I need to make sure I'm always backing up the newest one. Read this tip to ensure you are backing up your latest database in a series.

2012-12-03

2,037 reads

External Article

Understanding the SQL Server 2012 BI Semantic Model (BISM)

SQL Server 2012 introduced an unified BI Semantic Model (BISM) which is based on some of the existing as well as some new technologies. This model is intended to serve as one model for all end user experiences for reporting, analytics, scorecards, dashboards, etc. In this tip, I will talk in detail about the new BISM, how it differs from earlier the earlier Unified Dimensional Model (UDM) and how BISM lays down a foundation for future.

2012-11-27

3,420 reads

External Article

SQL Server Transaction Log Fragmentation: a Primer

Generally, you will have no need to worry about the number of virtual log files in your transaction log. However, if you use the default settings for 'auto-grow', you can end up with such 'fragmentation' in your transaction log as to affect performance noticably. How can this be avoided? How can you tell it's a problem? What do you do about it? Greg explains.

2012-11-23 (first published: )

7,126 reads

Technical Article

Performance Tuning Re-indexing and Update Statistics – A Case Study

Recently we started experiencing a very strange issue in our production reporting environment where the Re-indexing and Update Statistics operation suddenly began taking more than 2 days to complete and was thus causing blockage in the database which in turn caused impairment in application performance.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2012-11-20

5,852 reads

Technical Article

SQL Server 2012 AlwaysOn: Multisite Failover Cluster Instance

SQL Server Failover Clustering, which includes support for both local and multisite failover configurations, is part of the SQL Server 2012 AlwaysOn implementation suite, designed to provide high availability and disaster recovery for SQL Server. The multisite failover clustering technology has been enhanced significantly in SQL Server 2012. The multisite failover cluster architecture, enhancements in SQL Server 2012 to the technology, and some best practices to help with deployment of the technology are the primary focus of this paper.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2012-11-16

2,732 reads

Blogs

Speeding Up Patching – Beyond Patch Delivery

By

I wear many hats in technology, and one of those is as a (cyber)security...

Monday Monitor Tips: Query Recommendations

By

We keep adding stuff to Redgate Monitor, and it’s easy to miss some of...

A Pursuit of Lifelong Learning

By

The following came across my YouTube feed today. It’s an interview with General James...

Read the latest Blogs

Forums

Azure SQL Hyperscale Unveiled

By Site Owners

Comments posted to this topic are about the item Azure SQL Hyperscale Unveiled

What is the worst part about existing monitoring solutions?

By Evgenii Vaniukov

Hi. What is the most difficult aspect of using monitoring software like idera, redgate,...

MiniMax m3 and SQL Server

By Daniel Calbimonte

Comments posted to this topic are about the item MiniMax m3 and SQL Server

Visit the forum

Question of the Day

SQL Server Vector Support I

What are vectors in SQL Server 2025, as related to the new AI features?

See possible answers