Articles

SQLServerCentral Article

SQL 2000 to SQL 2005: Where have all the old features gone?

SQL Server 2005 is out and everyone is moving to test and deploy it. However many people are still managing SQL Server 2000 instances. New author Boris Baliner brings us a few tricks to find that information you are used to from Enterprise Manager.

(1)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

35,485 reads

SQLServerCentral Article

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.

(3)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

39,498 reads

SQLServerCentral Article

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.

(1)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

40,354 reads

SQLServerCentral Article

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.

(14)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

76,843 reads

SQLServerCentral Article

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.

(22)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

45,856 reads

Blogs

PlanTrace: Stop Reading Redshift EXPLAIN Plans. Start Seeing Them

By

PlanTrace: Stop Reading Redshift EXPLAIN Plans. Start Seeing Them Introducing PlanTrace — a free, browser-based...

A Cloud Dependency Failure from Amazon

By

I went to sleep while reading a Kindle book on my phone. I know...

Deploying AI in logistics (the unfiltered version)

By

A conversation with Jan Laš, CIO at HOPI, about what deploying a data agent...

Read the latest Blogs

Forums

SPAM Issues May 2026

By Steve Jones - SSC Editor

We suffered a SPAM attack from May 1-6, which unfortunately corresponded with time off...

SQL Password enforcing

By Andre 425568

Hi to all We have situation at a client where someone is illegally changing...

SQL Password enforcing

By Andre 425568

Hi to all We have situation at a client where someone is illegally changing...

Visit the forum

Question of the Day

Creating a JSON Document III

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      1960
If I run this code, how many rows are returned?
SELECT TOP 2 
  json_objectagg('Team' : TeamName)
FROM dbo.NFLTeams;

See possible answers