Administration

SQLServerCentral Article

Worst Practice - Bad Connection Strings and Bad Info in Sysprocesses

  • Article

Andy returns to the Worst Practice series this week with a short article looking at how connection strings in applications affect what you see in sysprocesses. Perhaps less controversial (in our opinion) that some of the other worst practices, this is something easy to fix and definitely worth fixing! Read the article and post a comment - explore other points of view! Readers posting a comment will be entered in a drawing for a copy of the SQL Server 2000 Resource Kit.

You rated this post out of 5. Change rating

2003-08-01

15,782 reads

Blogs

Local LLM Models at SQL Saturday Boston 2025

By

I’m starting a long trip at Boston this weekend. I’ll be there Saturday speaking,...

3 things you must do to start data quality management right

By

As a data & AI strategist who’s seen countless projects succeed and fail, I...

Set Theory vs. Batch Mode in SQL Server

By

Set Theory vs. Batch Mode in SQL Server Not long ago,...

Read the latest Blogs

Forums

Changing the Recovery Time

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing the Recovery Time

Getting More Time from AI

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Getting More Time from AI

When Page Prefetching Takes a Back Seat – Exploring Trace Flag 652 in SQL Server

By Chandan Shukla

Comments posted to this topic are about the item When Page Prefetching Takes a...

Visit the forum

Question of the Day

Changing the Recovery Time

I want to change the recovery time for a database running on SQL Server 2022. What are my options for setting the value in my ALTER DATABASE statement. If I run this code, what can I use in place of the xxx to define what 12 means?

ALTER DATABASE Finance 
 SET TARGET_RECOVERY_TIME = 12 xxx;

See possible answers