venu_hs:

I generally google for connection strings and come up with a page like: http://www.connectionstrings.com/sql-server-2008, then start trying variations on the connection strings. If you look at the error messages and/or tracing information (see http://search.cpan.org/~mjevans/DBD-ODBC-1.41/ODBC.pm#Tracing), the error messages generally guide you to the incorrect parameter.

For example, assuming everything is set up properly, and you're getting the original message "Requested server name not found", then I'd look at the spelling of the server name you specified. If the spelling is correct and you're using a name rather than IP address, I'd try pinging the name using the same account your program runs under to see if it can access the machine.

Unfortunately, there are so many different settings and potential connection issues, that it's rather hard to guide you through them. So start with the basics.

I'd suggest starting with DBI turn on as much diagnostic tracing as possible, and then ask it to enumerate the drivers it knows about. Once you're sure it's listing ODBC, then ask it what ODBC data sources are available. If it lists any, try to connect to one and see what sort of diagnostics you get.

...roboticus

When your only tool is a hammer, all problems look like your thumb.