Have a look at this link

http://dba.stackexchange.com/questions/88982/how-to-repair-database-consistency-errors

sp_RENAME 'dbo.AllocationDetails.[[Conversion_Fee]]]' , 'Conversion_Fee', 'COLUMN'

Disable firewall from Start > All programs > Microsoft SQL server > Configuration Tools > SQL server configuration manager> SQL server network configuration > Select protocol

> Enable TCP\IP

>...

take a look at this link: https://support.microsoft.com/en-us/kb/314546

Sometimes this error message occurs due to network traffic on the server. In such situation you need to change the Time

select left(name, charindex('_',name)-1)

from tempdb..sysobjects

where charindex('_',name) > 0 and

xtype = 'u' and not object_id('tempdb..'+name) is null

> Install Windows Updates

> After the updates are installed, restart your computer

> Download the Visual C++ Redistributable

> Run the vc_redist.x64.exe (64-bit) or vc_redist.x86.exe (32-bit) and select Uninstall

> Run the .exe...

Take a look at this link, hope this will help you: http://stackoverflow.com/questions/13307589/unable-to-access-stored-procedures-on-localhost

you can also take the help of this link: https://www.mssqltips.com/sqlservertip/2442/move-data-between-sql-server-database-filegroups/ [/url]

If you are not granted the needed permissions, you will not be able to see the Agent. You can grant the individual roles to the users: https://msdn.microsoft.com/en-us/library/ms188283.aspx

This state occurs when password is not correct in the connection string for any SQL server authenticated logins.

To fix this error uncheck the enforce password policy in the properties...

take a look at these links: https://social.technet.microsoft.com/Forums/office/en-US/0f7fd256-d469-4408-982c-0f1a9aa74026/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=winserverClustering

https://blogs.msdn.microsoft.com/sql_pfe_blog/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesnt-occur-or-does-it-a-look-at-the-logs/ [/url]

Check the login's default database

Take a look at this link, hope this will help you: http://www.sql-server-performance.com/2016/monitor-data-growth/[/url]

The most probable cause of this error is SQL CLR encountering memory pressure