October 31, 2007 at 12:52 pm
A standard SQL login is shared amongst a group of developers to gain access to a development database. The developers write their application to use this login, and hard-code the user name and password into the connection string of the application. At a later date, its decided that only the application running from a particular host should use this login and password, and no other developers should use it. Which SQL Server 2005 SP2 feature should be used to prohibit access to the database server if the connection is made from any other host than the application host?
October 31, 2007 at 1:38 pm
- a (serverlevel) login trigger may server you very well
- a simple change of password may also do the trick if your applications support extrenalised credentials/passwords.
- and if I'm correct, even ssl-certificates can help out (check bol)
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply