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
T-SQL Tuesday #198–Change Detection
By Steve Jones
This month we have a new host, Meagan Longoria, who graciously agreed to help...
Redgate and Rome
By Steve Jones
I’m at the UK Redgate office today, meeting with senior leaders in all areas...
Quick Tip: Check Most DTU Expensive Queries in Azure SQL Database
Optimizing Azure SQL Database performance often begins with identifying the most resource-intensive queries. Understanding...
Forums
How Important Is a Google Knowledge Panel for Online Reputation?
I’ve been learning more about the google knowledge panel and it seems like one...
Which Wireless Credit Card Terminal Works Best for Small Businesses?
I’m currently researching the best wireless credit card terminal for a growing business and...
Creating a JSON Document IV
Comments posted to this topic are about the item Creating a JSON Document IV
Question of the Day
Creating a JSON Document IV
I have this data in a table called dbo.NFLTeams
TeamID TeamName City YearEstablished ------ -------- ---- --------------- 1 Cowboys Dallas 1960 2 Eagles Philadelphia 1933 3 Packers Green Bay 1919 4 Chiefs Kansas City 1960 5 49ers San Francisco 1946 6 Broncos Denver 1960 7 Seahawks Seattle 1976 8 Patriots New England 1960If I run this code, how many rows are returned?
SELECT YearEstablished, json_objectagg(city : TeamName) FROM dbo.NFLTeams GROUP BY YearEstablished;See possible answers