Lmst

New blog post:
Which covers creating SQL Server 2025 containers in #Podman, #Qnap Container Station, #sqlcmd, and restoring a sample database to test the new version.
#sqlserver #sqldba #microsoftsqlserver #mssqlserver #mssql #mssqldba #sql #container #docker
https://vladdba.com/2025/05/30/sql-server-2025-container/

After extensive analysis, it seems that sqlcmd doesn't manage buffers and transactions properly, and it lead to the error, when there's lot's of data. I wrote my own alternateive program for #SQLCMD using #Python, and now the import was successful. So it turns out that sqlcmd code is just bit bad, and someone had to write better alternative. To be honest, some of the individual insert statements were up to 8 megabytes per row. #SQL

I created #SQL #dump file using #SSMS. Yet interestingly when running it with #sqlcmd, it says that it hasn't been properly #escaped. - I'll investigate it closer, but it looks interesting. Why it wouldn't be properly escaped? That's really confusing. But I'll dig into it. The dump file just just a hundreds of gigabytes which makes it bit harder.

Little #SQL Server Tricks: Export CSV With #sqlcmd

https://improveandrepeat.com/2024/01/little-sql-server-tricks-export-csv-with-sqlcmd/

Why does #Microsoft #SQLServerManagementStudio pretend to take a long time "creating a script" when requesting a view definition? The definition is stored in the information_schema. Using #sqlcmd we can request it, and it pops up instantly. What does #SSMS think its doing?