While cleaning up a project, I needed a list of all the views in the database. SQL Server Management Studio provides a menu for this, but I needed a way to get this data in text form. In SQL Server, you can get this information from the INFORMATION_SCHEMA.TABLES view.
The last update of VS Code has an annoying side effect: When you start typing in a file, the whole content moves one line down to give space for three dots on top of the editor:
Sooner or later we all run into this situation with Git: We committed a change that should not be committed and we only found that out after we hit commit in out IDE. If we did not yet push this change to our centralised repository, we can use this command to undo our mistake:
With SQL Server 2016 SP1 came a small but helpful new statement to create views: OR ALTER. If you add this to the create script for a view, SQL Server will figure out if it should run the CREATE or the ALTER statement:
I am a big fan of Octopus Deploy. This tool helps us to deploy our applications with ease and in a reliable way. In fact, it is so easy that I always forget the few important settings you need to have in place so that Octopus can do its magic.
We are currently migrating our larger databases to SQL Server 2019. While the migration went smoothly for the small databases, there was an unexpected problem with the last server: the backup was incredibly slow.
The first larger database we moved to the new server took 10 times longer to back up than on the old server (50 minutes instead of 5). If the backup time would proportionally increase with the database size, our biggest database would use the whole maintenance window just for the backup task. We had to fix this problem immediately.
Synology builds great NAS (Network Attached Storage) devices. For 9 years my DS1512+ worked like a charm. It still works, but since it reached the end of support it is time to move to another device – the DS1618+. The big question I had was how do I move the files from one NAS to the other? As it turns out, there is a surprisingly simple yet robust way to do that.
Visual Studio 2022 offers so many new features that we easily overlook how existing features have been improved. In today's post, I like to point out how "Paste JSON as Classes" got better and better. Pasting XML or JSON as classes exists since Visual Studio 2017. However, in Visual Studio 2022 you can work with complex object graphs that earlier Visual Studios could not handle.
For some problems you need a sequence of numbers. In Python I would use the range() function, while in C# the method Enumerable.Range() gives us what we need. We must specify the starting point and how many numbers we want:
GitHub provides a simple issue tracker with a minimalist user interface. While this minimalism is often an advantage, it does not help the user report the important details to reproduce a bug:
