SQL Server 2005 brings a new feature to T-SQL with Common Table Expressions, which make it possible for more complex subquery expressions than in previous versions. Recursion is a common use and Peter He takes a look at how well these new structures perform.
SQL Server expert Jeff Moden discusses a common problem seen in many update statements.
With SQL Server 2005 recently released, one of the things that many people are looking for are some guidelines for working with the new product. New author NandaKishore brings us a list of best practices that should give you a start.
This paper describes the Fuzzy Lookup and Fuzzy Grouping transformations that are part of SQL Server 2005 Integration Services (SSIS). These SSIS transformations are useful for improving the data quality of existing data as well as new data that is being loaded into your database.
Understanding different types of failovers/Role Switching and How do they internally work in database mirroring.
Importing data files is always a challenge for a DBA, especially when the files might vary in format. Having one codebase is important and new author Mark Balasundram brings us the template for a high performance application to do just that.
Scaling out is hard to do with SQL Server, but why doesn't Microsoft build a better solution?
Vote for Service Pack 3!!! For SQL Server 2005. As of now, Microsoft has no plans to release Service Pack 3 for SQL Server 2005. I sent them our poll results, but we need more votes. Let them know this is important by voting on Connect. Vote Now!!!! Update: There's a post that they hear […]
Every organization I talk to has the same problem dressed up in different clothes....
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Comments posted to this topic are about the item The day-to-day pressures of a...
Hello all, I’m looking for advice on how to derive a daily snapshot table...
We need to replace our Windows server running SQL 2017. Any reason not to...
I have some data in a table that looks like this:
BeerID BeerName brewer beerdescription 1 Becks Interbrew Beck's is a German-style pilsner beer 2 Fat Tire New Belgium Toasty malt, gentle sweetness, flash of fresh hop bitterness. 3 Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste 4 Alaskan Amber Alaskan Brewing Alaskan Brewing Amber Ale is an "alt" style beer 8 Kirin Kirin Brewing Kirin Ichiban is a Lager-type beerIf I run this, what is returned?
select t1.key
from openjson((select t.* FROM Beer AS t for json path)) t1 See possible answers