SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Worst Practice - Bad Connection Strings and Bad Info in Sysprocesses


Worst Practice - Bad Connection Strings and Bad Info in Sysprocesses

Author
Message
JohnWatts
JohnWatts
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 1
My only complaint is that I needed you to write this article about a year ago!

Oh well, such is life.



johnsonj
johnsonj
Right there with Babe
Right there with Babe (771 reputation)Right there with Babe (771 reputation)Right there with Babe (771 reputation)Right there with Babe (771 reputation)Right there with Babe (771 reputation)Right there with Babe (771 reputation)Right there with Babe (771 reputation)Right there with Babe (771 reputation)

Group: General Forum Members
Points: 771 Visits: 1
I've always used the very minimum connection string in my applications, but I ran into the exact problem Andy was talking about -- I had an older version running and had to find it by trial and error. I will definitely be putting the extra info in all my future projects.

Joe Johnson


Joe Johnson
NETDIO,LLC.

Brian McCool
Brian McCool
Valued Member
Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)

Group: General Forum Members
Points: 51 Visits: 1
I've always given thought on how this could be done, but never followed through. This is definately going into our best practices documentation!
Are there any other nifty things (clues) that can be added to the connection string that would show up in sysprocesses?

Brian McCool



Frank Kalis
Frank Kalis
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19295 Visits: 289
Hi there,

the following came right in
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q313295

Thought I'd share it

Cheers,
Frank

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/
Andy Warren
Andy Warren
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: Moderators
Points: 24971 Visits: 2746
Not that I've thought of, but you could really stick any bit of data there that might help you troubleshoot. MDAC version? Client OS? Though you could log that stuff elsewhere, if something like that helps you run down a problem, try it.

Andy
http://www.sqlservercentral.com/columnists/awarren/

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
dforbes@quadtra.com
dforbes@quadtra.com
Valued Member
Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)

Group: General Forum Members
Points: 74 Visits: 1
Having often filled the role of developer in an organization, I find it somewhat offensive that you claim someone is a victim of a "baaaaad developer." If an organization is sophisticated enough to have a dba who monitors database activity from multiple applications, that organization should also have a clearly defined process around how to connect to their databases.
Requirements of a project should include such information. The developer implements what is asked in those requirements.



Andy Warren
Andy Warren
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: Moderators
Points: 24971 Visits: 2746
Not trying to be offensive, though I think its semi-accepted practice for DBA's to complain about developers and vice versa. I'd like to think you're right that in large shops this would be part of the ground rules, not so sure. In any case, my hope is to get people to add it to their base requirements even if they are a 1-2 developer operation.

Andy
http://www.sqlservercentral.com/columnists/awarren/

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
bozo7
bozo7
Old Hand
Old Hand (336 reputation)Old Hand (336 reputation)Old Hand (336 reputation)Old Hand (336 reputation)Old Hand (336 reputation)Old Hand (336 reputation)Old Hand (336 reputation)Old Hand (336 reputation)

Group: General Forum Members
Points: 336 Visits: 1
Not coming from a VB development shop, we use strictly Delphi, I am not familiar with defing the connection like that. You can do it Delphi but there is no reason to. I have noticed however when our research department pulls data into Access.
This has never been a issue for us as we have several .udl files on our file server that the application reads it's connection info from at startup. This allows us to switch SQL Servers rapidly. If one server went down all I have to do is switch the connection properties in the .udl file and everyone is then using a backup server. This came in handy when we upgraded our server this spring.



Ross



Andy Warren
Andy Warren
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: Moderators
Points: 24971 Visits: 2746
UDL's are ok, as are DSN's for that matter, both exist to let you easily edit connection strings. The downside is that they aren't secure if you're using a sql login/password. But that is another discussion!

Andy
http://www.sqlservercentral.com/columnists/awarren/

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
TomT
TomT
SSC-Enthusiastic
SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)

Group: General Forum Members
Points: 169 Visits: 27
Very helpful article. I may have missed this in the thread, but I'm wondering if there's a way to get the workstation id from within an MS Access app?

Thanks



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search