Most have been fine. What the case here was that the Books Online entry was misleading. Therefore, if you wrote the question based on that entry, you get the idea....

You shouldn't need to, no.

If you're looking for a complete list, try something like this, otherwise, the function you cited works well for individual securables:

SELECT dperms.*

FROM sys.database_permissions dperms

JOIN sys.database_principals dprins

...

That either means the file no longer exists...

You're potentially getting back multiple rows. Therefore, to execute each row, you need a cursor to loop through them. Here's a good starting point, which also includes an example of...

Brandie Tarvin (11/15/2007)

---

Ahh, who needs access to data anyway! Right? @=)

I love the title of the book you co-authored. "How to Cheat at Securing SQL Server"... ...

SQL Noob (11/15/2007)

---

less constraints is a lot more flexible

we bought out some competitors and it's easier to migrate data to our systems because we don't have to worry about constraints....

Megha Yadav (11/15/2007)

---

Yes I do understand the importance of the foreign keys for maintaining the integrity ................but what the question is that if the system is working without it why...

A couple of reasons:

- Security

- Enhanced Reliability (supposedly)

If you want to return the permissions for the current connection, you don't need to do that. Something as simple as this will work:

SELECT *

FROM sys.database_permissions

WHERE grantee_principal_id = DATABASE_PRINCIPAL_ID()

The quotes are fine. However, if you're trying to execute this in a job, you probably need to use a cursor and then EXECute the returned SQL result.

The trick is to double the single quote. So when inserting, instead of just one ('), you put in two (''). If you are selecting, the same rule applies. You...

There are plenty of articles out on the Internet about why foreign key contraints are good to ensure data integrity. Perhaps this is an opportunity for you to be able...

Given that you only have two disks, I would. However, make sure you expand out the sizes of your user databases so that autoexpand doesn't take place. Otherwise, you may...

Yup, you noted that, too? I think it was a Kevin Kline article I was reading that...