SQLServerCentral Editorial

The Ad Hoc Change

Almost every DBA will be asked to change data in production at some point. Too often we don't have the tools to allow users to correct errors, but when you make changes, Steve Jones reminds you that you need to be careful and still have a process.

External Article

Using Extended Events to troubleshoot SQL Server issues

As a DBA, you'll encounter elusive performance, connectivity and locking problems that you'll need to troubleshoot. There are many tools that you can use such as Profiler. In addition to these tools, SQL Server 2008 offers extended events ("XEvents"), which you can use as a powerful tracing system. By default, the "system_health" extended events session is always on, and can provide you help to locate the source of trouble much faster.

Blogs

Database AI Agents: The Read-Only Rule

By

Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...

Creating a SQL Stored Procedure to Load a SCD2

By

This is a blog that I am writing for future me and hopefully it’ll...

Funny Money: #SQLNewBlogger

By

While wandering around the documentation looking for some Question of the Day topics, I...

Read the latest Blogs

Forums

Pro SQL Server Internals

By Site Owners

Comments posted to this topic are about the item Pro SQL Server Internals

SQL ART: Who's Blocking Who? Visualising SQL Server Blocking With Spatial Geometry

By Terry Jago

Comments posted to this topic are about the item SQL ART: Who's Blocking Who?...

Running SQLCMD II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Running SQLCMD II

Visit the forum

Question of the Day

Running SQLCMD II

I run this command to start SQLCMD:

sqlcmd -S localhost -E -c "proceed"
At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version
2> go
What happens?

See possible answers