Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a requirement from a customer that only DNS aliases may be used in application connection strings when connecting to SQL Server. Is there any way to enforce this from the server side? The point of doing this is to prevent hardcoding of IP addresses in applications, which may change with time.
Rather than enforce this (as it appears you may not be able to easily), how about auditing it instead.
You should be able to build a little application that will monitor a trace of successful logins. The application could then alert the sys admin / developers etc when a login happens that uses something other than a DNS alias.
This resources may help in terms of tracing this :
http://blogs.msdn.com/sqlprogrammability/archive/2006/08/16/703079.aspx
Cheers