Try to use the second option in the SSMS i.e "Reorganize Pages before releasing Unused Space". This will de-fragment the file by moving all the used pages to the front...

The .bak might have corrupted during the move or the file move might not have completed 100%.

Try to zip the .bak file, copy, unzip and then restore from the local...

You are absolutely right. In 95% of case it will not release space. What it does is just find the last used page in the file and chop the file...

Shrink the File with "Release Unused space" option which is the default option in the SSMS. Don't use Reorganize option which is the second one in SSMS.

...

Shawn is correct.

SQLBuddy

Check the LAST execution time column for the queries and then match it with the time of slowdown.

...

To check most expensive queries by CPU time check

http://blog.sqlauthority.com/2010/05/14/sql-server-find-most-expensive-queries-using-dmv/

Also you need to check for the extended blocking happening which could cause app timeouts. Also chek whether the server is...

Hi Sushanth,

As alvin said there is no going backwards once...

Check the SQL Server Error Logs or Windows Application or System Log to find the possible reason.

...

Instead of removing the Group, you can remove the sysadmin privilege from the BUILTIN\Administrators group.

But before doing so make sure that you know the sa password or you have...

DEVELOPER EDITION = ENTERPRISE EDITION with a caveat that you cannot use Developer edition for production purpose.

You can create and restore them on Dev edtio too.

SQLBuddy

AgentXP's should not be disabled. They are required for the nodes of the SQL Sever Agent to appear in the SSMS. If you disable them you can't manage Agent nodes...

That's not true. It can be used on 32 bit systems too.

...

If the box is dedicated for SQL Server then grant "Lock Pages in Memory" privilege to the SQL Server engine service account.

...

DTA requires atleast DBO privileges on the part of the user.

Thank You,

Best...