SSMS vs pgAdmin

What is SSMS? (The Microsoft Powerhouse)

SQL Server Management Studio (SSMS) is the native integrated environment for managing any SQL Server infrastructure. Developed by Microsoft, it is widely considered the gold standard for administrative tooling. It’s not just a query editor; it’s a full-scale command center.

Key Features of SSMS in 2026:

• Object Explorer: A highly intuitive tree view for managing databases, security, and server objects.
• Intelligent Query Processing: Native AI-driven suggestions (now bolstered by GitHub Copilot integration) that help write T-SQL faster.
• XEvent Profiler: Advanced monitoring that has largely replaced the old SQL Profiler for real-time troubleshooting.
• Integration Services (SSIS): Built-in support for managing complex ETL packages.

What is pgAdmin? (The Open Source Champion)

On the other side of the ring, we have pgAdmin, the most popular open-source management tool for PostgreSQL. While SSMS is tied to Windows and SQL Server, pgAdmin is the “citizen of the world.” It’s cross-platform, web-based, and built by the community for the community.

Key Features of pgAdmin in 2026:

• Web-Based Architecture: It can run as a standalone desktop app or as a web service on a server.
• Query Tool with Auto-Commit: A sleek interface for writing and executing asynchronous queries.
• Dashboarding: Real-time visual monitoring of server sessions, transactions per second, and locks.
• ERD Tool: A built-in Entity Relationship Diagram creator that is surprisingly robust for a free tool.

Head-to-Head Comparison: The “Must-Know” Differences

Before we dive into the tutorial, let’s look at the cold, hard facts. I’ve compiled this comparison table based on my experience managing high-traffic clusters.

First-Person Tutorial: Navigating Your First Session

Part 1: Setting the Stage in SSMS

When I open SSMS, the first thing I do is connect to my Object Explorer.

1. Connecting: I use Windows Authentication for local dev, but for production, I’m always using Azure Active Directory (now Microsoft Entra) with Multi-Factor Authentication.
2. The Environment: I immediately head to Tools > Options to enable “Line Numbers” and “Check for updates on startup.”
3. Writing a Query: I hit Ctrl+N for a new query window. The T-SQL IntelliSense in SSMS is incredibly snappy. If I’m working on a slow-running report, I right-click the query and select “Include Actual Execution Plan.” > Note: The graphical execution plan in SSMS is, in my opinion, the best in the business. It shows exactly which index is missing and even offers a “Missing Index” suggestion in green text at the top.

Part 2: Moving to the Open Side with pgAdmin

Now, let’s say my project requires a PostgreSQL backend for a mobile app. I fire up pgAdmin 4.

1. The Dashboard: Unlike SSMS, pgAdmin drops you into a Dashboard first. I love this. I can immediately see the “Transactions per second” and “Server sessions.” If a dev in the San Francisco office left a transaction hanging, I see it here instantly.
2. Server Registration: I right-click “Servers” and choose “Register.” One thing to watch for here: pgAdmin is very strict about SSL modes. If you’re connecting to an AWS RDS instance, make sure your “SSL Mode” is set to ‘Require’ or ‘Verify-Full.’
3. The Query Tool: I click the lightning bolt icon. The pgAdmin query tool feels more like a modern code editor (think VS Code light). One feature I use constantly is the “Filter” on the data output grid—it allows me to filter results without rewriting the WHERE clause.

Performance and Usability: An Honest Assessment

SSMS:

SSMS is built for the long haul. It can handle thousands of tables and complex schemas without breaking a sweat. However, it is resource-heavy. If you are running it on a laptop with only 8GB of RAM while also hosting a Zoom call and a Docker container, you’re going to feel the lag.

pgAdmin:

pgAdmin is agile. Because it’s web-based, I can actually host it on a central server and my entire team can access it via a URL—no installation required on their local machines. This is a game-changer for remote teams spread across different time zones.

However, pgAdmin can sometimes feel “clunky” when dealing with massive data exports. If I’m trying to view a result set of 100,000 rows, pgAdmin’s browser-based rendering can struggle compared to the native rendering of SSMS.

Which Tool Should You Choose?

Choose SSMS if:

• You are primarily working in a Windows-centric environment.
• You manage SQL Server Integration Services (SSIS) or Analysis Services (SSAS).
• You need the most advanced graphical execution plan analysis available.
• Your company relies on Active Directory for granular security.

Choose pgAdmin if:

• You are building cloud-native applications on PostgreSQL.
• You work on macOS or Linux (SSMS won’t even install there).
• You want a free, open-source tool that is updated frequently by the community.
• You prefer a web-based interface that can be shared across a team.

Expert Tips for More Productivity

• Dark Mode: Both tools finally have excellent dark modes. Save your eyes during those late-night deployment windows!
• Keyboard Shortcuts: Learn them. In SSMS, Alt+F1 on a table name gives you its schema. In pgAdmin, F5 executes the query. These seconds add up.
• Version Control: Don’t just write queries in the GUI. Both tools now have better integration with Git. Always commit your migration scripts to a repository like GitHub or GitLab.
• AI Integration: Use the new AI assistants. If a query is slow, ask the integrated AI to “Explain this plan in plain English.” You’d be surprised how often it points out a simple casting error or a missing join predicate.

Final Thoughts

In the battle of SSMS vs. pgAdmin, there is no loser—only different use cases.

If I’m working for a traditional bank, I’m probably using SSMS. It’s robust, secure, and integrated. If I’m at a tech startup in Boulder, CO, building a scalable web app, pgAdmin (or even a CLI like psql) is my go-to.

The beauty of the 2026 data landscape is that these tools are becoming more alike. pgAdmin is getting more “enterprise-grade” features, and SSMS is becoming more “cloud-aware.”

You may also like the following articles:

• SSMS vs Azure Data Studio
• Rename Database SSMS
• SSMS 22 New Features
• SSMS Latest Version

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com

Rename Database SSMS

Method 1: The Graphical User Interface (GUI) Way

For most day-to-day tasks in dev environments, the SSMS GUI is the most intuitive path.

Step-by-Step GUI Rename:

1. Open SQL Server Management Studio and connect to your instance.
2. Expand the Databases node in the Object Explorer.
3. Crucial Step: Ensure no one is using the database. (See the “Single User Mode” section below if you get an error).
4. Right-click the target database and select Rename.
5. Type the new name and press Enter.
6. Right-click the Databases folder and select Refresh to verify the change. Check out the screenshot below for your reference.

Expert Insight: If you see an error stating “The database could not be exclusively locked,” it means there are active sessions. I personally prefer Method 2 (T-SQL) for production servers because it allows me to force-close those sessions.

Method 2: The Professional T-SQL Script (Recommended)

When I am working on a mission-critical server, I never use the GUI. I use a script. Why? Because a script is repeatable, documented, and far more powerful at handling active connections.

The “Force Rename” Script

This script does three things: it kicks everyone out, changes the name, and lets everyone back in.

SQL

USE master;
GO

-- 1. Set the database to Single User mode and kick everyone out immediately
ALTER DATABASE [Old_DB_Name] 
SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
GO

-- 2. Perform the actual rename
ALTER DATABASE [Old_DB_Name] 
MODIFY NAME = [New_DB_Name];
GO

-- 3. Set the database back to Multi User mode
ALTER DATABASE [New_DB_Name] 
SET MULTI_USER;
GO

After executing the query above, I received the expected output, as shown in the screenshot below.

Why “ROLLBACK IMMEDIATE”?

In a busy office in Austin, a user might have a transaction open. ROLLBACK IMMEDIATE tells SQL Server to terminate those transactions and disconnect the users instantly so the rename can happen without waiting for them to finish their lunch break.

The “Physical File” Dilemma: Renaming .mdf and .ldf

After a rename, you might notice that your files on the C: or D: drive still have the old names. For a truly clean environment, you may want the physical files to match the logical name.

How to Rename Physical Files:

1. Detach the database in SSMS.
2. Go to the Windows folder and manually rename the .mdf and .ldf files.
3. Attach the database in SSMS, pointing to the new file names and specifying the new database name.

Troubleshooting: Common SSMS Rename Errors

Here is how to scale them:

1. Msg 5030: Database could not be exclusively locked

• The Cause: Someone (or a background service) is connected.
• The Fix: Use the SET SINGLE_USER script provided above.

2. Error: Login failed for user

• The Cause: After a rename, your application’s connection string is still looking for the old name.
• The Fix: You must update all .config files, .env files, and SQL Server Agent Jobs to point to the new name.

3. “The database is a system database”

• The Warning: You cannot rename master, model, tempdb, or msdb. Don’t even try—it will break the entire SQL instance.

Conclusion

Renaming a database in SSMS is a task that requires both precision and a plan. Whether you use the quick GUI method for a local project or the authoritative T-SQL script for a production cluster, always ensure you have exclusive access and a recent backup.

You may also like the following articles:

• SQL Join Example With Where Clause
• SSMS Keyboard Shortcuts
• How to find SQL Server instance name in SSMS
• How To Insert Data In SSMS

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com

SSMS vs Azure Data Studio

Defining SSMS and Azure Data Studio

Before we compare them, we must understand their DNA. One is a legacy powerhouse; the other is a modern, cross-platform challenger.

What is SSMS?

SQL Server Management Studio (SSMS) has been the gold standard since 2005. It is a comprehensive, Windows-only integrated environment for managing any SQL infrastructure, from SQL Server to Azure SQL Database. It is built for the “Deep DBA”—the person responsible for server configuration, security, and complex maintenance.

What is Azure Data Studio?

Azure Data Studio is the “new kid on the block,” released in 2018. Built on the VS Code shell, it is a lightweight, cross-platform (Windows, macOS, Linux) editor focused on data development and query execution. It brings modern features like Notebooks and an integrated terminal to the SQL world.

1. Platform Availability: Where Do You Work?

• SSMS: Strictly Windows-only. If you are a Mac user in San Francisco, you’ll need a virtual machine or a Remote Desktop session to a server in Dallas to run SSMS.
• Azure Data Studio: Fully Cross-Platform. Whether you are on a MacBook Pro or a Linux workstation, ADS runs natively. This makes it the darling of modern DevOps teams who don’t want to be tethered to a single OS.

2. Core Functionality: DBA vs. Developer

This is where the two tools diverge most sharply. I often tell my teams that SSMS is for administering the database, while ADS is for interacting with the data.

SSMS: The Administrator’s Command Center

If you need to perform deep-level tasks, SSMS is your only choice. It contains hundreds of “property” windows and wizards that ADS simply does not have.

• Query Store Management: Deep visual analysis of query performance.
• Policy-Based Management: Enforcing standards across a fleet of servers.
• SQL Server Agent: Detailed scheduling and monitoring of jobs.
• Database Diagrams: Visualizing complex schemas for a logistics firm in Atlanta.

Azure Data Studio: The Developer’s Playground

ADS is optimized for writing code. It feels like a modern text editor because it is one.

• Smart Code Completion: IntelliSense in ADS is often faster and more intuitive.
• Integrated Terminal: Run PowerShell, Bash, or cmd right next to your SQL query.
• Notebooks: This is the “killer feature.” You can combine formatted text (Markdown) with executable SQL code blocks—perfect for creating “Runbooks” for your night-shift team.

Comparison Table: Feature Breakdown

3. Visualization and Charting

• Azure Data Studio wins here. It allows you to create instant visualizations of your query results. With a few clicks, you can turn a result set into a bar chart or a pie graph.
• SSMS is strictly a grid or text output tool. To visualize data from SSMS, you usually have to export it to Excel or Power BI.

4. The Extension Ecosystem

Customization is the hallmark of a professional’s toolkit.

• ADS leverages the massive VS Code extension library. You can add support for PostgreSQL, MySQL, and even AI-powered coding assistants like GitHub Copilot.
• SSMS has a much smaller ecosystem. While companies like Redgate offer powerful tools for it, the platform is not as “plugin-friendly” as the modern ADS shell.

Tutorial: Which Tool Should You Open?

Use SSMS When:

1. Configuring Security: Managing logins, roles, and encryption for a sensitive project in Denver.
2. Performance Tuning: Using the Execution Plan and Database Engine Tuning Advisor.
3. Maintenance: Running backups, restores, or shrinking files.
4. Legacy Support: Working with very old versions of SQL Server (pre-2014).

Use Azure Data Studio When:

1. Writing Scripts: Crafting complex T-SQL for a new web app in Los Angeles.
2. On a Mac/Linux: If you aren’t on Windows, this is your primary tool.
3. Creating Documentation: Using SQL Notebooks to explain how a query works to a junior dev in Miami.
4. Quick Lookups: It launches faster than SSMS, making it perfect for “quick checks.”

Conclusion:

The battle of SSMS vs. Azure Data Studio isn’t about one being “better” than the other. It’s about Role-Based Utility.

If your job title is Database Administrator, you will live in SSMS. Its depth and administrative power are unmatched. However, if you are a Data Engineer or a Full-Stack Developer, Azure Data Studio will feel like home. Its modern interface and cross-platform flexibility align perfectly with the modern dev cycle.

You may also like the following articles:

• SSMS vs pgAdmin
• SSMS Keyboard Shortcuts
• SQL Select Query Examples
• SSMS 22 New Features
• Copilot In SSMS

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com

SQL Server Error 18456

What is SQL Server Error 18456?

At its core, Error 18456 is an authentication failure. It indicates that a user or application tried to connect to a SQL Server instance, but the server rejected the “digital handshake.”

The “Security Shield”

Microsoft designed this error with a specific security philosophy: Information obfuscation. When you see this error in your application or SQL Server Management Studio (SSMS), it often just says:

Login failed for user ‘<username>’. (Microsoft SQL Server, Error: 18456)

It won’t tell you why—at least not on the front end. To find the “Why,” we have to look at the SQL Server Error Log.

Phase 1: Decoding the State Codes

The secret to solving Error 18456 lies in the State Code. Each number represents a specific reason for the failure. I’ve compiled this table of the most common state codes I encounter in high-performance tech environments.

18456 State Code Reference Table

Phase 2: How to Find the “Hidden” State Code

To troubleshoot like an expert, you must go to the source. You can’t fix what you can’t see.

1. Open SQL Server Management Studio (SSMS).
2. Connect to your instance (using an account that can log in, like a Windows Admin).
3. In the Object Explorer, navigate to Management > SQL Server Logs.
4. Double-click the Current log.
5. Search for the text “18456”. You will see an entry that looks like this:Error: 18456, Severity: 14, State: 8. Check out the screenshot below for your reference.

Phase 3: Step-by-Step Fixes for Common Scenarios

Once you have your State Code, follow these authoritative steps to resolve the most common blockers.

1. Enabling Mixed Mode Authentication (State 58)

If you are trying to use a SQL Login (like sa) but your server is set to “Windows Only,” the connection will fail every time.

• The Fix:
  • Right-click the Server Name in Object Explorer and select Properties.
  • Go to the Security page.
  • Select SQL Server and Windows Authentication mode.
  • Crucial: You must restart the SQL Server service for this to take effect. Check out the screenshot below for your reference.

2. Enabling a Disabled Login (State 7)

Sometimes, during a security audit, accounts are disabled for compliance.

• The Fix:
  • Go to Security > Logins.
  • Right-click the user and select Properties.
  • Navigate to the Status page.
  • Ensure Login is set to Enabled.

3. Fixing Incorrect Database Access (State 11/12)

If your application for a retail giant in Minneapolis connects fine but can’t see its data, you likely have a mapping issue.

• The Fix:
  • In the Login Properties, go to User Mapping.
  • Ensure the user is mapped to the correct database.
  • Check that they have the appropriate role (like db_datareader or db_datawriter).

Best Practices for Preventing Login Failures

The best way to handle Error 18456 is to prevent it through strict standards.

• Use Windows Authentication: Whenever possible, avoid SQL Logins. Integrated Windows Authentication (Active Directory) is more secure and avoids “password rot.”
• Audit Default Databases: If you delete a database that was set as a user’s “Default Database,” their login will fail with State 38. Always update default databases before a deletion.
• Monitor the Error Log: I recommend setting up an Azure Monitor or SQL Agent Alert to ping your team in Phoenix whenever multiple 18456 errors occur in a short window. This is often a sign of a “Brute Force” attack.

Conclusion

SQL Server Error 18456 is a common but multifaceted hurdle. By understanding that the server is “hiding” the answer in the State Code, you can move from frustration to resolution. Whether it’s a simple password typo or a complex authentication mode mismatch, the Error Log is your primary tool.

You may also like the following articles:

• SSMS Cannot Connect To Server
• SQL Error Code
• Generate Insert Statements From Table SQL Server

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com

SQL Join Example With Where Clause

The Fundamentals: Connecting Tables and Filtering Results

At its core, a JOIN combined with a WHERE clause allows you to retrieve data from two or more tables while applying specific filtering criteria to the final result set.

Think of it this way: the JOIN logic (using the ON clause) defines how the tables are related, while the WHERE clause defines which rows from that combined set should be displayed.

The Standard Syntax

I always follow this standard structure:

SQL

SELECT 
    t1.ColumnName, 
    t2.ColumnName
FROM Table1 AS t1
INNER JOIN Table2 AS t2 
    ON t1.CommonKey = t2.CommonKey
WHERE t1.FilterColumn = 'SpecificValue';

1. The INNER JOIN with WHERE Clause

The most common scenario involves an INNER JOIN. This returns only the records that have matching values in both tables. When you add a WHERE clause, you are further narrowing down that “shared” set of data.

Imagine you are managing a logistics system for a company. You have an Orders table and a Customers table. You only want to see orders placed by customers located in “Miami”.

Example

SQL

SELECT 
    o.OrderID, 
    o.Amount, 
    c.Name
FROM Orders AS o
INNER JOIN Customers AS c 
    ON o.CustomerID = c.CustomerID
WHERE c.City = 'Miami';

After executing the query above, I received the expected output, as shown in the screenshot below.

Why this works:

• The JOIN: Links orders to specific customers.
• The WHERE: Discards every order in the database unless the associated customer resides in the Big Apple.

2. Filtering with LEFT JOIN: The “Anti-Join” Trap

Things get more sophisticated when using a LEFT JOIN. A LEFT JOIN returns all rows from the left table and the matched rows from the right table. If there is no match, the right side results are NULL.

The Common Pitfall

A common mistake I see among junior developers is placing a filter in the WHERE clause that accidentally turns their LEFT JOIN into an INNER JOIN.

• Scenario: You want a list of all customers and their orders, but you only want to see orders from the year 2026.
• The Mistake: Placing WHERE o.OrderYear = 2026. Because NULL (for customers with no orders) is not equal to 2026; those customers are filtered out entirely!

The Pro Fix: Filter in the ON Clause vs. WHERE

3. Advanced Filtering: Using Multiple Conditions

Using AND/OR in the WHERE Clause

SQL

SELECT 
    e.EmployeeName, 
    d.DepartmentName, 
    e.Salary
FROM Employees AS e
JOIN Departments AS d 
    ON e.DeptID = d.DeptID
WHERE d.Region = 'West' 
    AND e.Salary > 90000;

This query identifies high-earning individuals specifically in the West Coast divisions, excluding anyone in East Coast hubs like Philadelphia or DC.

4. Working with Dates and Ranges

Businesses often run reports based on specific fiscal quarters or timeframes. Using BETWEEN or comparison operators in the WHERE clause is essential.

SQL

SELECT 
    p.ProductName, 
    s.SaleDate
FROM Products AS p
JOIN Sales AS s 
    ON p.ProductID = s.ProductID
WHERE s.SaleDate BETWEEN '2026-01-01' AND '2026-03-31';

This provides a clear snapshot of Q1 performance for your sales team.

5. Handling NULLs in Joined Filters

Data is rarely perfect. When joining tables, you may encounter missing values. To handle this with authority, use IS NULL or IS NOT NULL in your WHERE clause.

Example: Finding “Stray” Records

If you want to find customers who have never placed an order (often called an “Anti-Join”):

SQL

SELECT c.CustomerName
FROM Customers AS c
LEFT JOIN Orders AS o 
    ON c.CustomerID = o.CustomerID
WHERE o.OrderID IS NULL;

Summary of SQL Join and Where Logic

Conclusion

The SQL JOIN with a WHERE clause is a foundational tool for any database professional. By understanding the distinction between the ON clause (the relationship) and the WHERE clause (the filter), you can write queries that are not only accurate but also optimized for speed.

You may also like the following articles:

• SQL Select Query Examples
• How To Find Who Updated The Table In SQL Server
• SQL Server Update Table From Another Table

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com

SSMS Keyboard Shortcuts

1. The Core Execution

These are the “Big Three” commands I use 500 times a day.

• F5 (or Ctrl + E): Execute. This is the bread and butter of SSMS. It runs the entire script or just the highlighted text.
• Ctrl + N: New Query. I often use this when a colleague in Chicago pings me with a quick data request. It opens a fresh editor window instantly.
• Ctrl + Shift + R: Refresh IntelliSense Cache. We’ve all been there—you just added a new column to a table, but SSMS still shows a red squiggle. This command forces SSMS to re-read the schema.

Pro Tip: The “Partial Execution” Rule

Highlight before you hit F5. If you have a 1,000-line script and you only need to run the UPDATE on line 45, highlight just that statement. SSMS will ignore everything else, saving you from accidental data wipes.

2. Navigation Shortcuts: Mastering the Object Explorer

Managing a server in a data center means dealing with thousands of objects. Don’t scroll—navigate.

3. The Formatting & Editing Toolkit: Writing Clean T-SQL

Use these shortcuts to ensure your code is readable by the next person on rotation.

Text Transformation

• Ctrl + Shift + U: Make selected text UPPERCASE. (Standard for SQL keywords).
• Ctrl + Shift + L: Make selected text lowercase.
• Ctrl + K, Ctrl + C: Comment out a block of code.
• Ctrl + K, Ctrl + U: Uncomment code.

The “Vertical Selection” Trick

One of the most powerful moves in my arsenal is the Alt + Mouse Drag. While holding Alt, you can select a vertical column of text. This is a lifesaver when you need to add commas or aliases to 50 columns at once.

4. Query Results Management

Once you run your query, you need to see the data—or hide it to make room for more code.

• Ctrl + R: Toggle Results Pane. This is the most used shortcut in my Manhattan office. It hides the results so you can see more of your code window.
• Ctrl + T: Output results to Text.
• Ctrl + D: Output results to Grid (Default).
• Shift + F6: Move focus into the results grid so you can use arrow keys to browse data.

5. The 2026 AI Era: Copilot & Modern Shortcuts

As we move into 2026, SSMS has integrated AI-assisted coding to keep up with the demands of tech firms.

• Ctrl + Alt + C: Display Copilot in SSMS. This launches the AI chat or inline assistance, helping you draft complex window functions or CTEs in seconds.
• Ctrl + G: Go To Line. When a fellow DBA in Dallas tells you there’s a bug on line 452, this gets you there in a heartbeat.

6. Customizing Your Own Query Shortcuts

As an authority on SSMS, I don’t just use the defaults—I build my own. In SSMS, you can map specific stored procedures to Ctrl + # keys.

My Recommended Custom Mappings:

Navigate to Tools > Options > Environment > Keyboard > Query Shortcuts and try these:

1. Ctrl + 3: Set to EXEC sp_whoisactive;. (Instantly see what’s running on the server).
2. Ctrl + 4: Set to SELECT TOP(100) * FROM. (Highlight a table name and hit this to see a preview).
3. Ctrl + 5: Set to sp_help. (The quickest way to see table schemas).

Summary Table: Essential SSMS Shortcuts

Conclusion

Mastering SSMS keyboard shortcuts is more than just a speed trick—it’s about increasing your productivity. When you aren’t fighting the interface, you can focus on the logic of your T-SQL. Whether you are building the next big app or maintaining a massive data warehouse, these commands will make you an indispensable asset to your team.

You may also like the following articles:

• SQL Select Query Examples
• How To Run Query In SSMS
• SSMS 22 New Features

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com

SSMS Cannot Connect To Server

Before we start clicking buttons, we need to understand the mechanics. When you open SQL Server Management Studio (SSMS) and hit “Connect,” the client sends a request across the network (or local pipe) to the SQL Server Browser or directly to the Database Engine. If that “handshake” fails, SSMS throws a generic error.

The most common culprits are:

• Error 26: Error Locating Server/Instance Specified.
• Error 40: Could not open a connection to SQL Server.
• Error 18456: Login failed (Authentication issues).

Phase 1: The 60-Second Check

I always start with the basics.

1. Is the SQL Server Service Running?

If the engine isn’t running, the door is locked.

• Open SQL Server Configuration Manager or services.msc.
• Locate the service named SQL Server (MSSQLSERVER) (for default instances) or SQL Server (InstanceName).
• Ensure the status is Running. If it is “Stopped,” right-click and select Start.

2. Verify the Server Name Syntax

Typing the wrong server name is the #1 cause of Error 26.

• Default Instance: Use the computer name (e.g., NYC-PROD-DB01) or . for local.
• Named Instance: Use ComputerName\InstanceName (e.g., NYC-PROD-DB01\DEVELOPMENT).
• The “Period” Trick: For a local default instance, simply typing a single period . or (local) in the server name box is the fastest way to connect.

Phase 2: Enabling Network Protocols

By default, SQL Server is installed with high security, which often means remote connections are disabled. If you are trying to connect from a satellite office in Phoenix to a server in Chicago, you must enable the right lanes.

Enabling TCP/IP

1. Open SQL Server Configuration Manager.
2. Navigate to SQL Server Network Configuration > Protocols for [YourInstance].
3. Right-click TCP/IP and select Enable.
4. Crucial: You must restart the SQL Server service for this to take effect.

Phase 3: The Firewall

In the USA corporate world, security is paramount, and the Windows Firewall is often the reason SSMS cannot talk to the server. The server might be listening on Port 1433, but the firewall is blocking the incoming request.

Configuring Inbound Rules

You don’t need to disable your firewall; you just need a surgical exception.

1. Open Windows Defender Firewall with Advanced Security.
2. Click Inbound Rules > New Rule.
3. Select Port > TCP > Specific local ports: 1433.
4. Select Allow the connection.
5. Name it SQL_1433_Inbound.

The SQL Browser Service

If you are using a Named Instance, you must also open UDP Port 1434. This allows the SQL Browser service to tell your client which dynamic port the named instance is currently using.

Phase 4: Troubleshooting Remote Connections

If the ports are open but you still can’t connect, the SQL Server instance itself might be told to ignore remote requests.

1. Connect to the server locally (if possible).
2. Right-click the server in Object Explorer and select Properties.
3. Go to the Connections page.
4. Ensure “Allow remote connections to this server” is checked.

Phase 5: Authentication Failures (Error 18456)

If you get as far as an authentication prompt but it fails, the “handshake” was successful, but your “ID” was rejected.

Mixed Mode Authentication

Many firms use a mix of Windows logins and specific SQL logins (like sa).

• Go to Server Properties > Security.
• Ensure “SQL Server and Windows Authentication mode” is selected.
• If you switch from Windows-only to Mixed Mode, a service restart is mandatory.

Phase 6: Professional Testing Tools

1. The PowerShell “Ping”

Open PowerShell and run this command to see if the port is actually reachable:

PowerShell

Test-NetConnection -ComputerName YourServerName -Port 1433

If TcpTestSucceeded is True, the network is fine—the problem is your SQL permissions.

2. The UDL File Trick

This is my “secret weapon” for testing connectivity without opening SSMS.

1. Create a blank file on your desktop named test.udl.
2. Double-click it.
3. Enter your server and login info.
4. Click Test Connection. This uses the native Windows OLE DB provider and is the purest test of connectivity available.

Advanced Scenarios: VPN and Multi-Subnet Clusters

• VPN Latency: If you are on a slow VPN, SSMS might “time out” before the server responds. You can increase the Connection Timeout in the SSMS connection dialog under “Options” > “Connection Properties.”
• Multi-Subnet Failover: If you are connecting to an Always On Availability Group, ensure your connection string (or SSMS options) includes MultiSubnetFailover=True.

Step-by-Step Tutorial

We follow this exact sequence:

1. Verify Service: Is SQL Server running? (Check Configuration Manager).
2. Verify Name: Are we using Server\Instance correctly?
3. Check Protocols: Is TCP/IP enabled?
4. Test Port: Can we reach the server via PowerShell on 1433?
5. Check Firewall: Is there an inbound rule for SQL?
6. Verify Login: Is the account locked out or using the wrong password?
7. Check SQL Browser: (For named instances) Is it running?

Conclusion

“SSMS cannot connect to server” is a broad error, but with a systematic approach, it is always solvable. By following this authoritative guide, you move from guessing to knowing. Start with the service, check the protocols, verify the firewall, and finally validate the authentication.

You may also like the following articles:

• SQL Server Error 18456
• How to find SQL Server instance name in SSMS
• SQL Select Query Examples
• How To Insert Data In SSMS

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com

How to find SQL Server instance name in SSMS

In the Microsoft SQL Server ecosystem, you can have multiple “instances” of SQL Server running on a single physical or virtual machine.

• Default Instance: This typically takes the name of the computer itself (e.g., NYC-PROD-DB01).
• Named Instance: This is a specific installation with a unique name appended to the server (e.g., NYC-PROD-DB01\PAYROLL).

Method 1: The “Connect to Server” Dialog (The Quickest Way)

The most common place to find your instance name is the very first screen you see when launching the application. If you’ve already connected in the past, SSMS likely has a “memory” of your server names.

Using the Dropdown Menu

1. Launch SQL Server Management Studio.
2. When the Connect to Server dialog box appears, look at the Server name field.
3. Click the downward arrow at the end of the text box.
4. Select <Browse for more…> from the bottom of the list. Check out the screenshot below for your reference.

Using the “Browse for More” Feature

This is a lifesaver for consultants who travel between different US-based offices.

1. In the Browse for Servers window, click the Local Servers tab.
2. Expand the Database Engine node.
3. Here, SSMS will list all SQL Server instances it can detect on your local machine.
4. Select the instance name (e.g., LAPTOP-DENVER\SQLEXPRESS) and click OK.

Method 2: Identifying Instance Name via Object Explorer

Reading the Object Explorer Tree

The top node of the Object Explorer tree displays the instance name in a specific format:

• ServerName\InstanceName (SQL Server Version – UserLogin). Check out the screenshot below for your reference.

Breaking Down the Display

Method 3: Using T-SQL Queries (The Pro Method)

As a database professional, I always prefer scripts over the GUI. Queries are immutable, shareable, and provide the most accurate “ground truth” directly from the engine.

The Standard Global Variable

To get the instance name quickly, run this in a New Query window (Ctrl + N):

SQL

SELECT @@SERVICENAME AS 'Instance Name';

• Result: If it returns MSSQLSERVER, you are on a Default Instance. If it returns a name (like DEVELOPMENT), that is your Named Instance.

After executing the query above, I received the expected output, as shown in the screenshot below.

The Full Server Name Query

If you need both the computer name and the instance name (the format required for connection strings), use this:

SQL

SELECT SERVERPROPERTY('ServerName') AS 'Full Instance Name';

Checking the Service Name and Version

For a more detailed audit, use this comprehensive query:

SQL

SELECT 
    SERVERPROPERTY('MachineName') AS [Computer Name],
    SERVERPROPERTY('InstanceName') AS [Instance Name],
    SERVERPROPERTY('Edition') AS [Edition],
    SERVERPROPERTY('ProductVersion') AS [Version];

After executing the query above, I received the expected output, as shown in the screenshot below.

Method 4: Checking Windows Services

Sometimes SSMS itself won’t connect, and you need to find the instance name to troubleshoot why. In this case, we go to the source: the Windows Services Manager.

1. Press Win + R on your keyboard, type services.msc, and hit Enter.
2. Scroll down to the entries starting with SQL Server.
3. Look at the text inside the parentheses.
   • SQL Server (MSSQLSERVER) = Default Instance.
   • SQL Server (TEST_INSTANCE) = The instance name is TEST_INSTANCE.

Expert Tip: If the service is “Stopped,” you won’t be able to connect in SSMS even if you have the correct name. Ensure the status is Running before trying to log in.

Method 5: Using SQL Server Configuration Manager

If you are a systems administrator in San Francisco managing multiple environments, the SQL Server Configuration Manager is your best friend. It provides a clean, consolidated view of every instance installed on that machine.

1. Open the Start Menu and search for SQL Server Configuration Manager.
2. Click on SQL Server Services in the left-hand pane.
3. The right-hand pane will list every instance.
4. Note the name following “SQL Server” in the list—this is exactly what you should type into the SSMS connection box.

Summary of Methods

Video Tutorial

Conclusion

Finding your SQL Server instance name in SSMS is a foundational skill that allows you to navigate complex data environments with confidence. Whether you are using the visual “Browse for more” feature, running high-level T-SQL queries, or digging into Windows Services, knowing where this information lives is the first step toward database mastery.

You may also like the following articles:

• Rename Database SSMS
• SSMS Cannot Connect To Server
• How To Insert Data In SSMS
• How To Run Query In SSMS
• How To Comment In SSMS
• SSMS 22 New Features

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com

SQL Select Query Examples

The Anatomy of a SELECT Statement

Before we dive into the examples, we must understand the core logic. A SELECT query isn’t just a command; it’s a request for a specific subset of reality.

The Basic Syntax

The fundamental structure of every query we will discuss follows this hierarchy:

1. SELECT: Which columns do you want?
2. FROM: Which table holds the data?
3. WHERE: What are the filters?
4. ORDER BY: How should the results be sorted?

1. Basic Retrieval

Selecting All Columns

While common in development, I always caution my teams against using SELECT * in production code. It’s inefficient and can break applications if the schema changes.

SQL

-- Selecting all columns from a customer table
SELECT * FROM dbo.Customers;

After executing the above query, I got the expected output as shown in the screenshot below.

Selecting Specific Columns

Efficiency is key. If you only need names and emails for a marketing campaign in Chicago, only ask for those.

SQL

SELECT Name, City FROM dbo.Customers;

After executing the above query, I got the expected output as shown in the screenshot below.

2. Filtering Data with the WHERE Clause

Using Comparison Operators

SQL

-- Finding high-value orders
SELECT OrderID, Amount
FROM dbo.Orders
WHERE Amount > 300.00;

After executing the above query, I got the expected output as shown in the screenshot below.

Filtering with Multiple Conditions

We use AND and OR to refine our search. Imagine searching for employees in San Francisco who work in the Engineering department:

SQL

SELECT Name, City
FROM dbo.Customers
WHERE City = 'Boston' 
AND Name = 'John Smith';

After executing the above query, I got the expected output as shown in the screenshot below.

Using the IN Operator

The IN operator is a cleaner way to handle multiple OR conditions.

SQL

-- Finding customers in specific tech hubs
SELECT CustomerName, State
FROM dbo.Customers
WHERE State IN ('CA', 'TX', 'WA', 'NY');

3. Advanced Pattern Matching with LIKE

Sometimes, you don’t know the exact value. Perhaps you are a customer support rep in Phoenix trying to find a client whose name starts with “Mc.”

• % (Percent): Represents zero, one, or multiple characters.
• _ (Underscore): Represents a single character.

SQL

-- Finding all customers with names starting with 'john'
SELECT Name, City
FROM dbo.Customers
WHERE Name LIKE 'john%';

-- Finding emails that end in .gov
SELECT Email
FROM dbo.Staff
WHERE Email LIKE '%.gov';

4. Sorting and Limiting Results

Presentation matters. When reporting to a board of directors in Washington D.C., you need your data organized.

Sorting with ORDER BY

SQL

-- Sorting products from most expensive to cheapest
SELECT ProductName, Price
FROM dbo.Products
ORDER BY Price DESC;

Limiting Results (TOP / LIMIT)

In SQL Server (common in US corporate environments), we use TOP. In MySQL or PostgreSQL (common in startups), we use LIMIT.

SQL

-- Getting the top 5 highest earners
SELECT TOP 5 EmployeeName, Salary
FROM dbo.Payroll
ORDER BY Salary DESC;

5. Aggregate Functions and Data Summarization

As an authority in data, you’ll often be asked for “the big picture.” Aggregates turn thousands of rows into a single, powerful number.

SQL

-- Calculating total sales from the Dallas branch
SELECT SUM(OrderTotal) AS TotalRevenue
FROM dbo.Sales
WHERE BranchCity = 'Dallas';

6. The Power of GROUP BY and HAVING

Aggregates become truly transformative when combined with GROUP BY. This allows you to categorize your summaries.

Grouping Data

If you need to see the number of customers per state across the USA:

SQL

SELECT State, COUNT(CustomerID) AS CustomerCount
FROM dbo.Customers
GROUP BY State;

Filtering Groups with HAVING

The WHERE clause filters rows before they are grouped. The HAVING clause filters the results after the grouping.

SQL

-- Finding states with more than 500 customers
SELECT State, COUNT(CustomerID) AS Total
FROM dbo.Customers
GROUP BY State
HAVING COUNT(CustomerID) > 500;

7. Joins: Connecting the Dots

In a normalized database, data is split across tables. A pro knows exactly how to stitch it back together.

INNER JOIN

The most common join. It returns records that have matching values in both tables.

SQL

-- Joining Orders with Customers to see who bought what
SELECT o.OrderID, c.FirstName, c.LastName, o.OrderDate
FROM dbo.Orders o
INNER JOIN dbo.Customers c ON o.CustomerID = c.CustomerID;

LEFT JOIN (LEFT OUTER JOIN)

This is critical when you want to see all records from the left table, even if there’s no match in the right table.

SQL

-- Finding all employees and their assigned projects (including those with no project)
SELECT e.EmployeeName, p.ProjectName
FROM dbo.Employees e
LEFT JOIN dbo.Projects p ON e.ProjectID = p.ProjectID;

8. Working with Dates

In the United States, date formats can be a point of contention. However, in SQL, we treat them with strict logic.

SQL

-- Finding orders placed in the last 30 days
SELECT OrderID, OrderDate
FROM dbo.Orders
WHERE OrderDate >= DATEADD(day, -30, GETDATE());

-- Extracting the year from a transaction
SELECT TransactionID, YEAR(TransactionDate) AS SalesYear
FROM dbo.Finance;

9. Subqueries and Common Table Expressions (CTEs)

When a single query isn’t enough, we nest them. As a consultant, I prefer CTEs for readability—they make your code look clean and professional.

Example of a CTE

Imagine you need to find employees whose salary is above the company average:

SQL

WITH AverageSalary AS (
    SELECT AVG(Salary) AS AvgSal
    FROM dbo.Employees
)
SELECT EmployeeName, Salary
FROM dbo.Employees, AverageSalary
WHERE Salary > AvgSal;

10. Handling NULL Values

In the real world, data is often missing. A junior dev ignores NULLs; a senior dev plans for them.

• IS NULL: Checks for missing data.
• COALESCE(): Provides a default value if data is missing.

SQL

-- Finding leads without a phone number
SELECT LeadName
FROM dbo.Leads
WHERE PhoneNumber IS NULL;

-- Replacing NULL emails with a placeholder
SELECT CustomerName, COALESCE(Email, 'No Email Provided') AS ContactEmail
FROM dbo.Customers;

Best Practices for SQL Querying

• Use Aliases: Table aliases (like Customers AS c) make long joins readable.
• Format for Humans: Use indentations and new lines. SQL doesn’t care, but your colleagues in Philadelphia will.
• Be Skeptical of SELECT *: Always specify columns to protect performance and security.
• Comment Your Logic: Use -- for quick notes. Explain the “why” behind complex filters.

Conclusion

The SELECT query is the heartbeat of data analysis. By mastering these examples—from basic retrieval to complex CTEs—you are not just “running code”; you are extracting the truth from a vast database.

You may also like the following articles:

• SQL Join Example With Where Clause

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com

How To Insert Data In SSMS

SSMS provides multiple avenues to get data into your tables. Choosing the right one depends on your specific scenario:

• Single Row Entry: For quick fixes or manual testing.
• Batch Scripts: For repeatable deployments across Dev, QA, and Production environments.
• Bulk Imports: For migrating large datasets from external sources like Excel or CSV.

Method 1: The Standard T-SQL INSERT Statement

For most developers, the INSERT INTO statement is the bread and butter of database work. It is precise, scriptable, and provides the most control over the transaction.

The Basic Syntax

The most common way to insert data is by specifying the table name, the columns you wish to populate, and the values themselves.

SQL

INSERT INTO dbo.Employees (FirstName, LastName, Email, HireDate, Salary)
VALUES ('James', 'Miller', 'james.miller@email.com', GETDATE(), 50000);

After executing the query above, I received the expected output, as shown in the screenshot below.

Why You Should Always Specify Column Names

INSERT INTO Customers VALUES (...). Don’t do this. If a colleague adds a new column to the table later, your script will break because the number of values won’t match the table schema. Always explicitly list your columns to make your code “future-proof.”

Method 2: Inserting Multiple Rows Simultaneously

You don’t need to write ten separate INSERT statements to add ten rows.

The Row Value Constructor

Since SQL Server 2008, we have been able to insert multiple rows using a single VALUES clause.

SQL

INSERT INTO dbo.Employees (FirstName, LastName, Email,HireDate, Salary)
VALUES 
    ('Smith', 'Miller', 'smith.miller@email.com', GETDATE(), 50000),
    ('grand', 'smith', 'grand.smith@email.com', GETDATE(), 60000),
    ('ley', 'chang', 'ley.chang@email.com', GETDATE(), 30000);

After executing the query above, I received the expected output, as shown in the screenshot below.

Benefits of Multi-Row Inserts:

• Performance: It reduces the overhead of multiple round-trips between the SSMS client and the SQL Server engine.
• Atomicity: If one row in the batch fails a constraint (like a duplicate primary key), the entire statement fails, ensuring you don’t end up with partial data.

Method 3: The “Edit Top 200 Rows” GUI Method

How to Use the GUI for Insertion:

1. In the Object Explorer, navigate to your database and expand the Tables folder.
2. Right-click on the desired table (e.g., dbo.Employees).
3. Select Edit Top 200 Rows.
4. A grid will open. Scroll to the very bottom to the empty row marked with an asterisk (*).
5. Type your data directly into the cells.
6. Press Enter or click away to commit the row to the database.

Check out the screenshot below for your reference.

Pro Tip: While convenient, I recommend using this only for small, non-critical updates. For production environments., always use scripts that can be peer-reviewed and saved in version control.

Method 4: Inserting Data from Another Table (INSERT INTO…SELECT)

The Syntax for Table-to-Table Insertion

You can combine an INSERT statement with a SELECT statement to migrate data dynamically.

SQL

INSERT INTO dbo.Archive_Customers (CustomerID, FirstName, LastName, Email)
SELECT CustomerID, FirstName, LastName, Email
FROM dbo.Customers
WHERE LastPurchaseDate < '2024-01-01';

Key Considerations:

• Column Mapping: Ensure the data types in the SELECT list match the destination columns in the INSERT list.
• Filtering: Use a WHERE clause to ensure you are only moving the specific subset of data you need.

Method 5: Handling Identity Columns During Insertion

Most tables in a modern US tech stack use an IDENTITY column (Auto-increment) for the Primary Key. By default, SQL Server prevents you from manually inserting a value into an identity column.

Overriding the Identity Property

If you are performing a data migration for a company and need to keep the original IDs, you must toggle the identity insert setting.

1. Turn it on: SET IDENTITY_INSERT dbo.Customers ON;
2. Run your insert: Include the ID value in your statement.
3. Turn it off: SET IDENTITY_INSERT dbo.Customers OFF;

Warning: Forgetting to turn this off can cause havoc with your application’s ability to generate new IDs later.

Method 6: Bulk Inserting Data (Importing Files)

When you are tasked with importing 50,000 leads for a marketing firm, typing them out is impossible. SSMS offers the Import and Export Wizard.

Using the Import Wizard:

1. Right-click your Database in Object Explorer.
2. Select Tasks > Import Data…
3. Choose your Data Source (e.g., Microsoft Excel or a Flat File/CSV).
4. Choose your Destination (SQL Server Native Client).
5. Map the source columns to your destination table columns.
6. Run the package immediately or save it as an SSIS package for later use.

Best Practices for Data Insertion in SSMS

1. Use Transactions for Critical Data

If you are running a script for a firm, wrap your insert in a transaction. This allows you to verify the results before “locking them in.”

SQL

BEGIN TRANSACTION;

INSERT INTO dbo.Orders (OrderDate, CustomerID, TotalAmount)
VALUES (GETDATE(), 501, 199.99);

-- Check the results first!
-- ROLLBACK TRANSACTION; -- Use this if it looks wrong
-- COMMIT TRANSACTION;   -- Use this if it looks right

2. Handle Constraints Gracefully

Ensure your data respects:

• Primary Keys: No duplicate IDs.
• Foreign Keys: The Customer must exist before you can add an Order for them.
• Check Constraints: For example, ensuring a Price column is never negative.

3. Output Your Inserted Data

Use the OUTPUT clause to immediately see the values that were generated by the server (like the new Identity ID or a default timestamp).

SQL

INSERT INTO dbo.Users (Username, Region)
OUTPUT inserted.UserID, inserted.CreatedAt
VALUES ('jdoe_nyc', 'Northeast');

Troubleshooting Common Insertion Errors

Here is how to fix the “Big Three”:

1. String or binary data would be truncated

• The Cause: You’re trying to put a 100-character name into a VARCHAR(50) column.
• The Fix: Increase the column size or trim the data before inserting.

2. Cannot insert the value NULL into column ‘X’

• The Cause: You missed a column that is marked as NOT NULL.
• The Fix: Provide a value for that column or modify the table to allow NULLs (if appropriate).

3. The INSERT statement conflicted with the FOREIGN KEY constraint

• The Cause: You are trying to reference a record in another table that doesn’t exist.
• The Fix: Insert the parent record first.

Summary of Key Shortcuts for SSMS

• F5 or Ctrl + E: Execute the current script.
• Ctrl + N: Open a new query window.
• Ctrl + Shift + R: Refresh the IntelliSense cache (helps when you’ve just added a new table).
• Ctrl + K, Ctrl + C: Comment out a block of code.

Conclusion

Inserting data in SSMS is more than just a mechanical task; it is the foundation of data management. By mastering the INSERT statement, understanding how to handle identity columns, and using the power of bulk imports, you position yourself as a capable and authoritative database professional.

You may also like the following articles:

• How To Run Query In SSMS
• How To Comment In SSMS
• SSMS 22 New Features

Bijay Kumar Sahoo

After working for more than 15 years in the Software field, especially in Microsoft technologies, I have decided to share my expert knowledge of SQL Server. Check out all the SQL Server and related database tutorials I have shared here. Most of the readers are from countries like the United States of America, the United Kingdom, New Zealand, Australia, Canada, etc. I am also a Microsoft MVP. Check out more here.

sqlserverguides.com