r/SQLServer

I am having an issue with the SQL Server 2025 starting when using an sMSA account that is 15 characters. With the 2 letter NETBIOS domain name and the $, it's 19 characters, similar to this:

AB\serviceactnm-sq$

If I use 1 less character, the MSSQLSERVER service will start, but the problem is the above never had any issue in any other version of SQL server and it doesn't exceed the NETBIOS password character limits. I even tried updating to the latest CU6 released in June with no luck.

This definitely sounds like a bug or does anyone know if Microsoft had some other reasoning behind it?

If you haven't seen it, Internals Viewer is a free tool for visualizing SQL Server internals, including allocations, pages, records, and indexes. It can run on a live database, or open a detached .mdf file.

I've been tinkering with it on and off for a long time. I was looking into locks recently and thought it would be useful to see if I could integrate some sort of visualization into the app. One thing led to another which led to something different yet hopefully useful!

The new query trace feature allows you to run a query and see the actual page I/O connected to the query plan on a timeline. Combined with the existing allocation and index visualizations you can see how a query is scanning or seeking and also how things like hash joins and loop joins are actually running from the perspective of the storage engine and how data streams through the operators.

The app is purely for educational purposes. I created it to help my understanding after reading blogs and books on internals so if you're interested in that area the tracing will hopefully be of use.

An upcoming release will show data modifications captured during the trace from the transaction log to show what a query is doing on a log entry basis on a page/row level.

It's available for free via the Microsoft Store or Github

(...but don't use it on a production database)

I'm studying SQL and am currently on the lesson about subqueries, but I just can't seem to wrap my head around it.

I'm struggling to get the different types of subqueries—and when to use each one—to stick in my mind.

Does anyone have any study materials on this? Maybe a YouTube video tutorial?

THANKS!

Looking for a very experienced SQL Server DBA who has deep experience with Database configuration for tuning and also SQL Queries tuning

Our org is rolling out Claude to all our devs. Your (and my) feelings in AI aside I'm part of the team coordinating the roll out. I discovered this week you can create org wide skills that detect anti patterns, non performant SQL, etc. You can choose to block it outright, allow the code but talk to the dev about it, or just log it.

Love the idea overall. Here's some of the ideas I came up with

*select * instead of explicit columns

*-non-sargable clauses, espwehere where or functions on indexes columns

*loops instead of batch queries /selects / inserts

-cursors where bulk selects or inserts would work (really cursors anywhere)

-implicit data type conversions causing scans instead of indexes

-using functions in where clauses

-using scalar functions in general

-unnecessary left joins and nested subqueries where a cte would be appropriate

 

any other ideas youd add?

Welcome to the open thread for r/SQLServer members!

This is your space to share what you’re working on, compare notes, offer feedback, or simply lurk and soak it all in - whether it’s a new project, a feature you’re exploring, or something you just launched and are proud of (yes, humble brags are encouraged!).

It doesn’t have to be polished or perfect. This thread is for the in-progress, the “I can’t believe I got it to work,” and the “I’m still figuring it out.”

So, what are you working on this month?

---

Want to help shape the future of SQL Server? Join the SQL User Panel and share your feedback directly with the team!

Hi all,

Thigh-deep in SQL licensing docs and can’t find a definitive answer on something that I’m sure is a loophole Microsoft wouldn’t leave open…

Looking at an ERP app that uses SQL as its database.

The app’s server would run on a Windows Server 2022 VM on Hyper-V.
The client app would be installed on a single Server 2022 Remote Desktop Session Host.
Users would access the application via the session host using RemoteApp.

For SQL Standard 2022 we have the option of per core or server + CAL licensing.

For the server + CAL option we can then order user or device CALs.

Device CALs are described as being valid for a single device used by any number of users.

Question - does this apply to a Remote Desktop Session Host server?

That is, assuming we’ve purchased the required number of RDS CALs, is just one SQL Device CAL valid for the RDS server, given that it is the only device accessing the SQL database?

Thanks!

Hi there, we have a US based client that is wanted to onboard a large office in Asia. Initially, they were intending on them using the same apps, DB, etc that are in US East, but they have concerns on latency. We did some testing and the latency isn't too bad, 200ms or so, but I guess enough that they don't want to proceed that way.

We have done replication across regions in the past and frankly, it went very poorly. I just don't think our team has the expertise in that kind of area, so I am heavily discouraging it.

My not-thoroughly-thought-out suggestion is that each region has their own database and apps, we start the Asia one as a clone from .bak from the US one. We would then do a nightly sync (they do not need real-time) pushing from Australia to US. It would not be a significant amount of data, mostly CRM-type stuff.

They do not anticipate pushing data from DC to Australia, but as always, that's certainly a possibility at some point.

My preference would be a read-only secondary in Australia, with writes going to the US database, but our application does not currently support that.

Thoughts? Is this is a decent idea, a horrible idea, or is there a much better idea?

I'm a fresher trying to understand what SQL skills are expected in a real data analyst role.

For those with 3–4 years of experience:

How advanced is the SQL you write day to day?

What kinds of business questions or requests do you typically solve using SQL?

Which SQL concepts do you use most often, and which ones are rarely used?

I'd love to hear some real-world examples of the tasks you work on.

What are the pros of using SSMS over other query tools? I currently use Toad Data Point 6.0 (TDD) and I use primarily 2 connections; SQL Server or Oracle. The license for TDD is about to expire. I believe my company is working on renewing the license but I am wondering if this is a good opportunity to start learning and working with SSMS instead.

I would say I have an intermediate understanding of SQL but all the "serious" and more advanced analysts use SSMS. What does SSMS do or have that only it offers?

Welcome to the monthly job thread!

Posting a job or opportunity? Include:

• Role title and description
• Location or remote/hybrid status
• Company or client context
• Direct application link

Looking for work? Share your skills, experience level, and what you're looking for.

Rules:

• One top-level comment per opportunity
• No "DM me" or link-free posts — include a direct, verifiable link
• Scam or misleading comments will be removed and may result in a ban

I want to know: I'm currently using an Azure Windows VM and SQL Server 2022 Web Edition. I'm planning to migrate to a Contabo VPS Server. The issue is that they don't have SQL 2022. They have only SQL 2019.

On my current server, I have 3 applications running on the LIVE version and using 3 databases on the server.

Since restoring a backup into the backward version is difficult, If I use SQL 2022 Developer version be an issue? I know that version is only for development, not for live databases. But until Contabo provides the SQL 2022 version, can I use the developer version? Is anyone using the developer version for their live work?

SELECT

`CONNECTIONPROPERTY('local_net_address') AS local_net_address` 

`, CONNECTIONPROPERTY('client_net_address') AS client_net_address` 

`, CONNECTIONPROPERTY('net_transport') AS net_transport`

`, CONNECTIONPROPERTY('protocol_type') AS protocol_type`

`, CONNECTIONPROPERTY('auth_scheme') AS auth_scheme`

`, CONNECTIONPROPERTY('local_tcp_port') AS local_tcp_port`

When I run this, it shows null for local_net_address , <local machine> for client_net_address, and null for local_tcp_port. This doesn't tell me the IP address. Right now, I have an express app running on the same machine that needs to know the IP address where SQL lives. How do I query the IP address correctly?

First Friday Feedback about Query Store 🎉

This week I have a poll about whether you'd be interested in having the max size (MAX_STORAGE_SIZE_MB) of Query Store managed for you.

The default size for SQL 2019 and higher and the SQL dbs (Azure and Fabric) is 1GB.

The max size for SQL dbs is 10GB; there is no max for box (but remember, just because you can, doesn't mean you should...)

I used to tell customers start with something like 2GB or 4GB, and monitor from there. But maybe we should figure out the size and manage it for you? Bonus internet points if you add a comment with additional input or reasoning about your response.

View Poll

I am making a data bridge that will pull down a few hundred rows every hour from a rate limited server to our local sql server for reporting and other daily use stuff. I obviously have to have a good stable place to put this thing. Would putting it on the same server as the sql instance speed up everything because it doesn't have to traverse the network more, or would it potentially slow it down as it uses more CPU cycles?

Hi there,

First off - aplogies if this is the wrong sub to post this question. If it is, please let me know where a good place would be.

I'm tinkering with the idea of breaking into the SQL world as a career. I was wondering how the job market is for SQL / DBA's is currently? Does entry level still exist? Any places (online and low cost/free preferrably) that anyone would recommend as a starting point? A little about my background:

I've worked in IT for 20+ years, mostly on the network/systems administration and engineering side. I've built and installed more SQL servers than I can count (just never touched or managed the actual SQL side of it) and am familiar with it how works both as itself and as a backend interacting with a front end. A few years back I took a 6 month coding boot camp and of all the languages I learned, SQL was my favorite and the one I actually viewed as (for lack of a better word) "fun". I enjoyed being tasked with "here are several tables, and we want to present data from the following columns from the following tables in the following format" (generically speaking).

Admittedly it's been quite a good while since I've tinkered with it so that's why I'm here. Hoping to get some advice/pointers of decent resources that will help me starting dipping my toes back in so I can start working toward moving away from SysAdmin work to DBA work. Thanks in advance for any direction/pointers/advice anyone is willing to provide.

Posting this here because there are many of you I suspect who have had to migrate from Access to SQL Server, or were forced to support it as "the database guy".

But then again, job security I guess?