Part 2 of new T-SQL enhancements from Srinivas Sampath. SQL Server 2005 contains a number of enhancements designed to allow you to write more powerful queries while keeping the code structured in a way that makes development and understanding it easier. Building on his first look at Common Table Expressions, Srinivas now looks at recursive queries with CTEs.
2008-04-18 (first published: 2005-03-03)
94,337 reads
One of the more interesting new features in SQL Server 2005 is the Service Broker. It's not something to help you manage your financial future, nor is it some new program that handles all the instances and their accounts. It's a message queue and SQL Server MVP Srinivas Sampath brings us a look at this new feature with some code to get you going.
2007-12-14 (first published: 2005-06-30)
32,436 reads
The next evoution of T-SQL, which will be released in SQL Server 2005, contains a number of enhancements designed to allow you to write more powerful queries while keeping the code structured in a way that makes development and understanding it easier. Coming ever so closer to the SQL-99 specification with Common Table Expressions, new author Srinivas Sampath brings us an introduction to this new way of writing complex queries.
2007-09-22 (first published: 2005-03-02)
50,884 reads
One of the less exciting, but perhaps very powerful new features in SQL Server 2005, the Service Broker is an asynchronous communications method. MVP Srinivas Sampath brings us the second part of his series looking at what you can accomplish with a practical example.
2005-08-30
13,109 reads
By DataOnWheels
My first time at SQL Saturday New York City was an absolute blast! Thank...
By Chris Yates
Businesses rely on data for decision-making and strategy, but data silos hinder productivity. These...
Hi, I have a workstation with SQL Express 2019 installed and I have a...
Hello - I have attached a Word document here with details about my issue....
I am having trouble writing linking the MAX query that I created back to...
If I want to delete a log shipping secondary server where only one database is used to restore the logs, what should I do?
See possible answers