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,787 reads

Blogs

The First Steps: Understanding the Basics of FinOps

By

As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...

Monday Monitor Tips: AI Query Analysis

By

AI is everywhere. It’s in the news, it’s being added to every product, management...

AI: Blog a Day – Day 8: RAG – Retrieval Augmented Generation

By

RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...

Read the latest Blogs

Forums

would it be so terrible to install ssms on a few user desktops?

By stan

Hi, ssms is free here.   I can think of other reasons to do this...

I'm thinking about submitting some articles

By Doctor Who 2

I've written some documentation on using different Markdown types of files on GitHub. It's...

Not Just an Upgrade

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Not Just an Upgrade

Visit the forum

Question of the Day

Restoring On Top I

I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?

USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO

USE DNRTest
GO
CREATE TABLE MyTest(myid INT)
GO
USE master
RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE

See possible answers