<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-24T20:47:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified w/ DataPRO version 4.0.846, 4.1.197
 
Attached mdf/ldf files to burrito-supreme database. Ran SQL command: UPDATE [dbo].[Users] SET [Password]='Onl79FZmtkwYRi5DfMV46DDfS0HMOpURgIxeUvhswuY=' WHERE UserName='Admin';
 
Set dbtype to 0, UseNTLMAuthentication = true, and LocalDbHost = burrito-supreme  in DataPRO.exe.config
 
Logged in as Admin and saw little to no delay.</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-02-07T22:28:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-02-07T21:03:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2022-11-29T21:42:53Z</TimeStamp>
    <ReleaseNote>Addresses a performance issue in large test setup databases</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T21:42:26Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-22T21:46:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-22T21:46:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1@47880</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-11-22T21:45:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>testing cases involve trying to login pre-patch with the db and post patch with the db.  It takes considerable time pre-patch. [loooong time]</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-22T21:42:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-22T21:41:19Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-22T21:39:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>to use a remote database change dbtype to 0 in DataPRO.exe.config
 
to change the db host change the property for localdbhost
 
attached 4.0 MS SQL 2014 mdf/ldf</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-22T00:23:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-11-22T00:06:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>attached is the database, it can be restored, but is already up on burrito-supreme for right now.
 
If you restore from the backup the admin password has been changed.  It can be changed back using the sql statement:
 
UPDATE [dbo].[Users] SET [Password]='Onl79FZmtkwYRi5DfMV46DDfS0HMOpURgIxeUvhswuY=' WHERE UserName='Admin';
 
 
 
more details of the issue can be found here:
 
https://dtsweb.zendesk.com/agent/tickets/11141
 
DP used to have cached "IsComplete" properties that bypassed calculated whether a test setup is complete or not, which is a very expensive operation (has to load all sensors, hardware, etc).  The database has 2000+ setups with a lot of sensors and calibrations.
 
The cached value can't really be used anymore as there are user specific settings which can determine which test setups are valid or not (example Allow TSR AIR recording modes).  Given on a central database several users could be logged in simultaneously there's no way to cache iscomplete across logged in users and it needs to be re-evaluated with each login.
 
The patch does not do away with IsComplete (which we probably need to remove a connection from the database and make sure it's always calculated or cached for the current user).  We could I suppose have a more complex caching system which is user based with a table in the database based on the user, but that's out of the scope for any work we want to do right now.
 
What this patch does is remove the calculation of IsComplete that happens on the login that's done in UpdateTestSetupLists, and also removes the IsComplete column from the test setups list xaml, removing an additional calculation of iscomplete for all test setups.
 
Finally there's a calculation of IsComplete that happens when the selected test setup changes, this also took a chunk of time.  In turn I've removed the Make Current button and Edit Test Setup save or run can be used instead.
 
There's still Change current test setup in the hamburger menu, but I don't recommend using it as it will also incur the penalty of checking IsComplete on all tests and that takes a long time with this db.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-11-22T00:06:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>