Senaste inläggen 


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

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