Senaste inläggen 


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

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