SqlServer-QA.net

Here it is first post in the year 2009, still I would like to visit the good old advice of securing your SQL Server environment.  For any user in IT, Security  must be a top priority in order to ensure their PC or environment is secured. You might have heard or aware of SQL Injection attacks, also you might find plenty of good sources ...

You may have seen the sp_replwriterovarbin - New SQL Server Injection-Based Attack Found vulerability about the new public reports of a vulnerability that could allow remote code execution on systems with supported editions of SQL Server 2000, 2005, 2005 Express Edition, 2000 Desktop Engine (MSDE 2000), and Windows Internal Database (WYukon). ...

They say better not to use UNDOCUMENTED stored procedures, which is true in the aspect when any Service Pack or version is released that may not be included and your task might have issues in working out. Similar to this I was going through various methods to get information on login mapping name since SQL Server ...

Recently got stuck with the stored procedure sys.sp_dbmmonitorupdate which is used to monitor the database mirroring session. As usual you could do using the GUI tool, but sometimes using TSQL methods is good enough to see what is happening on your system.   On the system with SQL 2005 Service pack2 when executing this ...

If you need to grant permissions to a login that only needs to view stored procedures (contents not just names of SP's). Further you may not want to grant that login with DB_OWNER or DB_DDLADMIN roles within that database, so how to achieve this task? As usual if that login needs the execute permission you have to ''grant execute'' ...