.Net

External Article

Use SqlBulkCopy to Quickly Load Data from your Client to SQL Server

  • Article

The .NET Framework 2.0 introduces a very handy new class in the System.Data.SqlClient namespace called SqlBulkCopy that makes it very easy and efficient to copy large amounts of data from your .NET applications to a SQL Server database. You can even use this class to write a short .NET application that can serve as a "middleman" to move data between database servers.

2007-05-09

3,525 reads

Technical Article

Part 1: Developing an object oriented database in less than 140 lines

  • Article

One of the best benefits of the .NET Framework over lower level programming is that it enables developers to create very complex, custom solutions, without writing low-level code. Zach Smith explores how you could take advantage of the built-in .NET Framework functionality to develop a simple object oriented database in less than 140 lines of code.

2007-01-19

4,211 reads

Blogs

Microsoft Purview data governance best practices

By

Microsoft Purview can be the best data governance tool in the world, but it...

AI and Data Engineering on the Edge: The Good, the Bad, and the Overhyped

By

Running AI and data pipelines on the edge instead of the cloud has gone...

UNION vs UNIONALL: #SQLNewBlogger

By

While writing another post I realized my UNION query didn’t work as one might...

Read the latest Blogs

Forums

Replacing Maintenance tasks now using SSMS 22 - what to do with File operations

By terry999

Unfortunately I'm using SSMS 22. It didn't come with maintenance plans by default. I...

Secure Cached Plans

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Secure Cached Plans

Complex Data Processing with dbt Python Models: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Complex Data Processing with dbt...

Visit the forum

Question of the Day

Secure Cached Plans

The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?

See possible answers