sql-agent | HTTP interface for executing ad-hoc SQL queries | SQL Database library

by chop-dbhi Go Version: Current License: BSD-2-Clause

X-Ray Key Features Code Snippets Community Discussions(6)Vulnerabilities Install Support

kandi X-RAY | sql-agent Summary

sql-agent is a Go library typically used in Database, SQL Database, Oracle applications. sql-agent has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

SQL Agent is an HTTP service for executing ad-hoc queries on remote databases. The motivation for this service is to be part of a data monitoring process or system in which the query results will be evaluated against previous snapshots of the results.

Support

Quality

Security

License

Reuse

Support

sql-agent has a low active ecosystem.

It has 74 star(s) with 21 fork(s). There are 14 watchers for this library.

It had no major release in the last 6 months.

There are 6 open issues and 6 have been closed. On average issues are closed in 41 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of sql-agent is current.

Quality

sql-agent has 0 bugs and 0 code smells.

Security

sql-agent has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

sql-agent code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

sql-agent is licensed under the BSD-2-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

sql-agent releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

It has 617 lines of code, 17 functions and 4 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed sql-agent and discovered the below as its top functions. This is intended to give you an instant insight into sql-agent implemented functionality, and help decide if they suit your requirements.

handleRequest handles HTTP requests .
EncodeJSON encodes an Iterator to w .
EncodeCSV returns a CSV representation of the Iterator .
Execute executes a query .
PersistentConnect creates a connection to a database connection
parseMimetype parses a mimetype from the Accept header .
Connect a database connection to the specified database .
Run the sql agent
EncodeLDJSON encodes the iterator to JSON .
cleanParams removes all key - value pairs

Get all kandi verified functions for this library.

sql-agent Key Features

No Key Features are available at this moment for sql-agent.

sql-agent Examples and Code Snippets

No Code Snippets are available at this moment for sql-agent.

Community Discussions

Trending Discussions on sql-agent

Can't get a runbook test (in portal) to ask for input parameters

Deploying SQL Changes Containing $(ESCAPE_SQUOTE())

Packaging SSIS (.ispac) into NuGet Feed (Azure Artifacts)

Debezium Change Data Capture (CDC) not working on sql-server 2017

SSIS 2012: Metadata out of sync after add/remove script parameter

Monitor biztalk server(biztalkmgmtdb) SQL Server Agent job failed on step 2 - Part2

QUESTION

Can't get a runbook test (in portal) to ask for input parameters

Asked 2019-Sep-21 at 03:09

I'm brand new to automation, and am trying to get a runbook to connect to a sql database and run a stored procedure. The problem is, the code I'm using (adapted from https://azure.microsoft.com/en-us/blog/azure-automation-your-sql-agent-in-the-cloud/) is not asking for the server and credentials parameters when I try to test it. The test window says, "No input parameters."

Here is my (genericized) code:

...

ANSWER

Answered 2019-Sep-14 at 19:11

It says no input parameters because AFAIK you are not providing runbook the required input credentials properly. You would have to do that by using Get-AutomationPSCredential cmdlet. I haven't done end-to-end testing but most probably you may follow this link to accomplish your requirement.

Hope this helps!

Source https://stackoverflow.com/questions/57929443

QUESTION

Deploying SQL Changes Containing $(ESCAPE_SQUOTE())

Asked 2019-Sep-16 at 13:23

I have a Database project in Visual Studio that I am attempting to deploy automatically to a test environment nightly. To accomplish this I am using TFS which leverages a PowerShell script to run "SqlPackage.exe" to deploy any changes that have occurred during the day.

Some of my procs contain logic that is run inside of a script that is part of a agent job step and contains the following code(In dynamic SQL):

...

ANSWER

Answered 2017-Jul-17 at 14:59

One way to get around this is to refactor the "$(ESCAPE_SQUOTE(JOBID))" string into a scalar function, then setup a PowerShell script to directly invoke the "Sqlcmd" command with the "-x" parameter to "Create/Alter" said function before running "SqlPackage.exe".

Looks something like this in PowerShell:

Source https://stackoverflow.com/questions/45090840

QUESTION

Packaging SSIS (.ispac) into NuGet Feed (Azure Artifacts)

Asked 2019-Jul-27 at 13:59

I have to connect Octopus-Deploy to an external feed located on a Azure Devops Artifact Feed. I've successfully connected to the feed, but seeing how I packaged my SSIS project (.ispac) and SSDB project (.dacpac) as .dacpac and .ispac, it won't find them as it expects them to be in .NuGet format.

I haven't been able to try much as I'm pretty stuck.

N/A

I'm constrained to put whatever type of package I make on this feed to connect to from Octopus and deploy from. I have to have either have all my packages be NuGet Packages or find and alternate way that Octopus Deploy can find my packages on the Azure External Feed w/out them being NuGet. I'm only deploying SSDT things: i.e. dacpac, ispac, sql-agents, sql scripts etc.

...

ANSWER

Answered 2019-Jul-27 at 13:59

You can make a NuSpec file which contains the things you need to package into NuGet to use a NuGet external feed in Octopus with. In the case of SSIS, you will want to reference the .ispac file in your nuspec file like so:

{

Source https://stackoverflow.com/questions/56994249

QUESTION

Debezium Change Data Capture (CDC) not working on sql-server 2017

Asked 2019-Jul-06 at 19:59

After following the instructions listed here debezium sqlserver connector and how to activate change data capture

And also making sure that the SQL-Agent is running, debezium is still not working ( streaming data to Kafka).

...

ANSWER

Answered 2019-Jul-06 at 18:09

It turns out that CDC is broken in the initial release of sql-server 2017

CDC Bug Report

Updating to cumulative update 4 or higher solves this.

Took a lot of debugging to figure this out, but I learned A LOT about how sql-server works and how the debezium driver works.

Source https://stackoverflow.com/questions/56916534

QUESTION

SSIS 2012: Metadata out of sync after add/remove script parameter

Asked 2017-Apr-20 at 01:54

We have deployed several changes to SSIS packages successfully, but this particular change gives us an error of

The component metedata is out of sync with the compiled script. Recompile the script using the Script Component Editor.

It runs fine in the debugger on my jump host. What do I do to "recompile the script"? Or is there a deeper problem?

UPDATE 1: This particular script component is more like a destination, and asynchronous. It accepts input rows, and all (or most) of them are consumed within the script (it updates external data via a Web Service), and only the error cases continue through to the output.

I have narrowed down the problem to the absolute minimum change that gives this error: adding another input column (or remove an unused input column). To be precise, after opening the package in Visual Studio 2012 on my jump host, double-click the Perform ETL task to open the Data Flow, then double-click the G9 Web Service Script Component.

I switch to Input Columns - there are 16 ticked/listed - and I untick one that is actually not used in the script. Or I tick (add) another column (which I want to use in the script).

Then I swap back to Script, click on Edit Script, and wait for the VstaProjects window to come up.

I either close this VstaProjects window straight away, or I make an extremely minor change to the script (comment only), then Build > Build ScriptComponent_5aa...acb, then press the floppy (Save) symbol, then exit Vsta.

Then I run in the debugger (press green start arrow) and it runs as expected. I build by right-clicking the project (G9) and selecting Build (this might be redundant after running in debugger).

In Windows (File) Explorer, I navigate to the G9/bin/Development folder, double-click G9.ispac (steps through deploy: Project Development file; my-dev-svr; SSISDB > ACME-SSIS (which gives SSISDB/ACME-SSIS/G9); Deploy!

Problem: When I log into my-dev-svr, drill into Integration Services Catalogs, and run the package, then drill into the Overview Report (for this execution) > View Messages, I see several errors. The most important are

Perform ETL:Error: "G9 Web Service Script Component" failed validation and returned validation status "VS_ISBROKEN".

Perform ETL:Error: The component metedata is out of sync with the compiled script. Recompile the script using the Script Component Editor.

Command Line

I'm not entirely convinced this is related, but here it is: I've copied G9.ispac to my-dev-svr, then logged in there and on the command-line, executed dtexec. Bear in mind that this is the same server where SSIS debugging does not work.

...

ANSWER

Answered 2017-Apr-17 at 15:02

Since you have already work out the script and make sure the script works fine. Then it has a lot chance it has issues in your destination. It seems that you are using the Script component as data source, try to check the Metadata from the output of the source (right click the precedence constraint), check them whether they are matched with the input of destination, more important, if you have made any changes to the source columns, you'd better to delete and create a new destination, sometimes it might cache the columns that no longer exists.

Source https://stackoverflow.com/questions/43453190

QUESTION

Monitor biztalk server(biztalkmgmtdb) SQL Server Agent job failed on step 2 - Part2

Asked 2017-Apr-18 at 09:07

Please go through: Monitor biztalk server(biztalkmgmtdb) sql agent job failed on step 2 - Part1 for details how this question was born.

How can we prevent messages with refcount less than 0, without reference counts from BizTalkMsgBoxDb and Orphaned DTA service instances from BizTalkDTADb?

Usually I need to run BHM quite frequently on my environment to clean up inconsistency so is there good practice to do regularly when ever SQL Server Agent job failed.

...

ANSWER

Answered 2017-Apr-17 at 14:12

First, I never run Monitor BizTalk Server. Preferring to run BHM regularly.

If you are experiencing a build up of orphaned messages, then the jobs aren't what you should be looking at. It's a app that allowing this to happen.

Source https://stackoverflow.com/questions/43414325

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install sql-agent

At the moment, it is recommended to run the service using Docker because there are no pre-built binaries yet.
In order to install the go-oci8 driver, you must install Oracle's client libraries. Download the instantclient-basic and instantclient-sdk package from Oracle's website and uncompress to the same directory. Make sure that you selected the platform and architecture. The installations instructions are listed at the bottom of the page with the download links.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: