Skip to content
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.

MSSQL Media specified in MSSQL Media Bucket is not getting installed because of hardcoded scripts/prepare-fci.ps1#L34 #24

Open
ar33bm opened this issue May 6, 2022 · 2 comments

Comments

@ar33bm
Copy link

ar33bm commented May 6, 2022

Thanks team for the great template.

We have noticed that when we want to specify MS SQL Standard version, by passing as parameters for the right .iso are not working because in the scripts/prepare-fci.ps1#L34 the value for MSSQL .iso is hardcoded. And it is always installing the MSSQL Express version.

@davmayd
Copy link
Contributor

davmayd commented May 11, 2022

The script in question does not use the hard coded value for SQL ISO. The file name specified is for the ‘target file name’ when copied from S3. When passing the parameter the user need to define the SQL ISO file in S3 which gets copied to local system as ‘en_sql_server_2019_developer_x64_dvd_baea4195.iso'. Essentially, it is just a target file name as has nothing to do what edition of SQL.

@ar33bm
Copy link
Author

ar33bm commented May 12, 2022

When we are trying to use our MSSSQL Standard .ISO to be used as MSSQL Installation media as we already have MSSQL license which we want to use, we noticed that the QuickStart is not using the media specified during the stack launch. And in any case it is installing the MSSQL developer for FCI instances. If the script mentioned in the subject is not the cause for it, then please try to replicate the issue by using another MSSQL media (like standard or express or enterprise).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants