Senaste inläggen 


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

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