2006-10-09
1,072 reads
2006-10-09
1,072 reads
2006-10-06
944 reads
2006-10-05
992 reads
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,403 reads
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,019 reads
2006-09-06
893 reads
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,050 reads
2006-07-24
1,305 reads
By ReviewMyDB
A behind-the-scenes look at Day of Data Jacksonville 2026, the transition from SQL Saturday,...
You run EXPLAIN ANALYZE on a slow query, stare at the plan, and something...
By Steve Jones
la guadière – n. a glint of goodness you notice in something that you...
hi, we couldnt get our upstream data source developers to supply what is sometimes...
Are there any good articles on all the trace flags that are enabled on...
Comments posted to this topic are about the item The Data Model Matters
I run the SQLCMD utility as follows:
lcmd -S localhost -EI then type this (the 1> is the prompt):
1> select @@version goIf I hit enter, what happens? See possible answers