Skip to content

SQL Nexus 7.21.03.26
Compare
Choose a tag to compare
@PiJoCoder PiJoCoder released this 27 Mar 00:50
· 395 commits to master since this release
7.21.03.26
52f0dba
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Development Environment:

  1. Visual Studio 2015/2017
  2. Report Builder 2016

Prerequisites to run SQL Nexus

  1. .NET framework 4.6.2. Windows 10 anniversary update has version already.
  2. Download and install SQLSysClrTypes
  3. Download and install ReportViewer control (ReportViewer.msi)
  4. Download and install RML Utilities (RMLSetup_AMD64.msi)
  5. An instance of SQL Server (2012 or above) to connect to and process data
  6. Optional: PowerBI Desktop

Automate Prerequisites Installation

You can use the following PowerShell file (https://github.com/microsoft/SqlNexus/blob/master/Setup-Related/SetupSQLNexusPrereq.ps1) to install the three required and one optional prerequisites for SQL Nexus

How to Use

  1. Download the SQLNexus_v_7_21_03_26.EXE (this is a digitally signed self-extracting zip file by Microsoft)
  2. Double-click on it to allow files to be extracted in a path location of your choice
  3. You will now see a SQLNexus_v_7_21_03_26.zip file which you can extract into a subfolder, e.g. \SQLNexus_v_7_21_03_26
  4. Go to the new subfolder and execute sqlnexus.exe

Fix List:

  • Added support for PowerBI reports and included reports with SQL Nexus

  • Added import support in Textrowset.xml for 6 more tables where were in the PSSDIAG data but not imported
    tbl_dm_os_memory_pools
    tbl_dm_os_memory_objects
    tbl_dm_os_ring_buffers_mem
    tbl_Query_Execution_Memory
    tbl_dm_os_loaded_modules
    sys.dm_os_sys_info
    tbl_dm_os_loaded_modules_non_microsoft

  • Fixing bugs in PerfStats analysis script and adding logging for ExecuteScript()

  • Modified references to Codeplex in RDL files to point to Github

  • Changed startup param for dropDb to 'N' and resolved MODIFY FILE issue …where the LDF size is larger than 50 MB

  • Introduced a Powershell file to install ALL the prerequisites …This would solve the trouble of hunting for prerequisite files manually. This is available on GitHub /Setup-Related folder

  • Changed QuietMode to QuiteNonInteractive variable and Quiet Mode --Help definition

    • Changed the Quiet mode definition to a clarify minimized window

  • Added logic separate for console mode and GUI mode in KeepPriorNonEmpyDb

  • Implemented logic to terminate cmd-line SQLNexus if Db is present and has nexus data

  • Fixed issue with using KeepPriorNonEmptyDB

  • Fixing issues related to running in Console mode (command line) …

  • Added support for /N command line param to allow Drop existing DB and create a new one - was not there before for command line

    • /N              Create a new SQLNexus database before importing (drop existing).

  • Shows a dialog when missing ReadTrace.exe or folder, instead of crashing SQL Nexus

  • Improved logging and messages in SQLNexus log and on screen (message bar at lower left corner)

  • Created Progress bars for ALL activities happening during Import and post-import activities

    • Added support for a progress bar and status update when perfstats analysis runs (after import)
    • Progress bar for post-process work
    • Progress bar for raw file imports
    • Progress bars for enumerating reports and counting runtime snapshots in db

  • Added a Close button at the end of the import

  • Change the size of the Import window

  • Fixed Stop button to function "as expected" - it was not truly stopping the import before

  • Improved Import performance by removing duplicate execution of each table drop and create statement for each object.

  • Enabled the Tasks panel with links to Nexus and RML logs (on the left) to be visible/active at all times. This allows you to view progress in SQL Nexus log during Import for example

  • Fixed a bug where using SQL Authentication was not consistent across the product and in some cases it was still using Windows authentication.

Assets 3
Loading