Senaste inläggen 


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

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