way0utwest

It's that lots of db people don't understand anything about VCS period. They don't use them. (it's my piece)

Thank you (it's my piece)

In the world I work in, which is lots of DBAs/sysadmins/db developers, lots don't do anything with VCS when working in databases.

To be fair, lots of developers who make/need database changes still email those to DBAs/sysadmins.

I work for the company that owns/developers Flyway, so I didn't include it in here.

However, for DBAs, they often are doing ad hoc stuff and there is a bit of overhead for FW/LB that they may not want. This is part of a series, just getting people comfortable with tracking their work.

In most cases. However, some changes, such as adding the column and needing to manipulate data (populate nulls, transforms, etc.) could still cause locking.

This really comes down to knowing the boundaries of what changes could cause timeouts and working around them as best you can. However, some edge cases could cause downtime.

Perhaps. There are tons of SQL Server sites and articles to provide information and details the docs lack.

Plus, the MS docs are now on Github and we can submit PRs to correct and expand things.

What support are you looking for? SQL Server on Linux, is for the most part, SQL Server. Django support for SQL Server should be roughly the same on Windows and Linux, they're just client apps.

All my testing, which is inherently limited to the things I look at, show that apps seamlessly port over from Windows to Linux, unless they're doing something in the file system, or have complexities with SQL Agent and other subsystems. Maybe of the Agent limitations have been removed, I just haven't retested.

MS supports Linux the same as Windows, with lots of their systems people having spent the last year+ learning about the differences between Windows and Linux.

Are they all going to be experts on client interactions? No, but they should be able to provide support in most cases.