I don't think that you need permission to view query plan on tempdb if you are using temporary tables. I've just tried it with this code:

create login testing with...

I've given permissions to view query plans to few developers and testers at Dev and QA environments. I admit that it is rare that I'm granting this permission, but...

The 2 backups work differently, so there isn't a connection between the sizes of differential backup and full backup. The full backup will back up the entire database regardless...

If I remember correctly DBCC cleantable reclaims disk space only on tables that varying length columns were dropped from. It doesn't reclaim disk space if the column still exists...

You are using dynamic SQL to construct the SQL Statement that is creating the temporary table. If you are concatenating a variable that is null, the whole statement is...

I tend to agree with your friend. I think that the data type that should be used is the smallest one that can be used and hold all...

In that case, you should use the function datediff.

SELECT datediff(SS,'2012-05-06 11:07:09.313', '2012-05-06 11:07:09.317')

Adi

Check the results of this query:

select CAST('2012-05-06 11:07:09.313' AS DATETIME) - CAST('2012-05-06 11:07:09.317' AS DATETIME)

The result of this query is - 1899-12-31 23:59:59.997. I have to admit that...

The with clause can have a third part that describes the location of the node. If you'll add it, you'll be able to get the data that you want....

You don't need to delete the data. You have to drop the primary key and the index IND_HIM8 before modifying the collation. After you create it you can...

As far as I remember when you rebuild the index the statistics are getting updated, so there is no reason to update the statistics again. If you just reorganize...

One more way, that uses the same logic as Sean, but uses a CTE instead of derived table.

with MyTests as(

select L.Name, TestDate, PfReal, row_number() over (partition by L.Name...

If the indexes that you have were not in use for 3 months as you wrote, then there is no reason to have them and you can drop them. ...

If the user has both deny and grant permissions, the deny wins:-). Check if your user also had deny permissions on the table or if he is a member...

I don’t think that developers should have the permissions in the production environment. They should have permissions on the dev environment, but there is no reason to give them...