Senaste inläggen 


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

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