<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with DataPRO v4.0.1119, 4.2.324
 
Testing Method:
 
 
Per Jerry: 
 
Install DataPRO on a system that does not have SQL Server 2019 LocalDB installed and ensure that it gets installed.
 
 
 
Best way I did this was to copy these versions of DataPRO to Quality Laptop which I knew did not have SQL server 2019
 
Installed DataPRO and was prompted with the following:</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-01-12T16:48:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-12T16:45:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-02T21:39:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-02T16:22:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49989 is 4.0</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-20T00:39:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-12-19T21:26:08Z</TimeStamp>
    <ReleaseNote>Installer now installs MS SQL 2019</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49979 is 4.2</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-12-18T21:54:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Both 2020 and 2023 versions of InstallShield can install the 2019 version of SQL Server LocalDb, and both have been tested successfully.

DTS already has a license for 2020, so the no-brainer choice is to change from 2016 to that version.

Since the installer will now install SQL 2019 if it isn't already installed on a user's system, whether or not to change our base SQL database from 2014 to 2019 is something to consider.  If we stay at 2014, then the first time a 2014 database is in use by SQL 2019, it will automatically undergo an irreversible upgrade.

This seems to be the safest choice for now, but can be changed at any time in the future.
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-16T00:29:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-13T17:45:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>there may be other manuscript tickets too ...</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-13T17:38:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-12T16:56:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Hi Dan,

This is great news. I am more than comfortable explaining we don't support WIN 7.

Chris

-----Original Message-----
From: Dan McFadden &lt;dan.mcfadden@dtsweb.com&gt; 
Sent: Wednesday, December 6, 2023 12:28 PM
To: Chris Balogh &lt;chris.balogh@dtsweb.com&gt;
Cc: Jerry Lawrence &lt;jerry.lawrence@dtsweb.com&gt;
Subject: SQL server end of security support note

We had a customer ask not to long ago about the version of SQL server we 
currently use and our plans to update.

updating this in the installer is fairly trivial, but may potentially 
mean windows 7 or similar OS may not be supported if it's not supported 
by the next SQL version to be installed.


https://endoflife.date/mssqlserver


the End of security support for 2014 is july 09 2024.


Can we bite this off for the 4.2 release?  This question is many to get 
a go ahead from support from chris.</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-12T16:56:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Rhonda Murray</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2021-09-02T21:56:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Eric Fizer</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2019-08-15T22:01:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Eric Fizer</User>
    <Comment>Chris Balogh (DTS) 
 
 Aug 15, 14:55 PDT 
 
 Rainer had an issue with SQL 2016 from my touching of his 2014 db.
 
 Eric,
 
 Can you get me an FB ticket for that one too?</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2019-08-15T22:01:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>