Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When I'm logged into our Windows Server 2003 server, I don't see any ODBC Data Sources, but when a different user logs in (who doesn't have Administrative rights), they have a big list of ODBC Data Sources.

Are ODBC Data Sources set on a per-user basis? How come the Administrator can't see user's ODBC Data Sources?

EDIT: Thanks for the replies. The Answer was staring me in the face :-)

share|improve this question
up vote 4 down vote accepted

You can set ODBC sources by either System or User. Check the ODBC connection definitions under Control Panel -> Administrative Tools -> ODBC. You'll see seperate tabs for 'User' and 'System' DSNs.

You can check out a users ODBC connections in their registry hive under SOFTWARE\ODBC

share|improve this answer

ODBC data sources can be defined per-user or per-system.

When you launch the ODBC manager, you'll see "System DSNs" and "User DSNs".

System DSNs are defined for the whole system, so any user and system services can use them (but only an Administrator can define and manage them).

User DSNs are defined per-user, any user can create them, but only their owner can use and manage them.

share|improve this answer
Argh, the infamous DSN/DNS mistake... thanks, Graeme :-) – Massimo May 13 '10 at 21:03
No problem. Muscle memory is a real bummer sometimes. ;-) – ThatGraemeGuy May 13 '10 at 21:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.