2006-10-06
943 reads
Security
2006-10-05
992 reads
Ownership Chaining
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,366 reads
Ownership chaining in SQL Server 2005
Ownership chains have unique permissions' issues in SQL Server 2005. Contributor Serdar Yegulalp explains the access levels of ownership chains, and the benefits of "EXECUTE AS."
2006-09-29
1,943 reads
2006-09-28
1,018 reads
2006-09-06
890 reads
Improving Data Security by Using SQL Server 2005
Microsoft IT developed strategies to reduce the duplication of sensitive data and improve the security of personally identifiable information in the Microsoft IT LOB application space. These strategies are based on the new security features and functionalities that Microsoft® SQL Server™ 2005 includes.
2006-09-05
2,039 reads
2006-08-02
1,049 reads
2006-07-24
1,304 reads
2006-07-21
1,095 reads
Blogs
How to Parameterize Fabric Linked Services in Azure Data Factory for Azure Devops Deployment
Quite the title, so let me set the stage first. You have an Azure...
Deployment Pipelines in Fabric – What Are They?
By HeyMo0sh
In the realm of software development and content creation, the deployment pipeline serves as...
Forums
A Quick Restore
Comments posted to this topic are about the item A Quick Restore
Guarding Against SQL Injection at the Database Layer (SQL Server)
Comments posted to this topic are about the item Guarding Against SQL Injection at...
Ola Hallengren Index Optimize Maintenance can we have data compression = page
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
Question of the Day
A Quick Restore
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