Here is how to work with DateOnly and TimeOnly with a SqlClient.SqlDataReader. https://t.co/trsJhCHacI

SqlClient working with Enum https://t.co/aWHFm3pP9G

SqlClient data reader extensions to read DateOnly and TimeOnly. #csharp #sqlclient

More Dapper.AOT progress: DbBatch, with zero consumer code changes! (ignore the large alloc - rotating sub-batch window is in progress; tested here on Npgsql today - SqlClient gets DbBatch support in the next public drop; /cc @shayrojansky)

Creating a custom GPT with ChatGPT can be extremely beneficial. For example, a developer wants to convert from using SqlClient operations to Dapper and will be converting many of these. Using a custom GPT allows a developer to skip prompting and instead paste code in and go. In

Güzel bir karşılaştırma yaptım. "OleDB vs SQLClient" Logo Tiger uygulamasında yapılan bir işlemi SQL profiler ile kaydedip aynı işlemleri bir .net framework windows uygulaması ile Ado. net üzerinde hem OleDB hem de SQLClient protokolleri ile çalıştırdım. Sonuçları çok çarpıcı.

Can you repeat with #EFCore or #Dapper or any other #SqlClient? #dotner #csharp

Struggling to trace what’s happening across your .NET app? Here’s a simple OpenTelemetry setup I use in every project: - ASP .NET Core instrumentation - HttpClient instrumentation - EF Core instrumentation - Redis instrumentation - Npgsql (or SqlClient) This gives you rich,

If you suffer under slow blob reads with SqlClient, try out 7.0 preview 2! #dotnet #sqlserver

Steal my simple OpenTelemtry tracing setup for .NET applications: - ASP .NET Core instrumentation - HttpClient instrumentation - EF Core instrumentation - Redis instrumentation - Npgsql (or SqlClient) This alone will give you very detailed traces.

Please help the community contributor who fixed slow async processing with large data in the SqlClient driver - just add this to your SQL data access library: <PackageReference Include=" https://t.co/lkm75UGvzO.SqlClient" Version="6.1.0-preview2.25178.5" />

@SimonCropp LITERALLY just had this exact conversation with my teammate because we have security scanning that showed the vulnerable Azure.Identity. It's mindboggling 😭😭 Not to mention the inconsistencies between the EFCore transitive deps down to the SqlClient one. Frustration++;

I really wish there were some built-in metrics for SqlClient or Entity Framework Core, but in lieu of that I built some of my own using our stupid repositories that I want to get rid of

This is something I'm working on right now. The ability to have something simple to add: * AspNetCore * Http * SqlClient * Otlp Exporter * Setup the Service name * Setup Tracing, Logs, Metrics

huh? V6.0.0 of Microsoft Data SqlClient has been unlisted

Microsoft sent me an urgent message I have to update DataJuggler.Blazor.Components. A transitive package references Microsofot.Identity.Client. After looking in 3 packages, the source is Microsoft. Data.SqlCLient, which hasn't been updated. Urgent for me but not for thee?

Last week NuGet removed two versions of DataJuggler.Blazor.Components, because they said it contained a vulnerable reference to Microsoft.Identity.Client. The culprit was Microsoft. Data.SqlClient. I told them about after they removed my package. Today they wrote me an apology

ahhhh finally got these dumb SqlClient traces sorted in this Aspire app

Follow me for .NET Data news, tools & links - Azure SQL, EF Core, SqlClient, DacFX and more.. - and help me get closer to 10K followers. Feel free to RT 🙏