EFT SQL Database Manual

Transcription

1 EFT SQL Database Manual Contents Overview... 2 Installation... 3 Requirements... 3 Install EFT Module for TestStand... 3 SQL Server Installation... 3 Configure Database... 4 Configure TestStand Result Processing... 8 Add EFT SQL Database... 8 Connect TestStand to EFT Database... 8 Configure TestStand Result Processing Options Show DB Uploader when Running Log Passed/Failed/Skipped/Error only Save Additional Results LogToDB Extended Step Names Logging Specialty Data Page 1 of 11

2 Overview The EFT SQL Database is a simple SQL Database reporting plugin for TestStand. As shown by the Database Diagram below, the plugin allows test Units (consisting of unique Part Number, Serial Number, Revision, and WorkOrder/Lot) to be associated with multiple Test Runs (full top-to-bottom execution of a sequence). Each test run stores some header information, and associated Step Results (measurement results of each step in the test) that are defined by the TestStep (name and limits for the step). Additionally, exit codes may be associated with step results and test runs to more precisely define the exit condition of a test. Figure 1: Database Diagram When enabled (See Configure TestStand Result Processing) the plugin automatically logs the result of each test step executed in Test Stand. Options are available to limit the logging to just pass/fail data and selected steps (see Configure TestStand Result Processing Options). When logging specialty parameters (TestType, Limit File, Exit codes, etc), the EFT module sample sequences provide a utility sequence that assists in configuring these parameters, as outlined in Page 2 of 11

3 Installation Requirements NI LabVIEW 2016 SP1 NI TestStand 2016 SP1 Bloomy EFT Module for TestStand 2016 MS SQL Server (Express) 2008 or later with Management Studio (WITH TOOLS) Install EFT Module for TestStand (Skip if already installed) 1. Run Setup.exe 2. Follow all on-screen instructions to install the EFT Module SQL Server Installation 1. Download MS SQL Express with Tools: 2. Open the installer 3. Select New SQL Server stand-alone installation or add features to an existing installation 4. When prompted for Installation Type, select Perform a new installation of SQL Server Page 3 of 11

4 5. When prompted for Instance Configuration, select Default Instance 6. When prompted for Database Engine Configuration, in the Server Configuration tab, select Mixed Mode (SQL Server authentication and Windows authentication). Specify a password for the system administrator account and then press ok. The password has to contain numbers, letter and at least one non-alphanumeric symbol (E.g. #Bloomy1234). 7. Continue clicking Next and following the instructions on-screen to complete the installation. Configure Database 1. Open SQL Server Management Studio You will be asked for your server name. This is just your computer name, followed by \SQLEXPRESS. Then click connect. Page 4 of 11

5 2. Right click on Database and select New Database Recommendations on DB creation a. Limit the growth of the Log file to a reasonable size. b. By default, SQL Server selects the path where the DB files will be stored. This is deep inside SQL Server directories (under Program Files). Look a location that is easier to find. 3. The DB will be created on it will be seen in the object explorer Page 5 of 11

6 4. Open UTS Build Script.sql file found in C:\Users\Public\Documents\National Instruments\TestStand <versionnum>\components\models\modelplugins\uts SQL Report Support Files\Queries a. NOTE: If your database has a name other than UTS, you must update the database name accordingly: i. Change USE [EFT] on line 1 to USE [X] where X is the name of your database ii. Change ALTER DATABASE [EFT] SET READ_WRITE on line 358 to the name of your database iii. Change USE [EFT] on line 362 to the name of your database Page 6 of 11

7 5. Click Execute button and wait for completion 6. Verify that tables and store procedures were created. Page 7 of 11

8 Configure TestStand Result Processing Add EFT SQL Database 1. From TestStand sequence editor or Bloomy Manufacturing OI, choose Configure > Result Processing. This will display the TestStand Result Processing Window 2. From the result processing window, choose the Insert New button. (If the Insert New button is not visible, check the Show more options checkmark found in the lower left corner of the window.) a. Select EFT SQL Database. A line for the EFT SQL Database will be added. 3. Click the Enabled Checkbox associated with the EFT SQL Database Connect TestStand to EFT Database 1. Click on the Options button associated with the EFT SQL Database to launch the configuration dialog. Page 8 of 11

9 2. From the configuration dialog, open the UDL file by clicking the Configure UDL File button. 3. Point the UDL file to the desired database, and configure as shown below a. Note: User Name = EFT; Password = bloomy (same as set up in logins above) b. Or use Windows NT Integrated Security Page 9 of 11

10 Configure TestStand Result Processing Options There are several configuration options available in the configuration dialog for the EFT SQL Database: Show DB Uploader when Running Show the upload status dialog when the SQL reporting is actively executing. Log Passed/Failed/Skipped/Error only Do not log steps whose status result to Done. This greatly reduces the quantity of data entering the database to only those steps which have a pass/fail result or that error out/skip. Page 10 of 11

11 Save Additional Results LogToDB Allows test developers to selectively define which steps are logged to the database. When checked, steps must have an additional result named LogToDB that results to TRUE in order to be added to the database: Extended Step Names When set to true, this option will store the subsequence name with the step name using dot notation (Subseq1.subseq2.stepname). This can be useful if generic subsequences are used across multiple channels. However, step names must not exceed 100 characters. Logging Specialty Data Specialty data may be logged to the database as outlined below. The EFT Module for TestStand ships with a sample sequence located at <MyDocuments>\UUT Test Files\Tests\Sample Sequence that contains a SQL DB Utilities sequence which assists in storing the following custom parameters: Test Run Parameters o Work Order/Lot (String) o Test Type (String) o Property (limit) file path (String) o Notes (String) o Part Revision (String) Test Step Parameters o Exit Codes (String) Page 11 of 11