Hope this article will help give you some idea about the error: https://support.microsoft.com/en-us/kb/3027860

If you will load a ssis package from a SQL Server, under a proxy account, be sure to grant to that user db_ssisoperator on msdb database.

Take a look at this link, this link will show you cause of Syntax error and how to fix it: http://www.sqlmdfviewer.org/fix-error-sql-syntax.html

This problem could be an issue with the database page or a problem with the SQL Server engine when determining what the expected allocation unit should be.

Take a look at this article hope this will help you out:

http://henkvandervalk.com/how-to-increase-the-sql-database-restore-speed-using-db-compression-and-solid-state-disks

Database> Tasks> Generate Scripts > Next > Next

On Choose Script Options UI, under Table/View Options Heading, set Script Triggers to True.

Take a look at these links: https://dbamohsin.wordpress.com/2009/02/20/tempdb-full-%E2%80%93-how-to-clear-tempdb-log-in-sql-server-2005/ [/url]

http://www.sqlserverlogexplorer.com/error-9002-transaction-full/ [/url]

Check out the following link maybe this will help you out: http://blog.sqlauthority.com/2016/01/26/sql-server-timeout-expired-the-timeout-period-elapsed-prior-to-completion-of-the-operation-or-the-server-is-not-responding/[/url]

You can open the properties dialog in Enterprise Manager and click "Permissions..."

Take a look at this article hope this will help you out: https://sites.google.com/site/pankajdbablog/sql-server-administration/installing-and-configuring-sql-server-2008/the-parameter-is-incorrect-0x80070057-in-sql-server-configuration-manager

Check out the following article hope this will help you: http://www.sqlmdfviewer.org/fix-error-sql-syntax.html

Check out the following links to shrink temp db in various ways: http://dbadiaries.com/how-to-shrink-tempdb

This error usually occurs when a Partition Scheme has been assigned to the filegroup, that you are trying to remove.

So delete the Partition Scheme that is using the filegroup.

Check the following things

>> Monitor this password reset activity using PROFILER for SA activities.

>> May be some policy is running on the database server to change the password try to...

Check out the following article maybe this will help you out: https://www.mssqltips.com/sqlservertip/3171/identify-sql-server-databases-that-are-no-longer-in-use/[/url]