January 19, 2017 at 6:40 am
Forgive me but this is my first sql server 2016 enterprise install. After the install there are a bunch of files that I’m not accustomed to seeing. Does anyone know what these are for? Are these specific to sql server enterprise or did they exist in my other standard installs but I never noticed them?
Location:
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG.1
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ FDLAUNCHERRORLOG
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ HkEngineEventFile_0_131292202968860000.xel
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ ManagedBackupEvents
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ system_health_0_131292203180260000.xel
January 19, 2017 at 6:48 am
Snargables - Thursday, January 19, 2017 6:40 AMForgive me but this is my first sql server 2016 enterprise install. After the install there are a bunch of files that I’m not accustomed to seeing. Does anyone know what these are for? Are these specific to sql server enterprise or did they exist in my other standard installs but I never noticed them?Location:
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG.1
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ FDLAUNCHERRORLOG
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ HkEngineEventFile_0_131292202968860000.xel
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ ManagedBackupEvents
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ system_health_0_131292203180260000.xel
Errorlog.1 is the previous error log, when the service restarts errorlog is renamed errorlog.1 and a new errorlog created.
All editions of SQL will have that, and all versions back to 6 or older.
The two xel files are extended events. the system health on has been in all versions and editions of SQL since 2012. The hekaton one is probably enterprise only, and since 2014.
ManagedBackups relates to the Managed Backups feature, all editions, since 2014 iirc. I cannot remember when that was introduced.
FDLAUNCHERRORLOG is related to the full text engine. All editions of SQL, and I think since 2012, not sure when they changed that thing last.
Edit: looks like the FDLAUNCHERRORLOG file is new in 2016.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 19, 2017 at 7:00 am
GilaMonster - Thursday, January 19, 2017 6:48 AMSnargables - Thursday, January 19, 2017 6:40 AMForgive me but this is my first sql server 2016 enterprise install. After the install there are a bunch of files that I’m not accustomed to seeing. Does anyone know what these are for? Are these specific to sql server enterprise or did they exist in my other standard installs but I never noticed them?Location:
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG.1
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ FDLAUNCHERRORLOG
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ HkEngineEventFile_0_131292202968860000.xel
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ ManagedBackupEvents
D:\Data\MSSQL13.MSSQLSERVER\MSSQL\Log\ system_health_0_131292203180260000.xelErrorlog.1 is the previous error log, when the service restarts errorlog is renamed errorlog.1 and a new errorlog created.
All editions of SQL will have that, and all versions back to 6 or older.The two xel files are extended events. the system health on has been in all versions and editions of SQL since 2012. The hekaton one is probably enterprise only, and since 2014.
ManagedBackups relates to the Managed Backups feature, all editions, since 2014 iirc. I cannot remember when that was introduced.FDLAUNCHERRORLOG is related to the full text engine. All editions of SQL, and I think since 2012, not sure when they changed that thing last.
Edit: looks like the FDLAUNCHERRORLOG file is new in 2016.
thanks you Gail.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply