pyodbc VS Sentry

Python can script and view this via pyodbc... https://github.com/mkleehammer/pyodbc/wiki

I am not 100% sure you call stored procedure correctly. in the examples they declare @out parameter for the procedures with output.

pyodbc has the odb2 part figured out. This could be useful instead of reinventing the wheel. The rest I can't think of anything that has been done. Sounds like an interesting project.

From its documentation it looks like pyodbc conforms to the DB API, so you can probably use named parameters by passing a dictionary to execute(), as described here.

~ $ pip show pyodbc Name: pyodbc Version: 4.0.34 Summary: DB API Module for ODBC Home-page: https://github.com/mkleehammer/pyodbc Author: Author-email: License: MIT Location: /data/data/com.termux/files/usr/lib/python3.10/site-packages Requires: Required-by:

I am trying to migrate data from our Enterprise Data Warehouse to one of our own reporting databases via ODBC and Python scripts. The python scripts import pyodbc to handle the database connections and execute SQL queries. A system DSN is defined on our ETL server for each database involved in the process.

See the docs.

First, sign up for a free account at https://sentry.io. Create a new project and make note of your DSN (Data Source Name).

Using APM tools like NewRelic, Sentry, Datadog, etc to monitor the performance of your application and while you're on it, they can help you identify N+1 queries.

However, ensuring the reliability and performance of your Next.js app is equally crucial. That’s where Sentry comes into play. Combined with Sentry, an industry-leading error monitoring platform, Next.js empowers developers to proactively identify and resolve issues that may arise in their applications. In this article, we’ll explore how to integrate Sentry into your Next.js project for effective error monitoring and performance optimization.

Sentry: Error monitoring for applications, including APIs. Also offers application performance monitoring (APM).

Indeed, webapps are not immune to distribution problems. Wayward and invasive browser extensions are a clear threat, as are 3rd-party dependencies (and their dependencies) loaded at runtime. Which is why companies like https://sentry.io exist. I think the difference is that webapps are "distributable by default" and it takes real work to break this. Versus having local desktop apps which require work to distribute. A potent example of the power of defaults.

Sentry produces nothing of value? You don't value an open source error tracking and performance monitoring platform? https://github.com/getsentry/sentry

> You invent something, and then immediately turn it into a cheap commodity by releasing it for free.

Exactly. A 71-line python script https://github.com/getsentry/sentry/commit/3c2e87573d3bd16f6... was groundbreaking when it came out and the fact that it springboarded into a startup is commendable.

sentry.io: 5

Sentry - Open Source Alternative For Error Tracking

11. Sentry