Security in SQL Server is not too complex, following a fairly simple framework for allowing and preventing access to data. However there are a few places where it can get tricky and some concepts that many people do not understand. Rob Farley brings us an explanation of one of those areas: ownership chaining. Read about how ownership chaining can be useful and also how it may open security holes in your environment.
2006-10-03
6,365 reads
SQL Server provides a decent ROUND function to help you cut off numbers after the proper number of decimal points. But what if you don't know how many decimals the number will have? Author Rob Farley brings us a UDF he built to do just this.
2006-07-25
19,705 reads
SQL Server 2005 has a new administrative tool called Management Studio, with many enhancements and changes from Enterprise Manager. But it's not just for SQL Server 2005 as new author Rob Farley shows us how to use this tool with SQL Server 2000.
2006-06-26
13,505 reads
Next Monday, March 9, 2026, my one-day live online training SQL Server 2025 Unleashed:...
By HeyMo0sh
As someone who’s worked with data for over 20 years and with many cloud...
By HeyMo0sh
2025 belongs to the AI startups. If you peek into the tech headlines, you’ll...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers