Tag Info

Hot answers tagged

6

This is a prime reason why different applications should be using different principals to authenticate on. If you use Login1 for 5 applications, then it would become a nightmare to manage security if you ever need those 5 different applications to have different security schemes. My recommendation? Have a separate login for both of those applications. ...


2

I've never heard of comments causing a problem. The code you captured from the running server and the posted source are for different SPs. It makes me think that maybe the ..SU01 version is still in your database and being executed (from a job perhaps?) whereas you are trying to debug the ..SU012_XML code. For testing you could add another INSERT to the ...


2

My initial thought was a logon trigger but, sadly, those only fire after a successful login. The documentation for the Audit Login Failed Event Class says that failed login audits will include the application name, but I haven't observed that so far (I only tested failed logins from changing connections within Management Studio, so maybe it is exposed in ...


2

As pointed above by Jeremy, permissions can almost always be found on the corresponding reference document within Books Online for SQL Server. On these reference documents, there is typically a section titled Permissions (typically towards the bottom of the document) which contains your desired data. CREATE LOGIN (copied directly from the reference) ...


1

This really isn't an SQL Server issue - it seems more of a firewall issue. If you are in a situation where your SQL Servers are directly accessible from dudes in china - I'd be sorting out why no one in your outfit is handling networking/firewalls etc It sounds quite possible that you need to be worried about more servers than just the one you've noticed ...



Only top voted, non community-wiki answers of a minimum length are eligible