Senaste inläggen 


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

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