TSQL Recipes – 2014 Edition

Announcing…the book

book_coverAt long last the wait is over. After much blood, sweat and more blood and sweat, the next edition of the SQL Server Recipes book is finished.

This edition brings several changes and quite a bit of re-write. It has been updated for many of the new SQL Server 2014 (well, new, at least until SQL 2016 hits mainstream) features that were added. In addition, we revisited some of the other features that had been omitted from previous editions to try and give it a more encompassing feel.

All of that said, the book is not a comprehensive listing of every command, jot or tittle in SQL Server. There were a finite number of pages and the features in SQL Server just has far too many features and nuances to cover within a single edition.

Despite the limitation of page quantity, we do feel that this is a pretty comprehensive book covering a wide array of features with several examples of how to perform various tasks along with use-cases for when to use the example.

When you crack the covers, you will find examples of how to perform backups to blob storage in Azure, create In-memory OLTP tables, restore from blob storage, and in some cases you will see how to use Extended Events to help with troubleshooting. That is just a small sampling of the contents that fill the almost 900 pages in this book.

Combine this reference book with the previous editions, and you will have an excellent resource for SQL Server.

You can purchase the book on Amazon – here.

Now for the mushy stuff

I am grateful to the folks at Apress for letting us come on board with this book and continue writing about SQL Server and creating a great resource.

I am grateful to the other authors Jonathan Gennick and Wayne Sheffield for helping push this along. The collaboration and support provided by these guys was fantastic. Their patience was also exceptional.

Equally important was the patience and understanding afforded by my family. Writing does take a significant amount of time and they sacrificed so I could continue on this project.

Thanks to all these folks for helping make this a great achievement!

Cloud Nirvana

Comments: 1 Comment
Published on: November 12, 2013

TSQL2sDay150x150T-SQL Tuesday is a recurring blog party, that is started by Adam Machanic (Blog | @AdamMachanic). Each month a blog will host the party, and everyone that want’s to can write a blog about a specific subject.

This month the subject is “Cloud Atlas”. If you want to read the invite, please click the image below to go to the party-starter: Jorge Segarra (Blog | @SQLChicken).

For me, this will be a quick entry on my part to participate.  I have a mixed bag of feelings about the Cloud and the buzz-wordiness that implies.

mushroomDisaster Struck

One of my biggest concerns with the cloud is the gloom and doom that has been felt by a client after a bout of corruption struck their database.  The person on staff responsible for backups did a fantastic job of ensuring the database was backed up on a daily basis.  That is not the doom and gloom sadly.

This particular case turned sour after corruption hit the database.  The web application no longer connected to the database.  The data was corrupt.  The database was inaccessible.  The client was distraught and sweating bullets.  The client and the employee new not what to do so they sought me out to get some help.

After an assessment, we determined that the database needed to restored from backup.  All of the backups were done fastidiously – to the cloud.  The backups were only accessible through a specific application and the process required copying the backup from the cloud down to the server via the application.  The process is pretty easy, right?

The recovery of the database took an entire week!  The copy down through the application from the cloud was destructive to the business to say the least.  The company had little to no chance of surviving being out of business for the outage caused by this scenario.


On the more positive side, there may be a silver lining to the cloud for many people.  I have done more than my share of successful Cloud migrations.  I have also seen many applications work very well from the Cloud.

One benefit to me personally about the Cloud is the ability to quickly spin up resources or even servers.  Much like a VM farm, I can request more resources for a Server during specific workload times.  And I can also dial down the gauges a bit when the workload is less intense.

I really like the idea of spinning up a machine in a matter of a few clicks and minutes.  When SQL 2014 released CTP2, this was fantastic.  I know several people took advantage of this ability and began playing with CTP2 almost immediately after the announcement of the CTP2 release.

Is the cloud right for you?  I can’t say.  I have had success and failure related specifically to the cloud that might not have happened in a less “nimble” environment.  The decision to move to the Cloud is frequently the decision made by somebody other than the technologist that must support the technology and the decision.  If you are moving to the Cloud, you may succeed and enjoy it or you may fail and hate it.  Your mileage will vary.

page 1 of 1

March 2017
« Jan    


Welcome , today is Sunday, March 26, 2017