microsoft / microsoft/CSS_SQL_Networking_Tools

SQLTrace suggestion

Open
#59 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
209
Forks
59
PR merge metrics
No merged PRs in 30d

Description

Since SQL Trace collects so many files, it may be beneficial to have the trace file zip everything at the end of the process so the customer can upload just that zip file. Before we had SQLTrace, I wrote out my own script with the following:

POWERSHELL -command "Compress-Archive -Path .\SQLTrace -DestinationPath .%computername%_SQLTrace.zip"

ECHO.
ECHO I have zipped the contents of this directory as %computername%_SQLTrace.zip, stored in the same directory you ran the batch file from.
ECHO Please upload this file to the DTM site provided by your support engineer.
ECHO I have also paused the batch file so you can review the command buffer.
ECHO.
PAUSE

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the SQLTrace process that collects its files and review the provided PowerShell Compress-Archive command as the requested packaging behavior. Done means the trace contents are archived into a customer-uploadable zip at the end of the process, with an accompanying upload message.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, sql
Domain
databases, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.