Import SQL server Management studio backup from an .ipynb file

Question

I have a doubt regarding an ipynb file, it turns out that they send me a database to replicate the structure, they use SQL server Management studio, but I don't know how to import it. I thought it was a simple python script, which could create a SQL database, then Install anaconda, use %%sql statements to recreate it,

Until I realized that they could be imported in SSMS, but there is something that I am not doing well to import it correctly, I understand that it is a problem of correctly parsing the file,

I appreciate any help, thanks!

Install extensions in visual code, anaconda and the necessary libraries for handling SQL in Python, but it all boils down to correctly importing the file created in SSMS.

Answer 1

The ipynb is a notebook that will contain scripts to be executed against a database or create the database and objects as well.

What you are using in SSMS is a tool to import data into tables - these are not the same thing.

As mentioned by @Squirrel, SSMS does not support notebooks, BUT Azure Data Studio does support notebooks. I think that the notebook was created using Azure Data Studio (which will be installed along with SSM on your computer provided you have a recent version of SSMS.

Note that Azure Data Studio is only the name of the tool - it is not restricted to connecting to databases in Azure or running in Azure so you can use it for local or on-premises databases as well.

When you open Azure Data Studio, click on the button for Noptebooks and then the file icon to browse and open your notebook as shown

You will still likely have to set up your connection but that is a similar experience to SSMS.

Answer 2

I would suggest you to follow the below steps:

1. Open the notebook file in Jupyter notebook and copy all the cell contents as given below: How to copy multiple input cells in Jupyter Notebook
2. Copy the content to a single.SQL file.
3. In the Management Studio, open a new query window and open the file, created in step no. 2 and you can run the sql statements.

Note: Please review the SQL file once to see if everything is falling in place. You might need to add GO statements between batches. Also, it is recommended to put semicolon at the end of statements, to make them running without issues.