Senaste inläggen 


Trace Flag     sql 2008     SQL Server     clean up     performance     improve     feedback     Datawarehouse     Säkerhet     sp1     central management server     CU3     HADR     undocumented procedures     filter     0xC0010014     page splits     SQL Server 2012     HEAP     resource governor     function     Cluster     AcquireConnection     package load     DECIMAL     CTE     bugs     connection     parameters     features     create index     2000     data warehouse     CU1     virtuell     2008     Logins     gratis verktyg     SQL server codename Denali     T-SQL     dbmail     Reports     DTA     SQL2008     sql 2005     SSIS     profile     Business Intelligence     access denied     Microsoft     temp table     sql browser     CTP1     Activity Monitor     Techdays     SSRS     XP_cmdshell     security     transactions     Page life expectancy     login error     0xC0202009     error     2005     history     Extended Event     #am_get_querystats     reorganize index     2011     connect     SQL Denali     rebuild     parallelism     CMS     constraint     platsannons SQL utvecklare     SSRS 2008     SSAS     concatenation     BOL     sp_MSForEachDB

SQL Server errorlog management

Skrivet den 24 februari 2012 i SQL Server best practices, Jan Nieminen, Level 200, sv, en The other day i encountered a problem when trying to open the SQL Server errorlog. SQL Server had been up and running for a long time without a restart so the errorlog had grown very big which made it very time consuming to open. This scenario can be avoided with a litte planning. If you suspect that your SQL Server instance will be running for a long time without interruption it could be a good idea to change the number of errorlogs before it's recycled from default (6) to, for example, 30. But this alone will not be enough. There is a stored procedure to recycle the errorlog, sp_cycle_errorlog which can be used to create a new logfile without restarting SQL Server. This command can be scheduled to run at appropriate intervals and together with the increased number of errorlogs it will make access to your SQL Server errorlog much more painless. These are two very simple things that can make your life a lot easier and they will let you focus on the real problem when it arrives. If you need help with planning your SQL Server environment don't hesitate to contact us.

Skriv en kommentar