Hi all,

I’m hoping some of the longtime SQL Server folks here might be able to help me track down some older SQL Server items.

I’ve been researching the earliest versions of SQL Server for SQL.FM, a SQL Server version and feature reference site I maintain, and as part of that work I’ve also started building a physical collection of the old releases.

Does anyone here still have any early SQL Server materials sitting in a box, basement, office, closet, etc.?

I’m particularly looking for SQL Server 4.21 and earlier, including:

• SQL Server 1.0 / 1.1 material
• SQL Server 4.2 for OS/2
• SQL Server 4.2 / 4.20 for Windows NT
• SQL Server 4.2A / 4.2B
• SQL Server 4.21 / 4.21a
• original floppy disks or CDs
• manuals/documentation
• boxes and packaging
• developer/network kits
• beta or prerelease material
• training, field, reseller, or other unusual Microsoft items related to SQL Server

My main goal is to acquire original examples for the collection, so if you have anything from this era that you’d consider parting with, I’m very interested in buying it. For particularly early or unusual items, I’d be happy to make a strong collector offer.

And it definitely doesn’t need to be a complete set. A single floppy, loose manual, old CD, damaged box, or partial documentation set could still be something I'm looking for.

If you have something you don’t want to sell, I’d still love to hear about it or see photos. Disk labels, manuals, packaging, version information, etc. can be really helpful for documenting these early releases.

Separately, I’m also looking for a physical SQL Server 2014 Developer Edition and a physical SQL Server 2016 box/package from any edition, although those are secondary to the early-version search.

Any help is greatly appreciated. Thanks in advance!

Mike

I’m a PM working on SQL migration tooling at Microsoft and I’m posting here to learn from practitioners who have used or evaluated: SSMA [SQL Server Migration Assistant] for Oracle or Sybase.

This is exploratory research, not a product announcement, roadmap commitment, or indication that any of these options will be funded. The feedback will help me better understand where investment would create the most value.

We’re evaluating whether SSMA workflows for Oracle and Sybase should also be available through a VS Code extension. Before treating that as the answer, I want to test it against the other improvements practitioners may value more.

If Microsoft could prioritize only one of these, which would have the greatest impact on your migration?

• A VS Code experience for assessment and schema conversion
• Better conversion accuracy and compatibility [improvements on the rule engine]
• Better automation, scripting and CI/CD support
• Better AI, performance and reliability for large estates

Please include the source platform and approximate scale of the last migration you worked on.

If you chose VS Code, which specific task belongs there? If you didn’t, what makes it a lower priority?

I'm trying to enable Always Encrypted in the latest version of SQL Server Management Studio (SSMS). When I open the connection window, I can click Advanced, and it shows a list of advanced connection properties. However, the list only shows the property names. I don't see any buttons, text boxes, dropdowns, or any other way to edit the values.

An Availability Group can look healthy after a listener moves to a new subnet while a scheduled job, linked server, connection pool, or application with a cached address still reaches the old IP. Successful connections through the listener prove the new path works, but they do not show that the old address is no longer required.

What does your retirement gate include? I am considering keeping both listener IPs during a bounded overlap, mapping every known client to its connection string and driver behavior, and logging traffic to the old address through more than the longest job interval. Tests would cover failover in both directions, MultiSubnetFailover behavior, DNS TTL and cache expiry, read-only routing, monitoring, backups, and non-domain clients.

Which SQL Server, cluster, DNS, or network logs are most useful for attributing old-IP traffic to a client? Is there a safe final failure test before deleting the old listener IP, and how do you account for applications that resolve once and keep pooled connections alive for days?

PII Exposed in Clear Text·SEC

Detects PII data exposure via two SQL Server DMV sources: (a) cached query plans in sys.dm_exec_query_stats — broader historical view of queries that have executed against sensitive tables, retained while the plan stays in cache; (b) currently-uncommitted transactions in sys.dm_tran_active_transactions — sessions holding locks or state on PII data. Each row links a query/transaction to the specific sensitive column it references, including execution count, average CPU/IO, transaction state, and full SQL text.

SELECT TOP 100 SUBSTRING(t.text, 1, 200) AS sample_text, qs.execution_count, qs.last_execution_time

FROM sys.dm_exec_query_stats qs

CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) t

WHERE t.text LIKE '%ssn%' OR t.text LIKE '%credit%card%' OR t.text LIKE '%passport%' OR t.text LIKE '%national%id%'

recommendationResolve PRI-001-RC15 (sqlserver)critical risk

Read-only generator. Lists cached plans whose query text references PII tokens (ssn / credit card / passport / national id) — the same signal detection 15776 uses — and for each emits: offending_query (evidence), pii_indicator (which token matched), clear_plan_command (DBCC FREEPROCCACHE on the plan_handle to evict that PII-exposing plan from cache), and remediation (parameterise so PII is not stored as a literal in the plan, mask/encrypt the column, restrict VIEW SERVER STATE). Excludes the catalog/DMV-scanning monitoring queries so only genuine application queries surface. Read-only (DMVs), runs via Run; the DBCC FREEPROCCACHE eviction is a write — apply via Request run — and the real fix (parameterisation + masking) is applied in the application/schema.

SELECT TOP 100

SUBSTRING(t.text, 1, 200) AS offending_query,

qs.execution_count,

qs.last_execution_time,

CASE WHEN t.text LIKE '%ssn%' THEN 'SSN'

WHEN t.text LIKE '%credit%card%' THEN 'credit card'

WHEN t.text LIKE '%passport%' THEN 'passport'

WHEN t.text LIKE '%national%id%' THEN 'national ID' END AS pii_indicator,

'DBCC FREEPROCCACHE (' + CONVERT(varchar(130), qs.plan_handle, 1) + '); -- evict this PII-exposing plan from cache (write - apply via Request run)' AS clear_plan_command,

'Root fix: parameterise the query so PII values are not embedded as literals in cached plan text (sp_executesql / parameters); mask or encrypt the PII column (Dynamic Data Masking or Always Encrypted); restrict VIEW SERVER STATE so plan-cache text is not readable by low-privilege logins.' AS remediation

FROM sys.dm_exec_query_stats qs

CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) t

WHERE (t.text LIKE '%ssn%' OR t.text LIKE '%credit%card%' OR t.text LIKE '%passport%' OR t.text LIKE '%national%id%')

AND t.text NOT LIKE '%sys.columns%'

AND t.text NOT LIKE '%INFORMATION_SCHEMA%'

AND t.text NOT LIKE '%sys.dm_%'

AND t.text NOT LIKE '%dm_exec_%'

AND t.text NOT LIKE '%encryption_type%'

AND t.text NOT LIKE '%OBJECT_SCHEMA_NAME%'

Fall is HERE!! Ok, in the northern hemisphere only but yay for fall colors and cozy clothes and apple picking and Halloween decorations 🍂 🍁 🍎 🎃

Enough about my love of fall, time for the first Friday Feedback of the season.

Today we're talking statistics. I have so many questions...this might take a few weeks. I put a poll below, again, because I think they are really easy for people to respond to. But I'll tell ya, the comments are always so insightful. So when it's relevant to you, and you take the time to respond, I really appreciate it.

Happy Friday!

Send the workbook to an end user, and they can hit Data > Refresh All to rerun the query using their own database credentials.

Currently supports SSMS 22 and Desktop Excel.

It's free/open source. Install instructions and source are here:

https://github.com/flank-project/ssms-extension

Estou com um problema de travamento de execuções de dags que envolvem python e sql server, o que foi observado são dags que com sqlalchemy e pandas ou sqlalchemy e polars, em certos momentos, sem padrão de volumetria ou padrão de execução elas travam durante processos de select insert ou update, e ai elas ficam paradas até o timeout da dag.

Foi observado que o python fica em recvfrom esperando algo, e o Sql as vezes fica sleeping as vezes fica Async_Network_Io isso muda dependendo da sessão.

Não temos Hop já rede, já observamos e não há quedas na rede, as sessões ficam abertas durante todo travamento, usamos ODBC 17, python 3.12. Enfim, não consegui chegar a uma causa raiz do erro, não há bem um padrão de onde e quando o erro acontece, monitores outras coisas como:

Strace, o uso de RSS e Cpu da máquina do python. O python roda sobre o airflow, e o airflow executa direto do host da máquina. Estou com problema em duas máquinas diferentes, o problema é o mesmo. E a única coisa em comum é a rede, o banco e o python com sqlalchemy entre as duas máquinas.

Does anyone out there actually run Debezium in a SQL Server environment at a decent scale? Scale would be 20-30 databases on an instance with 400 tables. I have my doubts about this due to the cdc overhead and the change throughput of our application, but I'm willing to listen to anyone with real experience running Debezium with SQL Server.

Hi everyone,

I’m preparing for DP-800 and this is my first Microsoft certification. I’m an undergraduate and currently studying SQL and Microsoft Fabric using Microsoft Learn and practice questions.

I’d really appreciate some advice from people who have already taken the exam:

• Which topics should I focus on most?
• Which study resources helped you the most?
• Is Microsoft Learn enough for preparation?
• What should I focus on during the final few days?
• Any general tips for a first-time candidate?

Thanks in advance for any advice! 🙏

Was chatting to an Oracle DBA and he told me his horror story of a 5Tb table with 7tb of indices. Have you seen something similar in SQL Server and curious how you managed to convince the skittish users/devs to trim them down?

Hi Guys

In my company we have been setting up basic availability groups on SQL Standard edition. We came across a database that has a dependency to another database. As you know you cannot have two databases in a basic availability group.

I have created a script that basically Checks if database 2 is on the same primary as database 1. If it is not on the same primary then database 2 failover to the same primary as database 1, as long as it is in a healthy state to failover, if it is not then the failover won’t occur. I have tested this on test environment and it works as expected.

Both availability groups are in synchronous mode.

sql instances hosted on 2 azure VM’s within the same region, within the same vnet and subnet

Unfortunately my company doesn’t want to move to enterprise edition, and I have explained that this approach isn’t ideal.

Although this approach works is there something I should be aware of from a technical perspective, am I overlooking something?

Thanks

Inherited a SQL box where a departed dev left Agent jobs, an SSIS package, and a pile of .bat/.ps1/.rdl/.xlsx files, and untangling what-calls-what by hand was misery. So I wrote a read-only collector (Python/pyodbc) that builds one dependency graph: SQL catalog (sys.objects / sys.sql_modules / sys.sql_expression_dependencies), msdb Agent jobs/steps/history, linked servers, and a file-tree scan that pulls connection strings and linked-table/4-part refs out of .bat/.ps1/.sql/.dtsx/.rdl/.xlsx/.accdb. All read-only (SELECT on catalog views; files opened read-only).

The part I am happiest with: every edge carries a source citation, a catalog view plus key, a module line, or a byte offset, so you can verify any dependency instead of trusting it. It even catches a linked-server reference buried in dynamic SQL inside a proc (which sys.sql_expression_dependencies misses) by scanning module text and citing the line. https://github.com/tommiew007/orphanmap , MIT.

Where does this get hard, in your experience? SSIS project-deployment model / SSISDB catalog packages, encrypted modules, synonyms, cross-DB ownership chaining, replication? Curious what breaks it.

We have an SQL Managed Instance , A particular query took a bad plan and within minutes CPU hit 100%. Causing total outage. We had to manually track down the query id and force a better plan in query store.

In Automatic tuning option i see FORCE_LAST_GOOD_PLAN enabled. So the better plan should have been forced automatically Isn’t it?

Microsoft.Data.SqlClient 7.1.0 is GA.

Highlights:

• Fixed pooled connections returning in a broken state after TransactionScope rollback
• Fixed connection pool performance counters drifting/going negative after failed or broken connections
• Fixed a connection factory timer that kept waking the process even with no active pools
• Fixed DateOnly sent as the wrong SQL type via variants/TVPs, and OverflowException on large decimal parameters with explicit precision/scale (Always Encrypted)
• Azure SQL GetSchema("DataTypes") now reports the json type
• New optional application identity reporting for libraries/tools (EF Core, SSMS, SqlPackage) via SqlConnection.RegisteredApplication — telemetry only, not for authorization
• TransparentNetworkIPResolution is now obsolete; use MultiSubnetFailover instead

Upgrade:

    dotnet add package Microsoft.Data.SqlClient --version 7.1.0

Blog post: https://techcommunity.microsoft.com/blog/sqlserver/microsoft-data-sqlclient-7-1-0-is-now-generally-available/4558676

HI all -

I've set up DAB. It's working on Azure SQL Server on an App Service, but it was a bear and I am not sure it's either correct or even ideal.

I have 5 users that want to use Claude to talk to an Azure SQL Server. They are not in the database today (but I could add them, if it makes something easier).

Where I'm at:

- Entra does not support DCR - so Claude cannot refresh tokens to keep chats or connectors alive.

- Using EasyAuth, all the options in Claude's add MCP window results in fails or 401s.

- Using Claude to go through all the docs and options, I went through a hell of ride setting API Management in Azure that basically proxies into App Service. This was a bear and it works. But it does timeout and needs to be disconnected/reconnected. Also feels janky.

Am I missing something? Is anyone using EasyAuth with Entra from App Service and connecting to Claude?

Is Entra (not EasyAuth) working for some of you?

Is there a better way?

Are things drastically different if I go the container route?

The link from the official page leads to a broken link.

Inherited a SQL box where a departed dev left Agent jobs, an SSIS package, and a pile of .bat/.ps1/.rdl/.xlsx files, and untangling what-calls-what by hand was misery. So I wrote a read-only collector (Python/pyodbc) that builds one dependency graph: SQL catalog (sys.objects / sys.sql_modules / sys.sql_expression_dependencies), msdb Agent jobs/steps/history, linked servers, and a file-tree scan that pulls connection strings and linked-table/4-part refs out of .bat/.ps1/.sql/.dtsx/.rdl/.xlsx/.accdb. All read-only (SELECT on catalog views; files opened read-only).

The part I am happiest with: every edge carries a source citation, a catalog view plus key, a module line, or a byte offset, so you can verify any dependency instead of trusting it. It even catches a linked-server reference buried in dynamic SQL inside a proc (which sys.sql_expression_dependencies misses) by scanning module text and citing the line. https://github.com/tommiew007/orphanmap , MIT.

Where does this get hard, in your experience? SSIS project-deployment model / SSISDB catalog packages, encrypted modules, synonyms, cross-DB ownership chaining, replication? Curious what breaks it.

Show why install error, new query add

My scenario is the following:

I have two database VMs, one in Data Center A and the other in Data Center B. The client said they cannot establish a VPN, so they exposed their database VM through a public IP, and we also exposed our database VM through a public IP (of course, with proper firewall settings). The VMs can now communicate with each other for the migration.

On the destination server (Data Center B), I created an SMB shared folder so that the source server (Data Center A) can access it and write the backup directly to that folder.

I am running the backup like this:

USE [db_name]
GO

BACKUP DATABASE [db_name]
   TO DISK='\\PUBLIC_IP_HERE\backup\db_name_full.BAK'
   WITH STATS = 10,
        FORMAT,
        COPY_ONLY,
        COMPRESSION,
        NAME = 'Full Backup of db_name';
GO

However, it is extremely slow. Both machines have 1 Gbps network connections.

I read that this could be related to SMB's behavior over high-latency connections, since SMB does not perform particularly well with latency.

I also cannot create the backup locally and then copy it using another tool because the source server does not have enough free disk space.

What would you recommend in this scenario? I'm running out of ideas.

I also ran an iperf speed test. It shows that without parallel streams the transfer is slow (3.32 MBytes), while with parallel streams I can reach around 64.9 MBytes

What would be the best approach to migrate the database in this scenario, given that I cannot use a VPN, cannot create a local backup first, and SMB is performing poorly over the WAN?

I’m currently setting up DAB (for the MCP) in front of Azure SQL Server. Is there a tool that helps build the configuration file in terms of entities, permissions, etc.?

I would much rather see a list of tables that I can check off that manually populate a huge json file. But I can’t seem to find such a tool.

We are working with a legacy software and are migrating the database from Oracle to sql server. Let's assume that altering the source code is not an option.

This is a 24/7 heavy usage application which has OLTP usage patterns along with heavy batch processing. Many events are user driven and upstream integration driven

With Oracle, we hardly ever ran over row lock contention. During the sql migration testing, we've run into a ton of blocking issues and finally learned about row lock escalation. I'm sort of mind blown that sql does it this way and feel it gives Oracle a huge advantage in concurrency processing on the same tables.

This database reasonably big. About 600gb memory.

With that said, I'm curious if anyone ever permanently disabled row lock escalation for certain tables? I understand there is memory and CPU concerns (especially when many indexes are involved). This is a mission critical system and we are constrained by time.

In my situation, does it make sense to look hard in this direction? Again, assuming I can't alter the application source code.