Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SqlSetup: Use SQL Server 2017 for integration tests #858

Closed
johlju opened this issue Oct 8, 2017 · 4 comments · Fixed by #1103
Closed

SqlSetup: Use SQL Server 2017 for integration tests #858

johlju opened this issue Oct 8, 2017 · 4 comments · Fixed by #1103
Assignees
@johlju
Labels
enhancement The issue is an enhancement request.

Comments

@johlju
Copy link
Member

johlju commented Oct 8, 2017

Details of the scenario you tried and the problem that is occurring:
Today SQL Server 2016 is used to run integration tests. We should look at using SQL Server 2017 instead. Or, we could use SQL Server 2017 together with SQL Server 2016 to run integration tests for more that one major version.

I can't find the CDN link to download the .iso for Trial or Developer edition. Neither in the download pages https://www.microsoft.com/en-us/sql-server/sql-server-downloads or on the web.

There is an .exe which can download the Developer edition or Trial edition. They are named SQLServer2017-SSEI-Dev.exe and SQLServer2017-SSEI-Eval.exe respectively.

PS > SQLServer2017-SSEI-Dev.exe /?
Optional settings for basic install
==================================

C:\Temp\SQLServer2017-SSEI-Dev.exe [/ConfigurationFile=C:\Configuration.ini] [/IAcceptSqlServerLicenseTerms] [/MediaPath=C:\SqlServer2016Setup] [/ENU]

ConfigurationFile              Specifies the ConfigurationFile to use.
IAcceptSqlServerLicenseTerms   Required to acknowledge acceptance of the license terms.
MediaPath                      Location where SQL Server setup media will be downloaded and extracted to.
ENU                            Use this parameter to install the English version of SQL Server on a localized operating system.

Unfortunately there is not switches to download this thru the command line.
Running this will just open the GUI and one must choose "Download Media" and then choose ISO and start the download.

.\SQLServer2017-SSEI-Eval.exe /MediaPath=C:\Temp\SQL2017RTMDEV /ENU /IAcceptSqlServerLicenseTerms

Looking at the logs there is nothing that I can see could help.

(01) 2016-11-27 14:47:47 SSEI v1.1611.3518.1
(01) 2016-11-27 14:47:47 CorrelationId: 1c41be26-56ed-49db-b9e7-b209e97e50fa
(01) 2016-11-27 14:47:47 currentUICulture.Name='en-US'.LCID='1033'.Parent.Name='en'
(01) 2016-11-27 14:47:47 supported culture detected ='en-US'.
(01) 2016-11-27 14:47:47 osSupported: True, osVersion: 6.2.9200.0, osPlatform: amd64
(01) 2016-11-27 14:47:48 .NET Framework Version: 4.5
(03) 2016-11-27 14:47:48 StartupBootstrapActivity:SSEIActivityStart:Message: Starting Activity StartupBootstrapActivity
(03) 2016-11-27 14:47:48 StartupBootstrapActivity:SSEIProgressReport:ProgressPercent: 1
(03) 2016-11-27 14:47:48 Downloading manifest from https://download.microsoft.com/download/B/F/2/BF2EDBB8-004D-47F3-AA2B-FEA897591599/Manifest_Bootstrap_All.xml
(03) 2016-11-27 14:47:48 StartupBootstrapActivity:SSEIProgressReport:ProgressPercent: 100
(03) 2016-11-27 14:47:48 StartupBootstrapActivity:SSEIProgressReport:ProgressPercent: 100
(03) 2016-11-27 14:47:48 StartupBootstrapActivity:SSEIActivityMessage:Message: Installation initialization successful
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Rules_All_en-US.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Full_Express_en-US.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_zh-CN.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_zh-TW.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_en-US.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_fr-FR.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_de-DE.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_it-IT.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_ja-JP.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_ko-KR.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_pt-BR.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_ru-RU.xml
(03) 2016-11-27 14:47:48 Found manifest resource: Manifest_Media_Express_es-ES.xml
(03) 2016-11-27 14:47:48 BootstrapActivity:SSEIActivityStart:Message: Starting Activity BootstrapActivity
(03) 2016-11-27 14:47:48 BootstrapActivity:SSEIProgressReport:ProgressPercent: 1
(03) 2016-11-27 14:47:48 BootstrapActivity:SSEIProgressReport:ProgressPercent: 100
(03) 2016-11-27 14:47:48 BootstrapActivity:SSEIProgressReport:ProgressPercent: 100
(03) 2016-11-27 14:47:48 BootstrapActivity:SSEIActivityMessage:Message: Installation initialization successful
(03) 2016-11-27 14:47:48 SetupLocationActivity:SSEIActivityStart:Message: Starting Activity SetupLocationActivity
(03) 2016-11-27 14:47:48 SetupLocationActivity:SSEIProgressReport:ProgressPercent: 1
(03) 2016-11-27 14:47:48 SetupLocationActivity:SSEIActivityMessage:Message: Locating drive that meets space requirements (412)
(03) 2016-11-27 14:47:48 SetupLocationActivity:SSEIProgressReport:ProgressPercent: 100
(03) 2016-11-27 14:47:48 SetupLocationActivity:SSEIActivityMessage:Message: Drive found: C:\ AvailableFreeSpace: 17945120768
(03) 2016-11-27 14:47:48 SetupLocationActivity:SSEIProgressReport:ProgressPercent: 100

There are these links to download the .box and .exe. I haven't found a link to the .iso yet. Or, these get coverted to an .iso.
https://download.microsoft.com/download/E/F/2/EF23C21D-7860-4F05-88CE-39AA114B014B\SQLServer2017-DEV-x64-ENU.box

https://download.microsoft.com/download/E/F/2/EF23C21D-7860-4F05-88CE-39AA114B014B\SQLServer2017-DEV-x64-ENU.exe

The DSC configuration that is using the resource (as detailed as possible):
n/a

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a

What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
n/a

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
n/a
@johlju
Copy link
Member Author

johlju commented Oct 8, 2017

Anyone knows the CDN link to the .iso for SQL Server 2017 Trial or Developer edition?

@johlju johlju added enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community. labels Oct 8, 2017
@johlju
Copy link
Member Author

johlju commented Dec 9, 2017 •
edited
Loading

Finally found a link to the ISO. Thanks to the AWS project here https://github.com/aws-quickstart/quickstart-microsoft-sql.

SQL Server 2017 Trial ISO:
https://download.microsoft.com/download/E/F/2/EF23C21D-7860-4F05-88CE-39AA114B014B/SQLServer2017-x64-ENU.iso

@johlju johlju changed the title xSQLServerSetup: Use SQL Server 2017 for integration tests SqlSetup: Use SQL Server 2017 for integration tests Dec 22, 2017
johlju added a commit to johlju/SqlServerDsc that referenced this issue Apr 6, 2018
@johlju
Changes to SqlSetup
dbce342 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
@johlju johlju mentioned this issue Apr 6, 2018
Merged
9 tasks
@johlju
Copy link
Member Author

johlju commented Apr 6, 2018

It has been slower and slower downloading the SQL Server 2016 media in the integration test för SqlSetup. Hoping that SQL Server 2017 location has more speed. :)

johlju added a commit to johlju/SqlServerDsc that referenced this issue Apr 8, 2018
@johlju
Changes to SqlSetup
d92eb83 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
johlju added a commit to johlju/SqlServerDsc that referenced this issue Apr 21, 2018
@johlju
Changes to SqlSetup
3201a27 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
johlju added a commit to johlju/SqlServerDsc that referenced this issue Apr 22, 2018
@johlju
Changes to SqlSetup
5d1946d 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
johlju added a commit to johlju/SqlServerDsc that referenced this issue Apr 23, 2018
@johlju
Changes to SqlSetup
d9a0c20 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
@johlju johlju self-assigned this Jun 6, 2018
johlju added a commit to johlju/SqlServerDsc that referenced this issue Sep 21, 2018
@johlju
Changes to SqlSetup
761800b 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
johlju added a commit to johlju/SqlServerDsc that referenced this issue Sep 21, 2018
@johlju
Changes to SqlSetup
853ecf9 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
johlju added a commit to johlju/SqlServerDsc that referenced this issue Jan 24, 2019
@johlju
Changes to SqlSetup
8e77207 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
johlju added a commit to johlju/SqlServerDsc that referenced this issue Feb 17, 2019
@johlju
Changes to SqlSetup
25d5501 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
johlju added a commit to johlju/SqlServerDsc that referenced this issue Feb 22, 2019
@johlju
Changes to SqlSetup
c619e2a 
- Integration test is using SQL Server 2017 (issue dsccommunity#858).
johlju added a commit to johlju/SqlServerDsc that referenced this issue Feb 24, 2019
@johlju
Split integration tests into two jobs (#13)
7a28aeb 
  - Split integration tests into two jobs, one for running integration tests
    for SQL Server 2016 and another for running integration test for
    SQL Server 2017 ([issue dsccommunity#858](dsccommunity#858)).
  - A new optional parameter `FeatureFlag` parameter was added to control
    breaking changes. Functionality added under a feature flag can be
    toggled on or off, and could be changed later to be the default.
    This way we can also make more of the new functionalities the default
    in the same breaking change release ([issue dsccommunity#1105](dsccommunity#1105)).
  - Added a new way of detecting if the shared feature CONN (Client Tools
    Connectivity, and SQL Client Connectivity SDK), BC (Client Tools
    Backwards Compatibility), and SDK (Client Tools SDK) is installed or
    not. The new functionality is used when the parameter `FeatureFlag`
    is set to `'DetectionSharedFeatures'` ([issue dsccommunity#1105](dsccommunity#1105)).
  - Added a new helper function `Get-InstalledSharedFeatures` to move out
    some of the code from the `Get-TargetResource` to make unit testing
    easier and faster.
johlju added a commit that referenced this issue Feb 25, 2019
@johlju
SqlSetup: Integration test is using SQL Server 2017 (#1103)
c139e99 
- Changes to SqlSetup
  - Split integration tests into two jobs, one for running integration tests
    for SQL Server 2016 and another for running integration test for
    SQL Server 2017 (issue #858).
  - Localized messages for Master Data Services no longer start and end with
    single quote.
  - When installing features a verbose message is written if a feature is found
    to already be installed. It no longer quietly removes the feature from the
    `/FEATURES` argument.
  - Cleaned up a bit in the tests, removed excessive piping.
  - Fixed minor typo in examples.
  - A new optional parameter `FeatureFlag` parameter was added to control
    breaking changes. Functionality added under a feature flag can be
    toggled on or off, and could be changed later to be the default.
    This way we can also make more of the new functionalities the default
    in the same breaking change release (issue #1105).
  - Added a new way of detecting if the shared feature CONN (Client Tools
    Connectivity, and SQL Client Connectivity SDK), BC (Client Tools
    Backwards Compatibility), and SDK (Client Tools SDK) is installed or
    not. The new functionality is used when the parameter `FeatureFlag`
    is set to `'DetectionSharedFeatures'` (issue #1105).
  - Added a new helper function `Get-InstalledSharedFeatures` to move out
    some of the code from the `Get-TargetResource` to make unit testing
    easier and faster.
@codykonior
Copy link
Contributor

Thanks for publishing this, was looking for ages for this ISO also!

@johlju johlju removed the help wanted The issue is up for grabs for anyone in the community. label Apr 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@johlju johlju

Labels
enhancement The issue is an enhancement request.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

SqlSetup: Integration test is using SQL Server 2017 johlju/SqlServerDsc
2 participants
@johlju @codykonior