We published a very interesting article about data warehousing in the SQL Server Standard awhile back. However the article was abridged and the author, a very respected data warehousing professional asked that we publish the entire thing here. So we bring you Harsh Bhaiya's very popular ETL treatise.
If business today is data, then the entire enterprise is in the capable hands of you, the SQL Server DBA. Before you panic, check out Grant's detailed dissection of SQL 2005 backup and recovery regimes.
Pop provides a cunning, trigger-based technique for auditing the activity on SQL Server tables
Among the most common tasks that have not yet been discussed in this series is the Send Mail task, which will be the topic of this article.
With a new name, new capabilities, and a new focus, the product formerly called SQL Server Mobile Edition expands its reach to small-footprint desktop applicationsand it's free!
In response to an editorial on eliminating tape in favor of disk backups, new author Tim OPry brings us a look at his environment and the process by which they eliminated the need for tape in their backup scheme while maintaining a well thought out disaster plan.
It's nice to have little amenities in your development tools. They make for easier development and can save you a little time. Synonyms is one of those tools.
Part 3 of Vincent Rainardi's data warehousing series looks at some of the situations and challenges of loading a fact table in a data warehouse.
In response to a number of suggestions, we have setup new forums where you can ask and comment about the various third party products that you use with SQL Server.
Security has become more and more important in today's business environment. From the database point of view, DBAs and system administrators need an improved security model. SQL Server 2005 provides an improved security feature. It is claimed that SQL Server 2005 is secure by default. In SQL Server 2005, the security model is divided into three areas namely authentication, authorization, and encryption.
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...
Comments posted to this topic are about the item Using OPENJSON
Comments posted to this topic are about the item Data Modeling with dbt for...
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