#python #pyodbc #SQLServer
https://devblogs.microsoft.com/python/mssql-python-vs-pyodbc-benchmarking-sql-server-performance/?wt.mc_id=DP-MVP-4015656
Boom!
In addition to our #MCP servers for #ODBC, #JDBC, #PyODBC, and #SQLAlchemy, we now have one for ADO.NET—bringing .NET runtime support into the mix.
At this point, we’ve covered all the major protocols needed to build data source–agnostic AI Agents via MCP.
Github Repo:
C# based Model Context Procotol (MCP) Server for ADO.NET ODBC provider - GitHub - OpenLinkSoftware/mcp-adonet-server: C# based Model Context Procotol (MCP) Server for ADO.NET ODBC provider
Teradata by itself is bad
PyODBC by itself is bad
Combine the 2 and the stress makes my hemorrhoids sad
Python snippet
uda_exec = Teradata.UdaExec()
conn=uda_exec.connect("SID")
conn.execute('delete from sales_table')
if sales_table is empty, the above statement throws an error "Function sequence error"
Now I have to check if data exists before I call "DELETE".
Who the fuck even designs such shit?
#Teradata #PyODBC #SQL #Tech #Python
To connect to a database in Python, use a database-specific library such as Pyodbc for Microsoft Access and SQL Server, Psycopg2 for PostgreSQL, mysql-connector-python for MySQL, or sqlite3 for SQLite. You will need to execute a database query to retrieve the data after establishing the connection.
#python #Pyodbc #Psycopg2 #PostgreSQL #mysql-connector-python #MySQL #sqlite3 #SQLite #database #db #sql
Spent a day battling #Azure SQL Server transaction deadlocks occurring in sharded and parallel #RobotFramework testing using #Pabot.
Was fun still I expect it's because:
- #pyodbc isn't very efficient deleting rows from multiple tables in one transaction.
- ODBC driver isn't really the latest and greatest so maybe updating it might have some positive effect.