Articles

External Article

Managing SQL Server Backup and Restore History Information

Greg Larson explains that SQL Server provides a couple of different ways to delete backup and restore history. If you want to remove backup and restore information for all databases based on a date you can use the sp_delete_backuphistory system stored procedure. Or you can use the system stored procedure named sp_delete_database_backuphistory if you want to remove all backup and restore history for a specific database.

2016-10-04

5,098 reads

External Article

Predicates With Subqueries

The ALL, SOME and ANY predicates aren't much used in SQL Server, but they are there. You can use the Exists() predicate instead but the logic is more contorted and difficult to read at a glance. Set-oriented predicates can greatly simplify the answering of many real-life business questions, so it is worth getting familiar with them. Joe Celko explains.

2016-10-03

8,250 reads

External Article

SQL Server for Linux

Although SQL Server for Linux removes the concern that adopting SQL Server forces you to also adopt the Windows platform, it could also provide a useful alternative platform, and a more obvious alternative to Oracle. There are, however, several obvious concerns as to how such a product could ever achieve parity with the existing Windows-based product. Microsoft have made an interesting move with several ramifications, as Robert Sheldon explains.

2016-09-30

6,963 reads

External Article

PowerShell Desired State Configuration: DSC Resources

Desired State Configuration (DSC) allows you to automate the way that you manage configuration data for software services as well as the environment in which these services run. DSC uses a set of built-in and custom 'resources' as the building blocks for a configuration. If you have specific requirements you may need to create the relevant resource to make the configuration happen. Nicolas Prigent provides a practical guide to DSC resources.

2016-09-27

3,764 reads

External Article

Querying Multiple MySQL Tables

It’s been said that one of the drawbacks to normalization to the third form (3NF) is more cumbersome data extraction due to the greater number of tables. These require careful linking via JOIN clauses. Improper table joining can easily result in erroneous results or even in the dreaded Cartesian Product. In today’s article, Rob Gravelle explores how table joins are achieved in MySQL.

2016-09-23

3,720 reads

Blogs

Scaling PowerShell – Lessons from a Technical Interview

By

Recently, I was in a technical interview where the topic of running PowerShell at...

Installing Old Versions of PowerShell Modules with Their Dependencies

By

I don’t recall where this came up (probably in SQLSlack), but I had a...

In Memory of Andrew Clarke, AKA Phil Factor

By

One of the parts of getting older that really sucks is I seem to...

Read the latest Blogs

Forums

SQL Server, Heaps and Fragmentation

By dbakevlar

Comments posted to this topic are about the item SQL Server, Heaps and Fragmentation

Stairway to Azure SQL Hyperscale – Level 2: Page Server Architecture Explained

By Chandan Shukla

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

Pushing the Limits of AGs

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pushing the Limits of AGs

Visit the forum

Question of the Day

SQL Server, Heaps and Fragmentation

A table without a clustered index (heap) will NOT suffer from fragmentation during frequent updates or deletes. True or False?

See possible answers