My new article for SQL Server Magazine on Hardening SQL Server has been posted online and will appear in an upcoming print issue. This article is a brief explanation of how to secure SQL Server against malicious attack or invasion. This article can serve as a guide for preventing your SQL Servers from being compromised. Excerpt from Article Hardening SQL Server SQL Server applications rely on data, and protecting that data has never been more important than it is today.
When Does Trustworthy Get Reset on a Mirror? When I’ve done sessions on automating database mirroring processes and in my book, I talk about incorporating steps to set properties that get reset during the restore process in the mirroring setup such as database owner and the Trustworthy property. When you perform the initial restores of the database to set up mirroring, the database owner is set to the account of the person performing the restore, and if Trustworthy is enabled,
Product Review: Security Explorer by ScriptLogic Recently, I started writing for SQL Server Magazine. A couple of days ago, my first piece for the magazine was posted online. It is a product review of Security Explorer by ScriptLogic. I have just completed the first draft of future article and am beginning work on another. Excerpt from Article Security is a source of frustration for DBAs. They’re frequently asked who has what permissions in which databases and servers. Determining this information
SSIS access permissions are managed via Component Services. It is the DCOM object named MSDTSServer. Here are the steps to follow: Run Component Services -> Computers -> My Computer -> DCOM Config -> MSDTSServer Right click on MSDTSServer Click properties Click on the Security tab Select Customize and add the users/groups to the Launch/Activation and Access tabs accordingly Add the user to the local Distributed COM Users group Restart the SSIS service