External Article

Do you regularly run queries and scripts in SSMS?

SQL Server Management Studio is where most SQL scripts and queries are run, and although it does a decent job, it doesn't provide much help storing, sharing and managing the scripts particularly in the context of a team. Red Gate is considering building functionality into SSMS to help its users consume and share queries and scripts. Please help us by completing this short survey to help us define the requirements.

SQLServerCentral Article

Brad's Sure Guide to SQL Server 2008

SQL Server 2008 has hundreds of new features and improvements for Production DBAs, Developer DBAs, and Business Intelligence specialists…in this book I focus on what I thought were the ten most important new features for Production DBAs.

SQLServerCentral Editorial

Driving Value

Does your IT organization bring value to your company? Steve Jones takes a look at some of the ways you can do this. This editorial was originally published on July 2, 2008. It is being re-published as Steve is at SQL Intersection.

Blogs

Capturing My Own Metrics: #SQLNewBlogger

By

A customer was trying to compare two tables and capture a state as a...

Red Flags in Your Query (T-SQL Tuesday #200)

By

When I'm looking at a query, I bet it's bad if I see... a...

T-SQL Tuesday #200: When I Look at a Query …

By

This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...

Read the latest Blogs

Forums

A Quick Second Opinion

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Second Opinion

Five Intelligent Query Processing Features in SQL Server 2022 That Quietly Tune Your Workload

By vgupta

Comments posted to this topic are about the item Five Intelligent Query Processing Features...

Checking the Error Log I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Checking the Error Log I

Visit the forum

Question of the Day

Checking the Error Log I

On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?

See possible answers