A Fine Slice Of SQL Server
Issue
SQL Server allows blank column names in tables, but this causes the following error when scaffolding:Â
The string argument 'originalIdentifier' cannot be empty.Workarounds
– Use EF Core Power Tools, which contains a fix for this. (Fix will also be in EF Core 6.0)
– Rename the column 🙂
Click through for several more issues and solutions in this vein.
Comments closedMohammad Darab shows off a tool to monitor the Kubernetes cluster driving a Big Data Cluster:
I don’t recall how I came across this Kubernetes IDE called Lens, but all I know is it’s cool as hec! It connects to a Kubernetes cluster (using the kube config file) and gives you an in depth view of all the different Kubernetes objects, their associated yaml files, health/metrics, etc. In this blog post I will show you how we can look into a Big Data Cluster’s Kubernetes infrastructure using Lens.
Click through for instructions on installation, as well as how to use the product.
Comments closedGrant Fritchey reviews a product which attempts to repair corrupted SQL Server databases:
Let’s start with the most important piece of information you need: it works.
The software itself is really simple to use and just does what you need, repairs your corrupted SQL Server instance. On that alone, I can recommend the tool.
However, there are a few gotchas I ran into along the way. Mostly, little stuff. It’s things a little polish in the UI and some clean up around language could help out. Don’t get me wrong, I’m happy with this software. It worked. It’s just how it works that we should talk about.
Click through for Grant’s full review.
Comments closedMax Trinidad has a public service announcement for us:
Have you installed any of the .NET Tools? Such as “.NET Interactive” and “PowerShell Global“, then you’ll need to remember, to update these tools manually.
These tools give you the ability to use create Jupyter Notebook using Python Kernel but also with C#, F#, and PowerShell 7 kernels.
Read on to see how to check if you need to update either of these.
Comments closedMicrosoft.Data.SqlClient version 2 has just been released. This library is the latest and greatest .NET client driver for SQL Server and Azure SQL Database – and will be used by EF Core 5. In addition to a number of new features (which I blogged about earlier), this major version release also includes a number of breaking changes.
Click through for the list.
Comments closedJason Hall gives us a bit of history:
Greg saw a need in his own work, and I was seeing a need in the field with our customers, for a way to go beyond identifying high-impact queries. DBAs and developers needed a way to tune queries surfaced by SentryOne SQL Sentry’s Top SQL without fiddling with a lot of extra tools to get there. We were already building integration with SQL Server Management Studio (SSMS), which included graphical query plans, so the original thought was to extend that integration from SentryOne with a link that opened plans in SSMS from Top SQL in SQL Sentry.
It seemed like an elegant solution that would allow us to reuse some code, but it wasn’t long before Brooke Philpott discovered that we wouldn’t be able to get what we needed this way. That particular part of SSMS wasn’t exposed to us in the manner we needed. Par for the course, we weren’t going to let that stop us from filling the need. Greg and Brooke dug into the problem to discover a mix of documentation, flow controls, and ingenuity that would provide the foundation for building our own query plan visuals.
Read on for the story and a bit about how the product has morphed through the years.
Comments closedAlan Yu announces the general availability of mssql-cli outside of Windows:
We are excited to announce that mssql-cli is now generally available on macOS and Linux.
mssql-cli is an open source and cross-platform command-line tool (CLI) to manage SQL Server on-prem and on the cloud. We are a proud member of the dbcli family of open source command line tools to manage relational databases.
If you are a user of sqlcmd, you will love the interactive and modern design components in mssql-cli. With this release, you will also be able to use mssql-cli in non-interactive scenarios such as scripting and automation. Read on to learn more about how mssql-cli will help improve your productivity through a modern CLI experience.
If you love the command line (or simply need to SSH into a box from time to time), give this product a try.
Comments closedDave Bland shows us the Poor SQL formatter for SQL Server Management Studio:
So what is PoorSQL Formatter? Well, as you probably know, formatting is very important when writing T-SQL code. While we try to format our code as we write it, sometimes the code we need to review was written by someone else and maybe doesn’t follow formatting standards. This is where PoorSQL Formatter will come in handy. It will help us take the poorly written code and format it in a manner that is more in line with T-SQL formatting best practices. The best part, it will do the formatting in seconds.
I’ve used that website many a time. It’s not as detailed as I want it to be, but if you just need a quick and dirty way to format a query so that it’s understandable, this does the trick.
Comments closedJess Pomfret walks us through the basics of tSQLt:
Getting started with tSQLt is really easy-Â you download a zip file, unzip the contents and then run the tSQLt.class.sql script against your development database.
There are a couple of requirements, including CLR integration must be enabled and your database must be set to trustworthy. These could open up some security considerations, but for my development environment it’s no issue.
This is where I’d say putting the database in a container would be extremely helpful, as then you can destroy it afterward. I’m not sure if that’d work, as SQL Server on Linux doesn’t support unsafe or external access assemblies (and I’m not sure what tSQLt requires there).
Comments closedGianluca Sartori takes us through workload replay ability in WorkloadTools:
One of the features I was asked to implement for WorkloadTools is the ability to replay commands to a database name different from the one recorded in the source workload.
This is something that I had been planning to implement for a while and it totally makes sense. Usually, you have two identical environments for the workload capture and replay, both with the same databases. Sometimes it makes sense to have two different databases as the source and target for the workload, for some particular reasons: resources constraints, ease of testing and so on.
WorkloadTools now supports replaying commands to a different database, using theÂ
DatabaseMapÂproperty of theÂReplayConsumer.
Setting this up is pretty simple, though Gianluca does lay out a caveat.
Comments closed