new V16 install database file location?

[adale]

Attempting my first install of V16 on a Windows11 PC, that has not had Lansa or SQL previously installed.
In the Installation Options and Summary, the new db instance name is: SQLS22L16 (Sql server 2022, and Lansa 16 - makes sense).

But for the Database file and log file locations, it has:
C:\Program Files\Microsoft SQL Server\MSSQL15.SQLS19L15\MSSQL\Data (Sql server 2019 and Lansa 15 ????)

Why the naming reference to what looks to be a previous version / install?

Does this really matter?

Will this cause in install issues?

I have spent very little time with MS SQL Server, so do not really know or appreciate the importance or implications of this naming.

Any insight here is greatly appreciated.

[Bikel]

hi Arlyn
I spotted this too when installing V16 on a new PC a few days ago and when I raised it with local support I was told that this was probably not what it should be and I had 2 choices in how to proceed
- leave it as it is and the folder will be created and apart from not looking 'in synch', it won't be a problem
- use the optional parameter button next to the database name during the install to change it to MSSQL16.SQLS22L16, which I guess is what it was originally meant to be, haha. I'd never even noticed that optional parameters button before.

hope that helps.

[adale]

I am still waiting on an response from support, but the Database file and log file locations sure look to be a parm that did not get updated when they made the new SPIN for V16. I proceeded to use the optional parameters to change the location name to follow the pattern, and used: MSSQL16.SQLS22L16 in the path instead of the older path pattern.

Other note: not sure if this will help any others, but here are a couple links for resolutions of other issues I ran into when trying to install VL 16 on this Windows11Pro PC, and changes that had to be made for MS SQL to install properly.

A. Change windows firewall setting for MS SQL:
* I used the program exception option.
https://learn.microsoft.com/en-us/sql/s ... ty-snap-in

B. Check the disk sector size for use with SSD drive:
* I ended up making the registry change instead of the trace flag. Not sure if the trace flag might have been a better option or not.
https://learn.microsoft.com/en-us/troub ... try-editor
-
https://www.mssqltips.com/sqlservertip/ ... ronous-io/

C. Link for clean uninstall of MS SQL if you have to start over. I did a couple times.
https://www.sql-easy.com/learn/how-to-u ... ql-server/