2015-05-29
1,377 reads
2015-05-29
1,377 reads
2015-05-21
1,254 reads
It is no good doing some or most of the aspects of SQL Server security right. You have to get them all right, because any effective penetration of your security is likely to spell disaster. If you fail in any of the ways that Robert Sheldon lists and describes, then you can't assume that your data is secure, and things are likely to go horribly wrong.
2015-05-13
9,527 reads
Sometimes you need to reach outside a database and access data and objects from multiple databases, which raises some security issues and increases the complexity of data access. In this stairway level, you’ll learn about cross-database ownership chaining so that you can reach across database boundaries securely.
2024-05-08 (first published: 2015-04-08)
11,339 reads
2015-03-25
1,774 reads
2015-03-19
1,979 reads
2015-02-10
1,654 reads
2015-02-09
1,616 reads
2015-02-05
1,905 reads
Database ownership is an old topic for SQL Server pro's. Check this simple lab to learn the risks your databases can be exposed to.
2015-01-29
11,435 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