| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
About Collectors
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...
Some tuning of the logging parameters may be needed depending on event volumes generated on your SQLServer instance.
Firstly First create or reuse an existing Azure Storage Account.
Then create a blob in the example the blob is called extended-events
...
Go to Settings, Select Sources and click Add Source
Select “Load from File” option
Give the source a Name - e.g. SQL Server SQLServer Azure Production
Add the Host name for the SQL Server instanceSQLServer Azure Instance
Click Next & Finish Setup
...
Step 2: Getting Access to the Source Landing Directory
...
The collector requires a set of parameters to connect to and extract metadata from SQL ServerSQLServer Azure.
FIELD | FIELD TYPE | DESCRIPTION | EXAMPLE |
|---|---|---|---|
server | string | SQLServer Azure server. If using a custom port append with comma | “mydatabase.database.windows.net” |
host | string | The onboarded host value in K, generally this would be the same as the server value, depending on what you onboard it as. | |
username | string | Username to log into the SQLServer Azure account | “myuser” |
password | string | Password to log into the SQLServer Azure account |
|
databases | list<string> | A list of databases to extract from SQLServer Azure | [“dwh”, “adw”] |
driver | string | This is the ODBC driver, generally its ODBC Driver 17 for SQL Server, if you another driver installed please use that instead. | “ODBC Driver 17 for SQL Server” |
meta_only | boolean | Do you want to extract metadata only without enabling extended events? We currently only support true | true |
output_path | string | Absolute path to the output location where files are to be written | “/tmp/output” |
mask | boolean | To enable masking or not | true |
compress | boolean | To gzip the output or not | true |
...