Senaste inläggen 


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

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