Senaste inläggen 


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

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