How to dump SQL Server Express schema to github? - sql-server

At the moment I'm using SQL Server Management Studio and stored procedures to execute all my API calls. I'm wondering where could I get started if I wanted to transfer the schema and queries within my stored procedures to github. Thanks!

Related

How do I create Stored Procedure in MSSQL without Management Studio?

I have a customer who is not interested in installing MSSQL Management Studio. And I need to add one Stored procedure in the Database for my application to communicate.
Is it possible to create the stored procedure in MSSQL Server without Management Studio?
FYI, I can export the .sql file for Stored procedure from my system.
Solved
Solutions based on the answers:
SQLCMD (installed with SQL Server)
Azure Data Studio
You can use...
SSDT (SQL Server Data Tools)
SQLCMD
PowerShell
You could see if your client would be willing to install Azure Data Studio (formerly SQL Operations Studio). It's a quicker install than SSMS.

MS Access calls stored procedure to linked server

3 pieces to the puzzle:
MS Access Front end
SQL Server with stored procedures
Oracle server with data
I want to use MS Access to call a stored procedure in SQL Server, which takes data from the Oracle server to SQL Server.
Problem: when I call the stored procedure from the MS Access frontend, which is stored in SQL Server, it times out...
I can run other SQL Server stored procedures (that don't use the Oracle server) from Access, and that works without any problems (no issues with security etc.)
I can run the stored procedure in SQL Server using SSRS and it works fine (so I know the stored procedure as such works).
I use Windows authentication to access SQL Server from Access, however there is a different username and password from SQL Server to Oracle (which may be something to do with it?)
Because the stored procedure works on SQL Server, how can I get the MS Access frontend to simply run the stored procedure on SQL Server?
Hope you can help!

SQL Server database performance using Prometheus

I am new to Prometheus, I want to use the results of a SQL Server stored procedure in Prometheus Grafana with using Web API (not using Docker or agent) to see the performances of my SQL Server database, I have cloned the GitHub project called Prometheous.net in Visual Studio, but my question is how can I use it with my SQL Server database to collect metrics?

Automatic update of the Database Engine (SQL Server) in a web-application context

I'm working on a web application using Spring 3.0 and hibernate 3 with SQL Server 2008.
A specific work flow requires to check some data in the database periodically (each 1st of a month for example) and do some process (update some tables).
My question is, do I need to put a script on the server that will check continually the database? Or can I do this with SQL Server?
See:
How to: Create a Job (SQL Server Management Studio), specifically,
How to: Create a Transact-SQL Job Step (SQL Server Management Studio)
and
How to: Schedule a Job (SQL Server Management Studio)
The easiest and most flexible way will be to have an external script that runs at the desired times and does the updates.

Accessing Oracle database from SQL Server stored procedure.

I was wondering if someone could give me some pointers on how to connect to an Oracle Database from stored procedure in SQL Server.
Firstly on your SQL Server server you will need to install Oracle Client Tools, the reason behind this is any machine that wants access to a Oracle Database will need the necessary Oracle Client Tools installed to access it.
Secondly you will need to configure the file "tnsnames.ora" that is installed with the above configured to point to the required Oracle Server/Database that you want to connect to.
Now you will need to create a Linked Server from your SQL Server management studio for that server to the oracle server.
Then in your stored procedure you have to follow the rule of:
[SERVER_NAME].[DATABASE].[OWNER].[OBJECT] in order of accessing thing on the oracle database, but keep in mind this is SQL Server syntax and there might be some minor twiking needed.
This is a rough outline and I hope it has set you on your way.

Resources