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

Blogs

Dynamically Unpivot columns in SQL

By

Picture this, your data ingestion team has created a table that has the sales...

Friday Basics: RPO and RTO

By

I did a post last month titled RTO and RPO are myths unless you've...

A New Word: ioia

By

ioia – n.the wish that you could see statistics overlaid on every person you...

Read the latest Blogs

Forums

SQL Server Encrypt data into a file, send it and then decrypt

By GBeezy

First off, my apologies for what could potentially be a bad title! I am...

Table partitioning best practice

By JasonO

I've inherited a couple of rather large databases from my ex-colleague when I join...

Identifying Customer Buying Pattern in Power BI - Part 2

By Farooq Aziz

Comments posted to this topic are about the item Identifying Customer Buying Pattern in...

Visit the forum

Question of the Day

Finding Marks

I have marked a few transactions in my code. How can I find out which marks were stored in a transaction log?

See possible answers