error 18456 severity 14 state 38

The transaction log for database 'xx' is full, Error: 9002, Severity: 17, State: severity Check database logs with the following error message: Error: 9002, Severity: 17,

transactions:currentdate2015-04-08 14:47:42.430You can see that a long transaction is running and has been running for nearly 90 minutes.View transaction Related information:selectfromwhere is_user_transaction=1session_id transaction_id is_user_transaction is_local1566 3452140915 1 1View transaction specific content according to session_id:selectfromwhere session_id=1566textCREATEPROCEDURE dbo.proc_MSS_Crawl .......

Yesterday morning, colleagues reflect a system in the process of executing stored procedures error, error information is as follows:05:00000:00009:2014/06/09 15:45:30.34 Server error:8242, Severity:16, state:105:00000:00009:2014/06/09 15:45:30.34 Server The table ' user_file

Check the database log, with the following error message: error:9002, Severity:17, State:4. The transaction log for database ' sharedservices1_search_db ' are full. To find out why spaces in the log cannot be reused, and the Log_reuse_wait_desc column in sys.databases To view the usage of the current log: The log is n

performance. This can lead to reduced transactions and a reduced bulk commit rate. The following error message may appear in the SQL Server error log: Error: 17883, severity: 1, State: 0Dispatcher 0 appears to have been suspended. SPID 7,ecid 0,ums Context 0x045530b8. Solut

When a new account uses table Tigger to call database mail to send an email, the following error occurs: MSG 229, Level 14, state 5, procedure sp_send_dbmail, line 1, execute Permission denied on Object 'SP _ send_dbmail ', database 'msdb', schema 'dbo '. This is because the current SQL Server login account (LOGIN) does not have the permission to send database