A Fine Slice Of SQL Server
Ed Elliott has some code for us:
I have just finished an update for the spark connect dotnet lib that contains the
DeltaTableimplementation so that we can now use .NET to maintain delta tables, over and above what we get out of the box by usingDataFrame.Write.Format("delta"), this is an example of how to use the delta api from .NET:
Click through for the example, and you can learn more about Spark Connect from the Spark website and Ed has a .NET client for the task.
Comments closedThis post, Part 2 in a series of two, looks at styling and deploying the Observable Framework app we built in Part 1. Codeblocks with burgundy backgrounds refer to specifc tagged commits in the accompanying GitHub repositiory.
Part 1 involved converting an existing R-Shiny app to Observable Framework. Read on for this part.
Comments closedSebastiao Pereira loads a PDF:
PDF forms are widely used for data collection, document processing, and digital workflows due to their versatility and consistency across different platforms and devices. They are essential in various industries, including healthcare, education, finance, government, and business. How do you retrieve data from PDF forms and insert into a SQL Server database table?
Read on for an answer using Visual Basic, which is a name I haven’t heard in quite some time.
Comments closedEd Elliott has an update for us:
There have been quite a few changes in the last couple of months and I just wanted to give a quick update on the current state of the project. In terms of usage I am starting to hear from people using the library and submitting pr’s and requests so although usage is pretty low (which is expected from the fact that the Microsoft supported version usage wasn’t very high) it is growing which is interesting.
Read on for thoughts on production readiness, support for Spark 4.0, a couple of other updates, and some future plans.
Comments closedSebastiao Pereira solves a problem:
Report Viewer was originally developed for the .NET Framework. As the industry shifts towards .NET Core, developers who have traditionally relied on this tool have faced challenges displaying reports within their applications due to compatibility issues. Is it possible to display a report from SQL Server Reporting Services (SSRS) in a .Net Core Application?
Click through for the answer. As a quick note, we had .NET Core, but then Microsoft renamed it to .NET with .NET 6, so instead we have to differentiate .NET Framework (Windows-only, heavy SDK) with .NET (nee .NET Core, cross-platform, less heavy). I’d rate Sebastiao’s solution a workaround, but one that I doubt Microsoft will ever provide a better solution for, given the heavy de-emphasis on Reporting Services over the past several years.
Comments closedAjay Jajoo tells us what’s new:
One of the standout features of .NET 9 is its focus on performance. With numerous optimizations across the runtime and libraries, applications can expect faster execution times and reduced memory usage. This is particularly beneficial for high-load applications, making .NET 9 an ideal choice for cloud-based solutions.
.NET 9 brings various performance optimizations, including improvements in garbage collection and just-in-time (JIT) compilation.
If you work at all with C#, you’ll see some quality of life improvements in .NET 9. But given Microsoft’s policy around short-term and long-term releases, you might wait until .NET 10 in many corporate environments to see them.
Comments closedWe are using Microsoft Fabric for our analytical data platform. The data is hosted in a warehouse and modeled in a star schema. Using the GraphQL API for Fabric, we are exposing it to end users, and for some reports, we want to join data together. Is this possible in a GraphQL query?
Read on for Koen’s solution to this issue.
Comments closedEd Elliott has an update for us:
I recently published the latest version of the Spark Connect Dotnet library which includes support for the new
Variantdata type in Apache Spark 4.0 here. One of the new features of Spark 4.0 is theVariantdata type which is a faster way of processing Json data (see here).
Click through to see how it all works.
Comments closedDavid Engel has an announcement:
We announced Microsoft.Data.SqlClient in the first half of 2019 and shipped the first stable package later that year. That release coincided with .NET Core 3.0. We’ve been developing Microsoft.Data.SqlClient in the dotnet/SqlClient repo since that time, over the last five years. It’s now time to start the deprecation process for the System.Data.SqlClient package. We plan to take a staged process to deprecation, with the intent to align support changes and associated code transition activities between these libraries to natural migration points between .NET major versions.
I haven’t used System.Data.SqlClient in a while, so I’m not sure how much is in that library that isn’t in Microsoft.Data.SqlClient.
Comments closedJustin Bird builds a script task:
There are several dedicated script tasks that can be used for different purposes, some of the tasks have shortcut tasks which require much less input and are arguably easier to read. In the examples below, I have included the required inputs needed to run the scripts but in most cases, other optional inputs are available.
This looks pretty similar to the way you’d do it in GitHub Actions workflows as well—no surprise there, considering that the same group of people who built pipelines in ADO handled Actions in GitHub.
Comments closed