More in Development

  • SQL Server data storage rack
    Jun 26, 2012
    blog

    Disk Space Monitoring: How To 1

    Keeping tabs on available disk space on your SQL Servers is something that every DBA should do—because once SQL Server runs out of disk on the underlying host, then everything obviously comes to a crashing halt....More
  • Jun 14, 2012
    blog

    SQL Server Database Corruption, Part XIII: RECAP

    One of the things I wish I had done a bit better in my previous ‘series’ of posts on SQL Server database corruption was provide better links and cohesion between posts—or a ‘table of contents’ at the top or bottom of each post—just because I always appreciate similar efforts when I stumble upon a series of posts via a set of keywords I’m searching for and so on....More
  • May 31, 2012
    blog

    SQL Server Database Corruption, Part XII: Recovery Sample 2

    In my last post in this ongoing series on SQL Server database corruption I mentioned that my next post would be to provide a ‘soup to nuts’ sample or example of how you can test corruption and recovery in your own environment – as a means of better getting familiar with exactly what corruption is, what it looks like, and how to address it....More
  • green corrupt data illustration
    May 25, 2012
    blog

    SQL Server Database Corruption, Part XI: Full Recovery Operations 1

    In part 9 of this series on SQL Server database corruption I defined a list of key things to do when responding to database corruption. And in that list of options and operations was the mention that in some cases you may have to revert back to using a full-blown recovery operation – meaning that you’ll need to completely restore your database from scratch....More
  • table data on white piece of paper
    Feb 27, 2012
    blog

    How about Filtered Indexes instead of Partitioning?

    Filtered indexes are an incredibly powerful feature (one of my favorites) so I don't want to dissuade you from using them. A table can be partitioned using the partitioned tables feature. A table can be broken into multiple tables and then unioned (UNION ALL) in a view using the "partitioned views" feature....More
  • Feb 9, 2012
    blog

    Solutions to VLT concerns around statistics and maintenance! 2

    Let's tackle why partitioned views can be a fantastic choice for partitioning large sets—even for new design....More
  • illustration of data with colorful numbers in background
    Feb 2, 2012
    blog

    Partitioned Tables v. Partitioned Views–Why are they even still around? 2

    Partitioning is CRITICAL for VLT. What is VLT? It’s about as descriptive as VLDB and it means very large table. Most people speak of VLDBs (very large databases) and they define that as databases that are 100s of gigabytes (many would say that a database that’s 1TB or larger is a VLDB)....More

Digital Magazine Archives

Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.

 

From the Blogs
business people around a table and laptop
Oct 9, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 10: Dynamic Detection Gotcha #3

You can interject a SQL Server Job Step into your Jobs and have this new/injected Job Step do some checking for you. Here's a look at everything that’s involved in such an approach....More
Man holding a piece of paper with the word GOTCHA
Oct 7, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 9: Dynamic Detection Gotcha #2 3

Given that a USE statement is parsed before code is actually run, there are a few options that could be used as a around when it comes to detecting whether or not code should be run....More
iceberg
Oct 2, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 8: Dynamic Detection Gotcha #1 1

Learn about why the option of dynamically detecting whether or not to run a SQL Server Job at execution time is quite a bit more problematic than you might think....More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×