Recently, I was working on one of the databases and I tried to insert a table through SQL Server Management Studio (SSMS) and I came across the following error.
Error:
The backend version is not supported to design database diagrams or tables.
Reproduce Error:
Let me reproduce this error step by step.
Step 1:
Let’s create a new database namely ‘TestDB’ as shown below.
CREATE DATABASE TestDB;
GO
Step 2:
Now, lets expand the database TestDB, then right click on the Tables option and then select New and then select Table… as shown below.
Step 3:
This will display the following error.
Solution:
This error occurs when you have the older version (18) of SSMS installed on your device. To check the version installed on your device, navigate to the Help menu and click on About menu in the menu bar as shown below.
A new window will pop up with all the version details of the SSMS.
In order to solve this error, you need to install a new version (19 or higher) of SQL Server Management Studio (SSMS). You can download it from here
Conclusion:
Make sure you have updated version of SSMS all the time to avoid such errors.
Comparing files is one of the frequent activities, when we want to see the difference between two files. SQL developers face this problem on a day to day basis when they have two versions of the same file and they want to know where they made changes.
Fortunately, SQL Server Management Studio (SSMS) has this toolbar, which you can use to compare two files very easily.
In order to explain it, let me create two scripts as shown below.
Sample:
The below scripts will be saved as Version1.sql & Version2.sql.
Version1:
USE Northwind
GO
CREATE OR ALTER VIEW [dbo].[OrdersQry]
AS
SELECT Orders.OrderID
, Orders.ShipName AS ShipName
FROM Customers
INNER JOIN Orders
ON Customers.CustomerID = Orders.CustomerID;
GO
Version2:
USE Northwind
GO
CREATE OR ALTER VIEW [dbo].[OrdersQry]
AS
SELECT COUNT(Orders.OrderID) AS TotalOrders
, Orders.ShipName AS ShipName
, Orders.ShipAddress AS ShipAddress
FROM Customers
INNER JOIN Orders
ON Customers.CustomerID = Orders.CustomerID
GROUP BY Orders.ShipName
, Orders.ShipAddress;
GO
Now, let’s compare above mentioned both scripts (Version1.sql, Version2.sql) in SQL Server Management Studio (SSMS) as shown in below steps.
Step 1:
Let’s activate Compare Files toolbar by clicking on View menu then click on Toolbars, and in Toolbars, click on Compare Files option as shown below.
The Compare Files toolbar will appear as shown below.
Step 2:
In the toolbar, there is menu button on extreme left hand side which shows the mode of compare. We have 4 types of mode as described below.
Side-by-side mode: It compares both files side by side. This is selected by default as shown below.
Inline mode: It compares combined scripts.
Left file only: It compares the first script.
Right file only: It compares the second file only.
Step 3:
Open File Version1 and Version2 in SQL Server Management Studio (SSMS) as shown below.
Step 4:
Open Command Widow by clicking on View menu then click on Other Windows then select Command Widow Or use shortcut(Ctrl+Alt+A).
Step 5:
In the Command Window, type Command Tools.DiffFiles and give the file name (Version1.sql, Version2.sql) which needs to be compared and press Enter as shown below.
Tools.DiffFiles Version1.sql Version2.sql
Step 6:
Both files will be compared in side by side mode since it is selected by default and the output will be as shown below.
Additional scripts in the second file (Version2.sql) are represented in GREEN color.
Modified or deleted scripts from first file (Version1.sql) are represented in RED color.
Scripts which are NOT changed are represented in NO Background color.
Please note that in case of any changes which are made to these files need to be saved again, we need to run the DiffFiles command again.
Conclusion:
Compare Files toolbar is one of the handy toolbars in SQL Server Management Studio (SSMS). Do let me know if you use it and found it helpful.
SQL Server Management Studio is a handy tool that gives us the control to easily manage SQL Server. However, in Azure SQL Server, you can use its own query windows, where you can pass query against database. In today’s article, I will explain how to connect Azure SQL Server using your (on premises) SQL Server Management Studio (SSMS).
Given below is a step by step approach, demonstrating how to CONNECT Azure SQL using SSMS in simple steps.
Step 1 : (Create SQL Server in Azure)
First of all, you need to create/ setup a Server in Azure SQL Server using pre-requisite article.
Note : If you already have Setup Azure SQL Server, skip this step.
Step 2 : (Configure IP Address)
Once you have setup the Azure SQL Server in the above step, you just need to select that particular Server then further select Configure to add your local Server IP address from where you want to connect Azure using SSMS. This step is most important step because if you bypass this step and unable to add IP address of your local Server here, Azure will not allow your SSMS to connect Azure SQL Server.
Note : If you already configured the IP address of your local SQL Server machine, skip this step.
Step 3 : (Open SSMS)
Lets open SQL Server Management Studio and try to connect Azure SQL Server. Given below is the info that you must pass at the time of connectivity as shown below and Press ConnectButton. Make sure your caps lock key should be turned on/ off accordingly ;).
Server Name : Azure SQL Server Name.database.windows.net (gx8icm0cm.database.windows.net) Login : The login name which we created in pre-requisite article step 3. Password : The password which we created in pre-requisite article step 3.
Step 4 : (Azure SQL Server Connected in SSMS)
Now, you have connected Azure SQL Server using SQL Server Management Studio as shown below.
This blog/website is a personal blog/website and all articles, postings and opinions contained herein are my own. The contents of this blog/website are not intended to defame, purge or humiliate anyone should they decide to act upon or reuse any information provided by me. Comments left by any independent reader are the sole responsibility of that person. Should you identify any content that is harmful, malicious, sensitive or unnecessary, please contact me via email (imran@raresql.com) so I may rectify the problem.