Tools used by the SQL Networking Customer Support Team
Перейти к файлу
Malcolm Stewart cbdc9aa045
Merge pull request #78 from microsoft/20241115_SQLCheck_ERRORLOG
SQLCheck: ERRORLOG improvement to handle more than 10 ERRORLOG files
2024-11-15 15:37:40 -05:00
.github/workflows Update SQLNA-Release.yml 2021-06-04 13:56:42 -04:00
.vs Report login errors, read-only intent connections, updated formatting and wording slightly 2020-09-14 17:25:40 -05:00
DBTest DBTest updated -top switch logic error 2024-07-11 13:26:19 -04:00
Documentation/Images Update BIDTrace.txt 2024-05-02 19:40:59 -04:00
SQLBench 20230828_BranchChangeNo64 2023-08-28 13:59:00 -07:00
SQLCheck SQLCheck 2024-11-15 15:36:01 -05:00
SQLTrace SQLTrace Network Improvement 2024-03-25 14:25:19 -04:00
SQL_Network_Analyzer SQLCheck 2024-11-15 15:36:01 -05:00
SQL_Network_Analyzer_UI PCAPNG parser fix 2024-08-21 15:33:30 -04:00
SSPIClient Typo 2023-04-21 17:15:56 -04:00
.gitignore Update .gitignore 2023-08-28 17:08:16 -04:00
CODE_OF_CONDUCT.md Initial CODE_OF_CONDUCT.md commit 2020-07-29 13:33:38 -07:00
LICENSE Updating LICENSE to template content 2020-07-29 13:33:40 -07:00
README.md Update README.md 2022-09-16 13:06:31 -04:00
SECURITY.md Initial SECURITY.md commit 2020-07-29 13:33:43 -07:00
msbuild Removing PII 2020-12-18 13:07:41 -05:00

README.md

Welcome

Welcome to the CSS SQL Networking team's tools repository.

Here, you will find a number of tools that we use when supporting our customers to help find solutions to problems faster and easier.

These tools all run locally and do not use any external services or report back to Microsoft or anyone else. For example, the SQL Network Analyzer tool reads a network trace on your local machine and writes the report to the same folder or to some location you explicitly designate. Some tools may connect to a SQL Server, such as SSPIClient and DBTest, or make some LDAP queries regarding account or machine properties, such as SQLCheck. Results are written to the console window or to a local file of the user's specification. More detail is provided in the individual tool documentation.

Tools

SQL Network Analyzer (SQLNA) - a command-line tool that reads a network trace (or series of chained traces) and produces a report indicating potential problems.

SQL Network Analyzer UI (SQLNAUI) - a GUI interface for SQL Network Analyzer.

SQL Check (SQLCHECK) - a command-line tool that records system information useful for analyzing SQL Server client-server connectivity issues.

SQL Trace (SQLTRACE) - a command-line tool that records network traffic and various driver and Windows events useful for analyzing SQL Server client-server connectivity issues.

SQL Benchmark Tool (SQLBENCH) - a command-line tool that performs a standard set of operations on a file folder/share or database, so you can compare systems and databases.

SQL Driver Security API Trace (SSPICLIENT) - an MFC Windows C++ Tool that can be run on client machines having SSPI or Kerberos errors and will log a detailed trace for analysis.

Database Connection Test (DBTEST) - a command-line tool that allows you to perform ad hoc database connection and command tests, and reliability tests to SQL Server and other OLE DB and ODBC data sources.

Various scripts referenced by workflows.

Documentation

The Wiki contains documentation for the tools on this site and workflows for solving many issues with SQL Server client-server connectivity.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.