SQL Server and SOX
The Sarbanes-Oxley act has changed many IT jobs, usually requiring more work and documentation. Johan Bijnens brings us a list of some things his team has had to do to comply with SOX regulations.
SQL Server Auditing - Part 1
Our SQL Server Security expert, Brian Kelley, brings us the first part of a new series on auditing. Most of the auditing articles we've had are based on how you audit changes to data. Brian looks at auditing from the server itself, explaining the different levels of auditing built into SQL Server 2000.
SQL Server Security Part 1
In this series of articles, Chris Kempster will discuss some of the finer aspects of SQL Server security and also touch on OS, physical and application security to open up this science for general discussion.
SQL Server Security: Server Roles
As yo probably know, Brian covers security topics for us and does a great job. This week he looks at the fixed roles and points out a few things you may not have thought about.
Stored Procedure vs Triggers
Performance tuning is an ongoing battle in SQL Server, but having a little knowledge up front when designing an application can greatly reduce the efforts. Do you know which performs better: stored procedures or triggers? There aren't many places where the two are interchangeable, but knowing the impacts of each might change the way you build an application. Read about this analysis by Vijaya Kumar.
Temp Tables in SQL Server
This is an entry level look at how temp tables work in SQL along with some tips about how to use them effectively.
The Best Kept Secret About SQL Query Analyzer
It has been nearly 5 years since SQL Server 2000 was released and almost seven since Query Analyzer was introduced in SQL Server 7. Surely every trick, tip, technique, or secret has been published by now? Perhaps, but this might be a new one from Yakov Shlafman. Check out what he thinks is the best kept secret.
The GO Command and the Semicolon Terminator
There are probably not many SQL Server DBAs that use the semicolon as a statement separator. In SQL Server 2005, this is required in certain places and new author Kenneth Powers brings us a look at where and why you need to use this syntax.
Tracing Deadlocks
New Author! Deadlocks aren't the most common problem but they happen they can really degrade performance. Shiv works through how to nail down what is causing the deadlock.
Transactions in SQL Server 2005 Integration Services
SQL Server 2005 no longer has DTS. Instead, the next evolution of ETL tools from Microsoft is Integration Services, with many enhancements and capabilities, far beyond what was available in SQL Server 2000 DTS. New author Jamie Thomson brings us a look at the transaction capabilities of SQLIS in Yukon.
Blogs
Why your data still can’t answer a simple question
Every organization I talk to has the same problem dressed up in different clothes....
T-SQL Tuesday #197 Invitation – An impactful session or two from a conference
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
Did You Really Name That Default?
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Forums
The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI
Comments posted to this topic are about the item The day-to-day pressures of a...
Using OPENJSON
Comments posted to this topic are about the item Using OPENJSON
Data Modeling with dbt for Visual Code: The Fabric Modern Data Platform
Comments posted to this topic are about the item Data Modeling with dbt for...
Question of the Day
Using OPENJSON
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