A
AllAboutMike
The Best PRactice Analyzer says I should remove 8.3 names on the Server2012R2 vm running SQL2014.
No problems! I follow the simple instructions to do that.
I turned off 8.3 creation easily, but when I go to strip the previously generated short file names, it tells me there are 1285 registry keys that reference short names.
A quick look at the log file shows that at least most of these are modern software (eg Office 2016) which shouldn't need 8.3 file names.
My question is: Is it safe for me to replace those registry entries with the equivalent full path?
For example can I make:
C:\PROGRA~2\COMMON~1\MICROS~1\OFFICE16\ACEODBC.DLL
read
C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\ACEODBC.DLL
instead? They point to the same location, so I'm reasonably confident it's a sensible move. I would just like to be sure I'm not going to break anything.
Mike
Continue reading...
No problems! I follow the simple instructions to do that.
I turned off 8.3 creation easily, but when I go to strip the previously generated short file names, it tells me there are 1285 registry keys that reference short names.
A quick look at the log file shows that at least most of these are modern software (eg Office 2016) which shouldn't need 8.3 file names.
My question is: Is it safe for me to replace those registry entries with the equivalent full path?
For example can I make:
C:\PROGRA~2\COMMON~1\MICROS~1\OFFICE16\ACEODBC.DLL
read
C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\ACEODBC.DLL
instead? They point to the same location, so I'm reasonably confident it's a sensible move. I would just like to be sure I'm not going to break anything.
Mike
Continue reading...