Hi

If a user has no permissions on the tables, he cannot even see them in the wizard.

No way he can export data.

I cannot imagine a bug this big.

Remember, when running...

I would like to add my 2 cents:

Whenever I can, I recommend against more than drive letters C and D and advice to use mount points for everything. It’s hard...

That's the way 🙂

johntam (9/24/2013)

Andreas.Wolter (9/24/2013)

I guess instead of Tables you want to give permissions on the views that you mentioned.

You might just as well put them into 2 different schemas.. keeps the...

Ok

I guess instead of Tables you want to give permissions on the views that you mentioned.

You might just as well put them into 2 different schemas.. keeps the permissions on...

vax09 (9/19/2013) I need to create a report in which I need to hide the column data base on who userid.

for example if Manager want to see the report then...

Well,

if you already know all about only granting access to only the data they really do need to see – preferably via views or stored procedures, then what else would...

With high lock wait times, you MIGHT have a chance by checking the system_health Extended Events session - if you are on SQL Server 2012. Because in 2012 onwards there...

Ok. I you say both is there, it might be so. But then why should the error come up.

Other than that it might be a case-sensitive instance, I have no...

dave-L (9/15/2013)

Is there a way for my to track down which query plans are generating the increased number of hash joins, or some how see what exactly is creating these...

This should not be.

Also adding the same user with renamed Windows-Level Login-Name...

You may want to share the errors that you are getting.

You have to fix them one by one, unless one builds upon the other.. which nobody can tell from this...

Oh yes, it's a really important proc.

And it's there since V2000 at least I think 😀

Yes, ALTER LOGIN is supposed to be the replacement, but it does not do the...

Maybe it's the issue of non-matched SIDs?

You can use the proc sp_change_users_login to find out: http://technet.microsoft.com/en-us/library/ms174378.aspx

On SQL Server 2008R2 Standard Edition (SP2 I hope), you have only 1 ½ options:

- A custom SQL Trace session (which you can prepare using Profiler) and then have to...