<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alex Keh on Medium]]></title>
        <description><![CDATA[Stories by Alex Keh on Medium]]></description>
        <link>https://medium.com/@alex.keh?source=rss-6ed071550929------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*Je8jGnRUmvj1GcRfT__XiQ.jpeg</url>
            <title>Stories by Alex Keh on Medium</title>
            <link>https://medium.com/@alex.keh?source=rss-6ed071550929------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:22:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alex.keh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Announcing ODP.NET Support for .NET 11]]></title>
            <link>https://medium.com/@alex.keh/announcing-odp-net-support-for-net-11-021ca086524f?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/021ca086524f</guid>
            <category><![CDATA[oracle-ai-database]]></category>
            <category><![CDATA[odpnet]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[dotnet-11]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 01:09:43 GMT</pubDate>
            <atom:updated>2026-11-17T01:09:43.479Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*mCCOc3CISI3uyea9rdRJBQ.png" /><figcaption>Oracle Database supports .NET 11</figcaption></figure><p>ODP.NET Core 23.26.401 is now available and formally supports the .NET 11 runtime. <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/23.26.401">Download ODP.NET Core 23.26.401</a> from NuGet to connect your .NET 11 applications to Oracle AI Database.</p><p>Let me describe the new features supported.</p><h3>Runtime Async</h3><p>.NET 11 introduces Runtime Async, which treats asynchronous methods as a first-class runtime concept rather than relying solely on the classic compile-time async model. The runtime now manages the async state machine instead of the compiler. This can improve performance and reduce overhead by eliminating some state-machine scaffolding. It can also produce cleaner stack traces and simplify debugging. ODP.NET can take advantage of these benefits in its async use.</p><p>For third-party libraries such as ODP.NET, Runtime Async remains in preview. To enable it in .NET 11, add this feature property to your project file:</p><pre>&lt;PropertyGroup&gt; <br> &lt;TargetFramework&gt;net11.0&lt;/TargetFramework&gt; <br> &lt;Features&gt;$(Features);runtime-async=on&lt;/Features&gt; <br>&lt;/PropertyGroup&gt;</pre><h3>More Accurate Numeric Conversions</h3><p>Starting <strong>with</strong> .NET 11, conversions among Decimal, float, and double now produce correctly rounded results. Previously, these conversions could truncate values, round through intermediate values, or discard significant digits.</p><p>ODP.NET also follows these updated conversion rules for greater accuracy. The affected members include:</p><ul><li>OracleDecimal constructors</li><li>OracleIntervalDS constructors</li><li>OracleTimeStamp.AddSeconds method</li></ul><p>Learn more about the new release in the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/index.html">ODP.NET 26ai documentation</a>.</p><h3>Coming Soon: Entity Framework Core 11</h3><p>Oracle plans to support EF Core 11 in the coming weeks. Stay tuned! I will cover this in an upcoming blog post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=021ca086524f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ODP.NET SQL Scripting and the Deep Data Security End-User Security Context Provider]]></title>
            <link>https://medium.com/oracledevs/odp-net-sql-scripting-and-the-deep-data-security-end-user-security-context-provider-b31c59aedef1?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/b31c59aedef1</guid>
            <category><![CDATA[opentelemetry]]></category>
            <category><![CDATA[aspnetcore]]></category>
            <category><![CDATA[sql-scripting]]></category>
            <category><![CDATA[deep-data-security]]></category>
            <category><![CDATA[odpnet]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 21:50:12 GMT</pubDate>
            <atom:updated>2026-11-09T21:10:59.784Z</atom:updated>
            <content:encoded><![CDATA[<h4>ODP.NET 23.26.4 brings production ready SQL scripting, stronger application security, updated monitoring, and cleaner pooled sessions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A-ODzSJuDm0hfXPWpNv7nw.png" /></figure><h3>Key Takeaways</h3><ul><li>.NET applications can now run Oracle SQL and PL/SQL scripts from files, cloud storage, REST APIs, or other stream based sources.</li><li>A new ASP.NET Core provider automatically applies Deep Data Security context with minimal application changes.</li><li>ODP.NET Deep Data Security no longer requires a human user identity, supporting services and AI agents that operate independently.</li><li>The release also adds current OpenTelemetry conventions, session state resets, and performance improvements for EF Core and asynchronous operations.</li></ul><h3>Introduction</h3><p>I’m proud to announce that <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/23.26.400">ODP.NET 23.26.4</a> is now available on NuGet with these features:</p><ul><li>Execute SQL and PL/SQL scripts from .NET</li><li>Use the Deep Data Security end-user security context provider with ASP.NET Core</li><li>Configure an optional user identity for Deep Data Security</li><li>Incorporate new ODP.NET OpenTelemetry attribute tags and semantic conventions</li><li>Reset each database session to the original application state</li><li>Benefit from ODP.NET performance improvements</li></ul><p>Let’s explore these enhancements.</p><h3>SQL Script Execution for .NET</h3><p>As more workloads move to cloud environments and AI agents administer them, organizations need programmatic interfaces for executing SQL and PL/SQL scripts. Command-line tools were generally designed for human operators with privileged access to on-premises databases. AI workloads instead rely on automated processes with least-privilege access, while cloud environments often restrict direct administrative access to database resources.</p><p>ODP.NET Core SQL script execution addresses these requirements. .NET applications can execute SQL and PL/SQL commands programmatically from a stream. They can bind script parameters as JSON and receive results as a JSON string.</p><p>Now in production with ODP.NET 23.26.4, this capability helps .NET applications apply and automate database changes. Scripts can come from files, blob storage, REST APIs, or any other source that can be read by a .NET StreamReader.</p><p>At runtime, an application passes a StreamReader to the OracleCommand.ExecuteStatements extension method. Parameters can be supplied as a JSON document through OracleCommand.SetParametersForExecuteStatements or through the OracleCommand.Parameters collection.</p><p>I described <a href="https://medium.com/@alex.keh/run-oracle-sql-scripts-in-net-bd4e950ff104">ODP.NET SQL script execution in a previous blog post</a> if you want more details.</p><p>In short, this feature gives .NET developers and DevOps teams a flexible scripting tool for modern cloud and AI applications.</p><h3>Deep Data Security: End-User Security Context Provider in ASP.NET Core</h3><p>The new ODP.NET Deep Data Security (DeepSec) provider model lets ASP.NET Core applications adopt Oracle DeepSec with minimal code changes.</p><p>After a one-time setup, existing applications can use DeepSec without explicitly creating or assigning an end-user security context.</p><p>Oracle AI Database version 23.26.2 first introduced the feature. I provided an overview of <a href="https://medium.com/@alex.keh/database-enforced-authorization-for-agentic-ai-net-applications-b383408453f6">ODP.NET Deep Data Security and its benefits in a previous blog post</a>. Here’s how to use the new provider with ASP.NET Core.</p><p>First, install the <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.DependencyInjection">Oracle.ManagedDataAccess.DependencyInjection</a> NuGet package, configure its settings, and call builder.Services.AddOracleEndUserSecurityContextProvider(builder.Configuration) before builder.Build().</p><p>Applications provide end-user security information through the authenticated request. When enabled, ODP.NET discovers and uses the provider implicitly. Immediately before an eligible database operation, the provider builds the security context from the current request and attaches it to the database operation. Requests must use JSON Web Token (JWT) bearer authentication so the provider can access the request context.</p><p>Configure the provider in appsettings.json or through the ASP.NET Core IConfiguration model under Oracle.ManagedDataAccess:EndUserSecurityContext. The provider is enabled by default because the EnableEndUserSecurityContextProvider option defaults to true.</p><p>Here’s a sample appsettings.json configuration for the end-user security context provider:</p><pre>{<br>  &quot;Oracle.ManagedDataAccess&quot;: {<br>    &quot;EndUserSecurityContext&quot;: {<br>      &quot;EnableEndUserSecurityContextProvider&quot;: true,<br>      &quot;Type&quot;: &quot;AZURE&quot;,<br>      &quot;TokenUri&quot;: &quot;https://&lt;identity-provider-host&gt;/&lt;tenant&gt;/oauth2/v2.0/token&quot;,<br>      &quot;GrantType&quot;: &quot;client_credentials&quot;,<br>      &quot;ClientId&quot;: &quot;&lt;client-id&gt;&quot;,<br>      &quot;ClientSecret&quot;: &quot;&lt;client-secret&gt;&quot;,<br>      &quot;Scope&quot;: &quot;&lt;database-token-scope&gt;&quot;,<br>      &quot;TokenRenewalOffsetSeconds&quot;: 60,<br>      &quot;SessionDataRoles&quot;: &quot;&lt;role-1&gt;,&lt;role-2&gt;&quot;,<br>      &quot;EndUserContextAttribute&quot;: &quot;{\&quot;&lt;namespace&gt;\&quot;:{\&quot;&lt;key&gt;\&quot;:\&quot;&lt;value&gt;\&quot;}}&quot;,<br>      &quot;FetchGroupsOnScope&quot;: &quot;&lt;optional-oci-groups-scope&gt;&quot;,<br>      &quot;RoleClaimType&quot;: &quot;ORACLE_DATA_ROLE&quot;,<br>      &quot;AttributeClaimType&quot;: &quot;ORACLE_CONTEXT_ATTRIBUTE&quot;<br>    }<br>  }<br>}</pre><p>Note: In a production app, you would supply the client secret in a more secure manner, such as from vault storage.</p><p>Once configured, import Oracle.ManagedDataAccess.DependencyInjection.EndUserSecurityContext and call its registration API before building the host to enable the provider. Here’s a code snippet of what that looks like:</p><pre>using Oracle.ManagedDataAccess.DependencyInjection.EndUserSecurityContext;<br><br>var builder = WebApplication.CreateBuilder(args);<br>builder.Services.AddAuthentication(/* app authentication setup */);<br>builder.Services.AddAuthorization();<br><br>builder.Services.AddOracleEndUserSecurityContextProvider(builder.Configuration);<br><br>var app = builder.Build();<br><br>app.UseAuthentication();<br>app.UseAuthorization();<br><br>app.MapGet(&quot;/health&quot;, () =&gt; Results.Ok(&quot;ok&quot;));<br>app.Run();</pre><p>For more information, see the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/featConnecting.html#end-user-security-context-provider">Deep Data Security End-User Security Context Provider section in the ODP.NET Developer’s Guide</a>. For database set up, review the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/ddscg/quick-starts-configure-oracle-deep-data-security.html">configuration chapter in the Oracle Deep Data Security Guide</a>.</p><h3>Deep Data Security: Optional User Identity</h3><p>Previously, DeepSec required an end-user identity: an access token or username. This release makes the identity optional.</p><p>Some services host multiple applications and AI agents in a single database. Each application or agent may use its own connection pool and perform work independently, without acting on behalf of a human user. By removing the identity requirement, DeepSec now supports these services alongside AI agents and human users.</p><p>Two new OracleEndUserSecurityContext methods create contexts without a user identity:</p><ul><li><a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/EndUserSecurityContextCreateWithDatabaseAccessToken.html#GUID-CDC0F1E9-79A7-428B-999B-EE68DF0BA4D5">CreateWithDatabaseAccessToken(string)</a> — creates an end-user security context using only a database access token.</li><li><a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/EndUserSecurityContextCreateWithoutEndUser.html#GUID-429BE95B-1927-4532-81C8-E773125AA4E4">CreateWithoutEndUser()</a> — creates a new end-user security context with the same database access token, data role, and attribute values as the current instance except for the end user identity.</li></ul><h3>New OpenTelemetry Attribute Tags and Semantic Conventions</h3><p>ODP.NET 23.26.4 supports the latest OpenTelemetry database semantic conventions and attribute names. Deprecated attributes remain available for compatibility.</p><p>Developers can configure ODP.NET to emit traces using the latest attributes, deprecated attributes, or both. The changes include:</p><ul><li>db.name is deprecated; db.namespace replaces it.</li><li>db.odp.connection.id is deprecated; oracle.db.connection.id replaces it.</li><li>db.odp.sql_id is deprecated; oracle.db.sql.id replaces it.</li><li>db.statement is deprecated; db.query.text replaces it.</li><li>db.system is deprecated; db.system.name replaces it.</li><li>db.user is deprecated.</li></ul><p>To configure the behavior, use one of these settings:</p><ul><li>OTEL_SEMCONV_STABILITY_OPT_IN environment variable</li><li>OpenTelemetrySemconvStabilityOptIn .NET configuration setting, or</li><li>OracleConfiguration.OpenTelemetrySemconvStabilityOptIn property</li></ul><p>The configuration sources support the same values. They are:</p><p>• database: emit the new tags only;</p><p>• database/dup: emit both the deprecated and new tags;</p><p>• any other value, or no value: emit the deprecated tags only.</p><p>Read more about <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/featOpenTelemetry.html#odpnet-opentelemetry-traces">ODP.NET OpenTelemetry in the ODP.NET Developer’s Guide</a>.</p><h3>Reset Each Database Session to the Original Application State</h3><p>When an ODP.NET connection returns to the pool, ODP.NET can reset the client and database session state to the original login state. This prevents state from leaking to the next user who receives the connection. Enable this feature by setting the RESET_STATE database service attribute to LOGIN. ODP.NET Core, managed ODP.NET, and unmanaged ODP.NET support it starting with version 23.26.4.</p><p>With this setting, each pooled connection starts with the same session state, reducing artifacts that might persist after a failover.</p><p>To learn more about using the RESET_STATE attribute and LOGIN value, read the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/adfns/high-availability.html#GUID-7950B60E-E05A-4B96-ACFC-777074B768F2">Application Continuity section of the Oracle Database Development Guide</a>.</p><h3>ODP.NET Performance Improvements</h3><p>For this release, ODP.NET includes performance improvements across the provider, including faster EF Core SaveChanges operations and improved asynchronous execution. Performance remains a focus, and we plan to deliver further improvements in upcoming ODP.NET releases in 2027.</p><h3>Coming Soon</h3><p>In November, Microsoft will release .NET 11 and EF Core 11. ODP.NET will support both soon afterward, and I will announce availability in future blog posts.</p><p>Until then, read more about the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/release_changes.html#GUID-608C2CE9-86B7-4B29-BF17-8B33826E6256">ODP.NET 23.26.4 features in the ODP.NET Developer’s Guide</a> and download ODP.NET packages from <a href="https://www.nuget.org/profiles/Oracle">NuGet Gallery</a>.</p><h3>FAQs</h3><p><strong>How does SQL script execution exchange inputs and results?</strong><br>Applications can bind parameters through JSON or the standard command parameter collection, while execution results are returned as JSON.</p><p><strong>How is the Deep Data Security provider enabled?</strong><br>Install the dependency injection package, configure the provider, and register it before building the ASP.NET Core application. The provider is enabled by default after setup.</p><p><strong>Does the release remove older OpenTelemetry attributes?</strong><br>No. It supports the latest attribute names and conventions while retaining deprecated attributes for compatibility.</p><p><strong>What does the new session reset feature do?</strong><br>It restores pooled database connections to their original login state, helping prevent one user’s session settings from affecting the next user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b31c59aedef1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oracledevs/odp-net-sql-scripting-and-the-deep-data-security-end-user-security-context-provider-b31c59aedef1">ODP.NET SQL Scripting and the Deep Data Security End-User Security Context Provider</a> was originally published in <a href="https://medium.com/oracledevs">Oracle Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Run Oracle SQL Scripts in .NET]]></title>
            <link>https://medium.com/oracledevs/run-oracle-sql-scripts-in-net-bd4e950ff104?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd4e950ff104</guid>
            <category><![CDATA[odpnet]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[plsql]]></category>
            <category><![CDATA[sql-scripting]]></category>
            <category><![CDATA[oracle-ai-database]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 23:05:53 GMT</pubDate>
            <atom:updated>2026-11-09T21:09:11.055Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>ODP.NET script execution is designed </strong>for safer, automated Oracle database updates across cloud and AI workflows</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kIStepNXoVZUPJ2JL0NLCg.png" /></figure><h3>Key takeaways</h3><ul><li>The preview feature runs multiple SQL and PL/SQL statements directly from .NET applications without a separate scripting tool.</li><li>Scripts can come from files, cloud storage, REST APIs, or any other source available as a .NET stream.</li><li>Results, output parameters, metadata, and detailed errors are returned as JSON for easy processing and recovery.</li><li>Developers can control error handling, parameter binding, transactions, output limits, and concurrent script execution using .NET.</li></ul><p>ODP.NET Core introduces a scripting option for applying database changes. Developers can now programmatically manage schema changes, errors, and scale their workflows more easily without a separate tool. ODP.NET scripting benefits include:</p><ul><li>Cloud and AI-friendly</li></ul><p>As more applications move to the cloud and adopt AI, management tools must support cloud automation and AI-driven operations. ODP.NET scripting can run in the cloud and enable both AI agents and human operators to execute database tasks.</p><p>· Enhanced security and safety</p><p>ODP.NET scripting can retrieve credentials at runtime from encrypted vaults or secure environment configurations, so they do not appear in command history.</p><p>· Robust error handling and conditional logic</p><p>.NET applications can inspect detailed statement execution errors to automate recovery workflows, such as retries after a temporary network outage or rolling back changes. Developers can inspect the execution results to determine application-level failures and take the appropriate next steps.</p><p>· Seamless data sharing and state management</p><p>Programmers can capture script output as JSON, parse it, and manipulate it as variables or objects. Keeping intermediate results in memory can avoid disk I/O, which can improve performance and reduce exposure of sensitive data.</p><p>· Parallelism and concurrency</p><p>.NET provides APIs for asynchronous programming, threads, and parallel processing, making it easier to run multiple scripts concurrently.</p><h3><strong>ODP.NET SQL Script Execution Features</strong></h3><p>For these reasons, we have introduced ODP.NET SQL scripting. Available on NuGet as a preview release, the <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.SQLScriptExecution">Oracle.ManagedDataAccess.SQLScriptExecution</a> package supports:</p><ul><li>Executing SQL scripts with OracleCommand.ExecuteStatements</li><li>Running multiple SQL and PL/SQL statements from one stream</li><li>Returning result sets, output parameters, and errors as JSON</li><li>Binding parameters through JSON or APIs</li><li>Choosing whether to stop after an error or continue execution</li><li>Setting LOB and LONG fetch limits for JSON results</li><li>Getting statement-level metadata with detailed error information</li></ul><p>Let’s explore ODP.NET SQL script execution.</p><h3><strong>Using SQL Script Execution</strong></h3><p>ODP.NET Core can execute SQL and PL/SQL from a StreamReader so that developers can apply and automate their database changes. The scripts can originate from a file, blob storage, a REST API, or any other source that can be represented by a .NET StreamReader.</p><p>Programmatically, a script is represented by a .NET StreamReader object and passed to an OracleCommand.ExecuteStatements extension method to run.</p><p>Parameters can be provided either as a JSON document via OracleCommand.SetParametersForExecuteStatements method or through the OracleCommand.Parameters collection. If both are provided, the parameter collection takes precedence. JSON-based parameters support bind-by-name only, while the parameter collection supports bind-by-name and bind-by-position.</p><p>SQL script execution supports binding all the parameter data types ODP.NET can bind except for associative arrays, array binds, and user-defined types.</p><p>Output result sets, parameters, and metadata, such as rows affected are all returned as JSON strings.</p><p>For every error, its related information is returned, including its number, message, and statement parsing metadata. Developers can configure whether the script aborts upon an error (default) or continues to execute after the error. After an error, previously committed statements are not undone. Retries must account for partially committed scripts.</p><p>These scripts can only contain SQL and PL/SQL syntax. A forward slash (/) on a line by itself is supported as a PL/SQL block terminator. It is recognized by the SQL script execution parser as a statement terminator and is not included in the statement text returned in the result JSON. Other SQL*Plus and SQLcl syntax is not supported.</p><p>By default, statements execute with the connection’s auto-commit behavior. Transactions are supported. However, if a DDL statement is supplied within a transaction, its execution implicitly commits the current transaction. The remaining statements are executed in connection’s auto-commit mode.</p><p>ODP.NET SQL script execution is backwards compatible with the same database versions as the ODP.NET version it depends on. For example, ODP.NET 26ai is backwards compatible with Oracle Database 19c.</p><h4><strong>Sample Scripts and Output</strong></h4><p>Here is a C# code sample that supplies a script and its input parameters through StreamReader objects, sets the script error option behavior, and executes the script. The results are returned as a JSON string. The script and parameters are retrieved from Oracle Cloud infrastructure Object Storage.</p><pre>const string namespaceName = &quot;&lt;OCI_NAMESPACE&gt;&quot;;<br>const string bucketName = &quot;&lt;BUCKET_NAME&gt;&quot;;<br>const string sqlObjectName = &quot;oci_sql_script.sql&quot;;<br>const string jsonParametersObjectName = &quot;oci_sql_parameters.json&quot;;<br><br>// Authenticate using the DEFAULT OCI profile.<br>var provider = new ConfigFileAuthenticationDetailsProvider(&quot;DEFAULT&quot;);<br><br>using var objectStorageClient = new ObjectStorageClient(provider);<br><br>// Retrieve the SQL script from OCI Object Storage.<br>var sqlRequest = new GetObjectRequest<br>{<br>    NamespaceName = namespaceName,<br>    BucketName = bucketName,<br>    ObjectName = sqlObjectName<br>};<br><br>var sqlResponse = await objectStorageClient.GetObject(<br>    sqlRequest,<br>    completionOption: HttpCompletionOption.ResponseHeadersRead);<br><br>using var sqlReader = new StreamReader(<br>    sqlResponse.InputStream,<br>    Encoding.UTF8,<br>    detectEncodingFromByteOrderMarks: true);<br><br>// Retrieve the JSON parameters from OCI Object Storage.<br>var jsonParametersRequest = new GetObjectRequest<br>{<br>    NamespaceName = namespaceName,<br>    BucketName = bucketName,<br>    ObjectName = jsonParametersObjectName<br>};<br><br>var jsonResponse =<br>      await objectStorageClient.GetObject(jsonParametersRequest);<br><br>using var jsonParametersReader = new StreamReader(<br>    jsonResponse.InputStream,<br>    Encoding.UTF8,<br>    detectEncodingFromByteOrderMarks: true);<br><br>// Open the database connection.<br>using var connection = new OracleConnection(&quot;&lt;CONNECTION_STRING&gt;&quot;);<br>connection.Open();<br><br>using var command = connection.CreateCommand();<br><br>// Set parameters from the JSON stream.<br>command.SetParametersForExecuteStatements(jsonParametersReader);<br><br>// Set execution behavior.<br>var executionSettings = new OracleStatementExecutionSettings<br>{<br>    ExecutionOption = OracleExecutionOption.ContinueOnError<br>};<br><br>// Execute the SQL/PLSQL script from the stream.<br>string results = command.ExecuteStatements(<br>    sqlReader,<br>    executionSettings);</pre><p>The SQL script contains a series of SQL and/or PL/SQL statements.</p><pre>insert into EMPTABLE(EMPNO, ENAME) values (5,&#39;John&#39;);<br>insert into INVALIDEMPTABLE(EMPNO, ENAME) values (10, &#39;Max&#39;) returning EMPNO into :param1;<br>select * FROM EMPTABLE where ENAME = :param2;<br><br>BEGIN<br>:p_message := NVL(:p_message, &#39;&#39;) || &#39;is an anonymous PL/SQL block.&#39;;<br>END;<br>/</pre><p>A JSON stream provides the parameter binding information for the SQL script. The JSON below supplies the parameters for the SQL script above.</p><pre>[<br>  {<br>    &quot;name&quot;: &quot;param1&quot;,<br>    &quot;type&quot;: &quot;NUMBER&quot;,<br>    &quot;direction&quot;: &quot;Output&quot;<br>  },<br>  {<br>    &quot;name&quot;: &quot;param2&quot;,<br>    &quot;type&quot;: &quot;VARCHAR2&quot;,<br>    &quot;size&quot;: 32,<br>    &quot;value&quot;: &quot;John&quot;,<br>    &quot;direction&quot;: &quot;Input&quot;<br>  },<br>  {<br>    &quot;name&quot;: &quot;p_message&quot;,<br>    &quot;type&quot;: &quot;VARCHAR2&quot;,<br>    &quot;size&quot;: 40,<br>    &quot;value&quot;: &quot;This &quot;,<br>    &quot;direction&quot;: &quot;InputOutput&quot;<br>  }<br>]</pre><p>After the script executes, the results from the SELECT statement are returned as a JSON output string. Here are several examples of the output.</p><blockquote>Note: The JSON document returned from SQL script execution does not escape the characters &lt;, &gt;, &amp;, and ‘. If the JSON is embedded in HTML or ‘&lt;script&gt;’ content, apply the appropriate context-specific encoding before inserting it to avoid any security vulnerabilities.</blockquote><p><strong>DML Statement Output</strong></p><pre>{ <br>    &quot;statement&quot;: &quot;insert into EMPTABLE(EMPNO, ENAME) values (5,&#39;John&#39;)&quot;,  <br>    &quot;errors&quot;: null,<br>    &quot;rowsAffected&quot;: 1,<br>    &quot;result&quot;: null<br>}</pre><p><strong>Execution Error Output</strong></p><pre>{<br>  &quot;statement&quot;: &quot;insert into INVALIDEMPTABLE(EMPNO, ENAME) values (10, &#39;Max&#39;) returning EMPNO into :param1&quot;,<br>  &quot;rowsAffected&quot;: null,<br>  &quot;result&quot;: null,<br>  &quot;errors&quot;: {<br>    &quot;startLine&quot;: 2,<br>    &quot;endLine&quot;: 2,<br>    &quot;startColumn&quot;: 1,<br>    &quot;endColumn&quot;: 90,<br>    &quot;items&quot;: [<br>      {<br>        &quot;number&quot;: 942,<br>        &quot;message&quot;: &quot;ORA-00942: table or view does not exist&quot;<br>      }<br>    ]<br>  }<br>}</pre><p><strong>SELECT Output</strong></p><pre>{<br>    &quot;statement&quot;: &quot;select * FROM EMPTABLE where ENAME = :param2;&quot;,<br>    &quot;errors&quot;: null,<br>    &quot;rowsAffected&quot;: -1,<br>    &quot;result&quot;: [<br>      {<br>        &quot;columns&quot;: [<br>          { <br>            &quot;name&quot;: &quot;EMPNO&quot;, <br>            &quot;type&quot;: &quot;NUMBER&quot;,<br>            &quot;precision&quot;: 0,<br>            &quot;scale&quot;: -127,<br>            &quot;columnDefinition&quot;: &quot;NUMBER&quot;<br>          },<br>          { <br>            &quot;name&quot;: &quot;ENAME&quot;, <br>            &quot;type&quot;: &quot;VARCHAR2&quot;,<br>            &quot;size&quot;: 32,<br>            &quot;isByteSemantic&quot;: true,<br>            &quot;columnDefinition&quot;: &quot;VARCHAR2(32)&quot;<br>          }<br>          ],<br>        &quot;rows&quot;: [<br>          [<br>            5, <br>            &quot;John&quot;<br>          ],<br>          [<br>            20, <br>            &quot;John&quot;<br>          ]<br>        ]<br>      }<br>    ]<br>}</pre><p><strong>PL/SQL Output</strong></p><pre>{<br>    &quot;statement&quot;: &quot;BEGIN\r\n:p_message := NVL(:p_message, &#39;&#39;) || &#39;is an anonymous PL/SQL block.&#39;;\r\nEND;\r\n&quot;,<br>    &quot;errors&quot;: null,<br>    &quot;rowsAffected&quot;: -1,<br>    &quot;result&quot;: [<br>      {<br>        &quot;columns&quot;: [<br>          {<br>            &quot;name&quot;: &quot;p_message&quot;,<br>            &quot;type&quot;: &quot;VARCHAR2&quot;<br>          }<br>        ],<br>        &quot;rows&quot;: [<br>          [<br>            &quot;This is an anonymous PL/SQL block.&quot;<br>          ]<br>        ]<br>      }<br>    ]<br>}</pre><h4><strong>Oracle Data Type Representation in JSON Results</strong></h4><p>This table defines how Oracle database data types are mapped to JSON value types (JsonValueKind) in .NET for accurate JSON representation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*uSFFrJ8dntm2gNF66b9K0A.png" /><figcaption>ODP.NET SQL Scripting data type representation in JSON</figcaption></figure><p>Now that the capabilities and features have been covered, let’s explore the ODP.NET SQL scripting APIs in detail.</p><h3><strong>SQL Script Execution APIs</strong></h3><h4><strong>OracleCommand.ExecuteStatements Method</strong></h4><p>This method executes a stream of SQL and PL/SQL statements and returns any results as a JSON string.</p><p><strong>Declaration</strong></p><pre>public static string ExecuteStatements (this OracleCommand cmd, StreamReader streamReader, OracleStatementExecutionSettings executionSettings = null);</pre><p><strong>Parameters</strong></p><ul><li><em>cmd</em> — The OracleCommand instance</li><li><em>streamReader — </em>The stream of SQL and PL/SQL statements to execute.</li><li><em>executionSettings — </em>The mode the statements are executed and output size limits for LONG/LOB columns.</li></ul><p><strong>Return Value</strong></p><p>A JSON string with result sets, result metadata, and error information, if applicable.</p><p><strong>Remarks</strong></p><p>By default, each statement execution is auto-committed. App can use ExecuteStatements in a transaction by starting the transaction before calling this method.</p><p>executionSettings determines behavior when a statement returns an error.</p><p><strong>Statement Execution Result Format</strong></p><p>The return value is output in the following JSON schema format:</p><pre>{<br>  &quot;$schema&quot;: &quot;https://json-schema.org/draft/2020-12/schema&quot;,<br>  &quot;$id&quot;: &quot;urn:oracle:manageddataaccess:sqlscriptexecution:schemas:statement-result:1.0&quot;,<br>  &quot;title&quot;: &quot;ScriptExecutionResults&quot;,<br>  &quot;type&quot;: &quot;array&quot;,<br>  &quot;items&quot;: {<br>    &quot;type&quot;: &quot;object&quot;,<br>    &quot;required&quot;: [<br>      &quot;statement&quot;,<br>      &quot;errors&quot;,<br>      &quot;rowsAffected&quot;,<br>      &quot;result&quot;<br>    ],<br>    &quot;properties&quot;: {<br>      &quot;statement&quot;: {<br>        &quot;type&quot;: &quot;string&quot;,<br>        &quot;description&quot;: &quot;SQL or PL/SQL command text&quot;<br>      },<br>      &quot;errors&quot;: {<br>        &quot;description&quot;: &quot;Error details if execution failed; null otherwise&quot;,<br>        &quot;oneOf&quot;: [<br>          {<br>            &quot;type&quot;: &quot;null&quot;<br>          },<br>          {<br>            &quot;type&quot;: &quot;object&quot;,<br>            &quot;required&quot;: [<br>              &quot;startLine&quot;,<br>              &quot;endLine&quot;,<br>              &quot;startColumn&quot;,<br>              &quot;endColumn&quot;,<br>              &quot;items&quot;<br>            ],<br>            &quot;properties&quot;: {<br>              &quot;startLine&quot;: {<br>                &quot;type&quot;: &quot;integer&quot;,<br>                &quot;minimum&quot;: 1<br>              },<br>              &quot;endLine&quot;: {<br>                &quot;type&quot;: &quot;integer&quot;,<br>                &quot;minimum&quot;: 1<br>              },<br>              &quot;startColumn&quot;: {<br>                &quot;type&quot;: &quot;integer&quot;,<br>                &quot;minimum&quot;: 1<br>              },<br>              &quot;endColumn&quot;: {<br>                &quot;type&quot;: &quot;integer&quot;,<br>                &quot;minimum&quot;: 1<br>              },<br>              &quot;items&quot;: {<br>                &quot;type&quot;: &quot;array&quot;,<br>                &quot;minItems&quot;: 1,<br>                &quot;items&quot;: {<br>                  &quot;type&quot;: &quot;object&quot;,<br>                  &quot;required&quot;: [<br>                    &quot;number&quot;,<br>                    &quot;message&quot;<br>                  ],<br>                  &quot;properties&quot;: {<br>                    &quot;number&quot;: {<br>                      &quot;type&quot;: [<br>                        &quot;integer&quot;,<br>                        &quot;null&quot;<br>                      ],<br>                      &quot;description&quot;: &quot;Oracle error number or null for non-SQL errors&quot;<br>                    },<br>                    &quot;message&quot;: {<br>                      &quot;type&quot;: &quot;string&quot;<br>                    }<br>                  },<br>                  &quot;additionalProperties&quot;: false<br>                }<br>              }<br>            },<br>            &quot;additionalProperties&quot;: false<br>          }<br>        ]<br>      },<br>      &quot;rowsAffected&quot;: {<br>        &quot;description&quot;: &quot;-1 for successful SELECT, DDL, and PL/SQL statements; a nonnegative affected-row count for successful DML; null when statement execution fails&quot;,<br>        &quot;oneOf&quot;: [<br>          {<br>            &quot;type&quot;: &quot;integer&quot;<br>          },<br>          {<br>            &quot;type&quot;: &quot;null&quot;<br>          }<br>        ]<br>      },<br>      &quot;result&quot;: {<br>        &quot;description&quot;: &quot;Query result sets or OUT / IN OUT bind values&quot;,<br>        &quot;oneOf&quot;: [<br>          {<br>            &quot;type&quot;: &quot;null&quot;<br>          },<br>          {<br>            &quot;type&quot;: &quot;array&quot;,<br>            &quot;items&quot;: {<br>              &quot;type&quot;: &quot;object&quot;,<br>              &quot;required&quot;: [<br>                &quot;columns&quot;,<br>                &quot;rows&quot;<br>              ],<br>              &quot;properties&quot;: {<br>                &quot;columns&quot;: {<br>                  &quot;description&quot;: &quot;Metadata for each column in the result set, in the same order as values appear in each row.&quot;,<br>                  &quot;type&quot;: &quot;array&quot;,<br>                  &quot;items&quot;: {<br>                    &quot;$ref&quot;: &quot;#/$defs/columnMetadata&quot;<br>                  }<br>                },<br>                &quot;rows&quot;: {<br>                  &quot;description&quot;: &quot;Result set rows; each row is an array of column values&quot;,<br>                  &quot;type&quot;: &quot;array&quot;,<br>                  &quot;items&quot;: {<br>                    &quot;type&quot;: &quot;array&quot;,<br>                    &quot;items&quot;: {}<br>                  }<br>                }<br>              },<br>              &quot;additionalProperties&quot;: false<br>            }<br>          }<br>        ]<br>      }<br>    },<br>    &quot;additionalProperties&quot;: false<br>  },<br>  &quot;$defs&quot;: {<br>    &quot;oracleNativeType&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;description&quot;: &quot;Oracle native data type or PL/SQL data type.&quot;,<br>      &quot;enum&quot;: [<br>        &quot;NUMBER&quot;,<br>        &quot;INT&quot;,<br>        &quot;INTEGER&quot;,<br>        &quot;FLOAT&quot;,<br>        &quot;LONG&quot;,<br>        &quot;BINARY_FLOAT&quot;,<br>        &quot;BINARY_DOUBLE&quot;,<br>        &quot;VARCHAR2&quot;,<br>        &quot;NVARCHAR2&quot;,<br>        &quot;CHAR&quot;,<br>        &quot;NCHAR&quot;,<br>        &quot;CLOB&quot;,<br>        &quot;NCLOB&quot;,<br>        &quot;BLOB&quot;,<br>        &quot;BFILE&quot;,<br>        &quot;DATE&quot;,<br>        &quot;TIMESTAMP&quot;,<br>        &quot;TIMESTAMP WITH TIME ZONE&quot;,<br>        &quot;TIMESTAMP WITH LOCAL TIME ZONE&quot;,<br>        &quot;INTERVAL DAY TO SECOND&quot;,<br>        &quot;INTERVAL YEAR TO MONTH&quot;,<br>        &quot;RAW&quot;,<br>        &quot;LONG RAW&quot;,<br>        &quot;ROWID&quot;,<br>        &quot;BOOLEAN&quot;,<br>        &quot;JSON&quot;,<br>        &quot;VECTOR&quot;,<br>        &quot;REFCURSOR&quot;,<br>        &quot;SYS_REFCURSOR&quot;,<br>        &quot;XMLTYPE&quot;<br>      ]<br>    },<br>    &quot;columnMetadata&quot;: {<br>      &quot;type&quot;: &quot;object&quot;,<br>      &quot;required&quot;: [<br>        &quot;name&quot;,<br>        &quot;type&quot;<br>      ],<br>      &quot;properties&quot;: {<br>        &quot;name&quot;: {<br>          &quot;type&quot;: &quot;string&quot;,<br>          &quot;description&quot;: &quot;Column name for SELECT result sets, or parameter name for OUT/INOUT/ReturnValue bind results&quot;<br>        },<br>        &quot;type&quot;: {<br>          &quot;$ref&quot;: &quot;#/$defs/oracleNativeType&quot;<br>        },<br>        &quot;precision&quot;: {<br>          &quot;type&quot;: &quot;integer&quot;,<br>          &quot;minimum&quot;: 0,<br>          &quot;description&quot;: &quot;Numeric precision (optional)&quot;<br>        },<br>        &quot;scale&quot;: {<br>          &quot;type&quot;: &quot;integer&quot;,<br>          &quot;minimum&quot;: -127,<br>          &quot;description&quot;: &quot;Numeric scale (optional)&quot;<br>        },<br>        &quot;size&quot;: {<br>          &quot;type&quot;: &quot;integer&quot;,<br>          &quot;minimum&quot;: 1,<br>          &quot;description&quot;: &quot;Size of the column in bytes or chars depending on isByteSemantic (optional)&quot;<br>        },<br>        &quot;isByteSemantic&quot;: {<br>          &quot;type&quot;: &quot;boolean&quot;,<br>          &quot;description&quot;: &quot;True for byte semantics, false for character semantics (optional)&quot;<br>        },<br>        &quot;vectorDimensions&quot;: {<br>          &quot;type&quot;: &quot;string&quot;,<br>          &quot;description&quot;: &quot;Vector dimension count for VECTOR types (optional)&quot;<br>        },<br>        &quot;vectorType&quot;: {<br>          &quot;type&quot;: &quot;string&quot;,<br>          &quot;enum&quot;: [<br>            &quot;DENSE&quot;,<br>            &quot;SPARSE&quot;<br>          ],<br>          &quot;description&quot;: &quot;Vector storage type for VECTOR columns (optional)&quot;<br>        },<br>        &quot;vectorDimensionFormat&quot;: {<br>          &quot;type&quot;: &quot;string&quot;,<br>          &quot;description&quot;: &quot;Vector dimension format for VECTOR columns (optional)&quot;<br>        },<br>        &quot;columnDefinition&quot;: {<br>          &quot;type&quot;: &quot;string&quot;,<br>          &quot;description&quot;: &quot;The column definition that matches what SQL*Plus returns when describing a table with this column&quot;<br>        }<br>      },<br>      &quot;additionalProperties&quot;: false<br>    }<br>  }<br>}</pre><h4><strong>OracleCommand.SetParametersForExecuteStatements Method</strong></h4><p>This method binds a JSON stream of parameters for SQL script execution.</p><p><strong>Declaration</strong></p><pre>public static void SetParametersForExecuteStatements(this OracleCommand cmd, StreamReader jsonParameters)</pre><p><strong>Parameter</strong></p><ul><li><em>cmd</em> — The OracleCommand instance</li><li><em>jsonParameters — </em>The parameter information to bind to the script’s SQL and PL/SQL statements.</li></ul><p><strong>Remarks</strong></p><p>Parameters can only be bound by name using this method.</p><p><strong>Bind Parameter Format</strong></p><p>SQL script execution parameters are bound using the following JSON schema format:</p><pre>{<br>  &quot;$schema&quot;: &quot;https://json-schema.org/draft/2020-12/schema&quot;,<br>  &quot;$id&quot;: &quot;urn:oracle:manageddataaccess:sqlscriptexecution:schemas:bind-parameters:1.0&quot;,<br>  &quot;title&quot;: &quot;BindParameters&quot;,<br>  &quot;type&quot;: &quot;array&quot;,<br>  &quot;items&quot;: {<br>    &quot;type&quot;: &quot;object&quot;,<br>    &quot;required&quot;: [<br>      &quot;name&quot;,<br>      &quot;type&quot;,<br>      &quot;direction&quot;<br>    ],<br>    &quot;properties&quot;: {<br>      &quot;name&quot;: {<br>        &quot;type&quot;: &quot;string&quot;<br>      },<br>      &quot;type&quot;: {<br>        &quot;$ref&quot;: &quot;#/$defs/oracleNativeType&quot;<br>      },<br>      &quot;direction&quot;: {<br>        &quot;type&quot;: &quot;string&quot;,<br>        &quot;enum&quot;: [<br>          &quot;Input&quot;,<br>          &quot;Output&quot;,<br>          &quot;InputOutput&quot;,<br>          &quot;ReturnValue&quot;<br>        ]<br>      },<br>      &quot;value&quot;: {<br>        &quot;description&quot;: &quot;Value for the bind parameter.&quot;<br>      },<br>      &quot;size&quot;: {<br>        &quot;type&quot;: &quot;integer&quot;,<br>        &quot;minimum&quot;: 1<br>      },<br>      &quot;precision&quot;: {<br>        &quot;type&quot;: &quot;integer&quot;,<br>        &quot;minimum&quot;: 0<br>      },<br>      &quot;scale&quot;: {<br>        &quot;type&quot;: &quot;integer&quot;,<br>        &quot;minimum&quot;: -127<br>      }<br>    },<br>    &quot;allOf&quot;: [<br>      {<br>        &quot;if&quot;: {<br>          &quot;properties&quot;: {<br>            &quot;direction&quot;: {<br>              &quot;enum&quot;: [<br>                &quot;Output&quot;,<br>                &quot;InputOutput&quot;,<br>                &quot;ReturnValue&quot;<br>              ]<br>            },<br>            &quot;type&quot;: {<br>              &quot;enum&quot;: [<br>                &quot;VARCHAR2&quot;,<br>                &quot;NVARCHAR2&quot;,<br>                &quot;CHAR&quot;,<br>                &quot;NCHAR&quot;,<br>                &quot;RAW&quot;,<br>                &quot;LONG RAW&quot;<br>              ]<br>            }<br>          },<br>          &quot;required&quot;: [<br>            &quot;direction&quot;,<br>            &quot;type&quot;<br>          ]<br>        },<br>        &quot;then&quot;: {<br>          &quot;required&quot;: [<br>            &quot;size&quot;<br>          ]<br>        }<br>      },<br>      {<br>        &quot;if&quot;: {<br>          &quot;properties&quot;: {<br>            &quot;direction&quot;: {<br>              &quot;enum&quot;: [<br>                &quot;Input&quot;,<br>                &quot;InputOutput&quot;<br>              ]<br>            }<br>          },<br>          &quot;required&quot;: [<br>            &quot;direction&quot;<br>          ]<br>        },<br>        &quot;then&quot;: {<br>          &quot;required&quot;: [<br>            &quot;value&quot;<br>          ]<br>        }<br>      }<br>    ],<br>    &quot;additionalProperties&quot;: false<br>  },<br>  &quot;$defs&quot;: {<br>    &quot;oracleNativeType&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;description&quot;: &quot;Oracle native data type or PL/SQL data type.&quot;,<br>      &quot;enum&quot;: [<br>        &quot;NUMBER&quot;,<br>        &quot;INT&quot;,<br>        &quot;INTEGER&quot;,<br>        &quot;LONG&quot;,<br>        &quot;BINARY_FLOAT&quot;,<br>        &quot;BINARY_DOUBLE&quot;,<br>        &quot;VARCHAR2&quot;,<br>        &quot;NVARCHAR2&quot;,<br>        &quot;CHAR&quot;,<br>        &quot;NCHAR&quot;,<br>        &quot;CLOB&quot;,<br>        &quot;NCLOB&quot;,<br>        &quot;BLOB&quot;,<br>        &quot;BFILE&quot;,<br>        &quot;DATE&quot;,<br>        &quot;TIMESTAMP&quot;,<br>        &quot;TIMESTAMP WITH TIME ZONE&quot;,<br>        &quot;TIMESTAMP WITH LOCAL TIME ZONE&quot;,<br>        &quot;INTERVAL DAY TO SECOND&quot;,<br>        &quot;INTERVAL YEAR TO MONTH&quot;,<br>        &quot;RAW&quot;,<br>        &quot;LONG RAW&quot;,<br>        &quot;BOOLEAN&quot;,<br>        &quot;JSON&quot;,<br>        &quot;VECTOR&quot;,<br>        &quot;REFCURSOR&quot;,<br>        &quot;SYS_REFCURSOR&quot;,<br>        &quot;XMLTYPE&quot;<br>      ]<br>    }<br>  }<br>}</pre><h4><strong>OracleStatementExecutionSettings Class</strong></h4><p>An OracleStatementExecutionSettings object provides options for configuring the execution mode of SQL and PL/SQL statements from a script and output size limits for LONG/LOB columns.</p><p><strong>Class Inheritance</strong></p><p>System.Object</p><ul><li>Oracle.ManagedDataAccess.SQLScriptExecution.OracleStatementExecutionSettings</li></ul><p><strong>Declaration</strong></p><pre>public sealed class OracleStatementExecutionSettings</pre><p><strong>Thread Safety</strong></p><p>Instance members are not guaranteed to be thread-safe.</p><h4>OracleStatementExecutionSettings.<strong>ExecutionOption Property</strong></h4><p>This property specifies ODP.NET SQL script execution exception behavior.</p><p><strong>Declaration</strong></p><pre>public OracleExecutionOption ExecutionOption {get; set;}</pre><p><strong>Property Value</strong></p><p>An OracleExecutionOption enumeration value</p><p><strong>Property Type</strong></p><p>OracleExecutionOption</p><p><strong>Remarks</strong></p><p>This property determines ODP.NET behavior when SQL script execution encounters an error. Either the execution aborts on error, OracleExecutionOption.AbortOnError<em>, </em>(default) or continues to execute the remaining statements after the error is encountered, OracleExecutionOption.ContinueOnError.</p><h4>OracleStatementExecutionSettings.<strong>MaxLOBFetchSize Property</strong></h4><p>This property specifies the maximum amount of LOB data included in the JSON result.</p><p><strong>Declaration</strong></p><pre>public long MaxLOBFetchSize { get; set; }</pre><p><strong>Property Value</strong></p><p>The maximum number of characters for CLOB/NCLOB data or the maximum number of bytes for BLOB/BFILE data to include in the result JSON.</p><p><strong>Property Type</strong></p><p>Long</p><p><strong>Remarks</strong></p><p>This property limits how much CLOB/NCLOB/BLOB/BFILE data is fetched and serialized into the JSON result for each LOB column value. If the LOB value exceeds this limit, only up to MaxLOBFetchSize characters for CLOB/NCLOB or bytes for BLOB/BFILE are included. The default is 65536.</p><h4>OracleStatementExecutionSettings.<strong>MaxLONGFetchSize Property</strong></h4><p>This property specifies the maximum amount of LONG data (LONG/LONG RAW) included in the JSON result.</p><p><strong>Declaration</strong></p><pre>public long MaxLONGFetchSize { get; set; }</pre><p><strong>Property Value</strong></p><p>The maximum number of characters for LONG data or the maximum number of bytes for LONG RAW data to include in the result JSON.</p><p><strong>Property Type</strong></p><p>Long</p><p><strong>Remarks</strong></p><p>This property limits how much LONG/LONG RAW data is fetched and serialized into the JSON result for each LONG column value. If the value exceeds this limit, only up to MaxLONGFetchSize characters for LONG or bytes for LONG RAW are included. The default is 65536.</p><h4>OracleExecutionOption Enumeration</h4><p>This enumeration values specifies the SQL script execution behavior after encountering an exception.</p><p><strong>OracleExecutionOption Enumeration Values</strong></p><p>AbortOnError — When ODP.NET encounters an exception, SQL script execution stops with no further statements executed. This is the default value.</p><p>ContinueOnError — When ODP.NET encounters an exception, SQL script execution continues on.</p><h3><strong>Get Started with ODP.NET SQL Scripting</strong></h3><p>After this whirlwind tour, try ODP.NET SQL scripting for yourself. Download the <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.SQLScriptExecution">SQL scripting package from NuGet</a> and share feedback with the Oracle team on <a href="https://github.com/oracle/dotnet-db-samples/issues">GitHub</a> or <strong>in</strong> the <a href="https://forums.oracle.com/ords/apexds/domain/dev-community/category/odp-dot-net">ODP.NET discussion forum</a>.</p><p>#OracleDotNet</p><h3>FAQs</h3><p><strong>How can developers access the feature?</strong><br>It is available as a preview release through the <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.SQLScriptExecution">Oracle.ManagedDataAccess.SQLScriptExecution</a> package on NuGet.</p><p><strong>What syntax can a script contain?</strong><br>Scripts may contain SQL and PL/SQL, including / as a PL/SQL block terminator. Other SQL*Plus and SQLcl commands are unsupported.</p><p><strong>What happens when a statement fails?</strong><br>Execution stops by default, but it can be configured to continue. Each error includes its number, message, and location in the statement.</p><p><strong>How are database changes committed?</strong><br>Statements are auto-committed by default. Transactions are supported, although a DDL statement implicitly commits the current transaction and causes the remaining statements to run in auto-commit mode.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd4e950ff104" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oracledevs/run-oracle-sql-scripts-in-net-bd4e950ff104">Run Oracle SQL Scripts in .NET</a> was originally published in <a href="https://medium.com/oracledevs">Oracle Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New ODP.NET Releases for AI Agent Development and AI Skills]]></title>
            <link>https://medium.com/oracledevs/new-odp-net-releases-for-ai-agent-development-and-ai-skills-75cf9c6e4946?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/75cf9c6e4946</guid>
            <category><![CDATA[deep-data-security]]></category>
            <category><![CDATA[microsoft-agent-framework]]></category>
            <category><![CDATA[odpnet]]></category>
            <category><![CDATA[oracle-ai-database]]></category>
            <category><![CDATA[ai-skills]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 00:17:47 GMT</pubDate>
            <atom:updated>2026-10-20T18:32:45.363Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introducing the Oracle AI Database Vector Store Connector, Oracle .NET AI Skills, and new Deep Data Security features</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CLqcCzjqQUtcf4x0ji-m0A.png" /></figure><h3>Key Takeaways</h3><ul><li>ODP.NET 26ai (23.26.3) and the Oracle AI Database Vector Store Connector are now available for .NET developers.</li><li>The connector lets applications store, search, update, and delete vectors in Oracle AI Database and supports Microsoft Agent Framework.</li><li>Expanded Oracle Deep Data Security features allow applications to manage access for human users and AI agents through end-user names and lookup keys.</li><li>Oracle .NET AI skills provide reusable guidance that helps coding agents create ODP.NET applications using Oracle best practices.</li></ul><p>I’m excited to announce ODP.NET 26ai (23.26.3) and the production release of the Oracle AI Database Vector Store Connector, expanding support for AI agent development.</p><p>These releases add new AI agent, skills, and security capabilities for Oracle .NET developers. With the Oracle AI Database Vector Store Connector, .NET applications can search, create, read, update, and delete vectors directly in Oracle AI Database.</p><p>The connector also integrates with Microsoft AI technologies, including Microsoft Agent Framework, to support AI agents, large language model (LLM) applications, Model Context Protocol (MCP) solutions, and workflows.</p><p>ODP.NET 23.26.3 extends Oracle Deep Data Security support for agentic AI by adding end-user names and lookup keys to security contexts. These additions give developers more flexible ways to create and manage security contexts for both users and AI agents.</p><p>Finally, we’ve released <a href="https://github.com/oracle/skills/blob/main/db/appdev/dotnet-oracle.md">Oracle .NET AI developer skills</a> to help AI coding agents build robust ODP.NET applications faster while following Oracle best practices.</p><p>Oracle AI Database and ODP.NET offer a broad set of capabilities for C# data applications, including performance, high availability, security, data management, scalability, and AI. The challenge is that developers need time to learn these capabilities and apply the right practices.</p><p>Oracle AI skills help agents apply that guidance directly when generating application code, improving developer productivity while helping teams avoid common implementation pitfalls.</p><p>Let’s take a closer look at these new capabilities and the benefits they provide.</p><h3>Oracle AI Database Vector Store Connector</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KJgT8__OuNiflZ6Yy8o70w.png" /><figcaption>Oracle Vector Store Connector integrates Microsoft Agent Framework and Oracle AI Database</figcaption></figure><p>The Oracle AI Database Vector Store Connector for .NET is now generally available in the Oracle.VectorData NuGet package. It provides out-of-the-box support for standard .NET vector operations, so existing C# AI applications can use Oracle AI Database to store and retrieve vectors with minimal code changes.</p><p>The connector also exposes Oracle AI Database 26ai capabilities beyond basic vector storage, including multiple vector distance functions and vector index types that most databases don’t offer. This gives .NET developers access to a broader set of vector search options directly from their applications.</p><p>The new Oracle connector also supports Microsoft Agent Framework, an SDK and runtime for building, orchestrating, and deploying multi-agent AI systems. It combines simple agent abstractions with enterprise-ready capabilities.</p><p>Microsoft Agent Framework applications can use Oracle AI Database as a vector store for retrieval-augmented generation. Because the framework uses the same vector store libraries as .NET, existing connectors such as Oracle’s can integrate with little or no additional customization.</p><p>To learn more about the Oracle AI Database Vector Store Connector, explore the documentation or try the sample applications.</p><ul><li><a href="https://learn.microsoft.com/en-us/semantic-kernel/concepts/vector-store-connectors/out-of-the-box-connectors/oracle-connector?pivots=programming-language-csharp">Documentation: Using the Oracle AI Database Vector Store Connector</a></li><li><a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/VSConnector4SKClasses.html#GUID-6E3FFDD3-17B3-42E1-BA14-902E011C6FDA">Documentation: Oracle AI Database Vector Store Connector Classes</a></li><li><a href="https://github.com/oracle/dotnet-db-samples/tree/master/samples/ai-vector">Samples: AI </a><a href="https://github.com/oracle/dotnet-db-samples/tree/master/samples/ai-vector">Agent Framework Chat App </a><a href="https://github.com/oracle/dotnet-db-samples/tree/master/samples/ai-vector">and AI Vector Hotel Search App</a></li></ul><p>The connector supports both .NET and .NET Framework and uses ODP.NET for database access.</p><p>While the connector supports Oracle Database 19c and later, I recommend Oracle AI Database 26ai for its broader vector search and AI agent capabilities, with additional features delivered in quarterly releases. One of its most important capabilities is Deep Data Security, designed to help secure applications for the agentic AI era.</p><p>That brings us to the second major Oracle .NET enhancement in this release: expanded Deep Data Security integration.</p><h3>ODP.NET Deep Data Security End-user Names and Lookup Keys</h3><figure><img alt="Oracle Deep Data Security is a database-enforced data authorization framework for developers and security architects to define and enforce application-level security requirements for all applications." src="https://cdn-images-1.medium.com/max/1024/1*lbchAmJppWLK_SnXyqeXSQ.avif" /><figcaption>Oracle Deep Data Security is a database-enforced data authorization framework for developers and security architects to define and enforce application-level security requirements for all applications.</figcaption></figure><p>Agentic AI can perform complex tasks, but it often requires broad, dynamic access to data, increasing security and compliance risk. Enforcing authorization in the database reduces duplicated application logic and keeps access rules consistent across applications, agents, and tools.</p><p>Oracle Deep Data Security provides unified, database-native policy enforcement for both conventional and AI applications. ODP.NET 23.26.2 first added support for passing Deep Data Security end-user security contexts from .NET applications. I covered this integration in more detail in a <a href="https://medium.com/oracledevs/database-enforced-authorization-for-agentic-ai-net-applications-b383408453f6">previous blog post</a>.</p><p>Deep Data Security plays a critical role in AI by helping prevent autonomous agents from exposing sensitive information or making unauthorized data changes. Enforcing security policies in the database provides a consistent control point instead of relying on every application to govern AI agents correctly and stay up to date on new practices.</p><p>In the vibe-coding era, AI can generate applications quickly, cheaply, and with extensive customization. That can produce many variations of the same application, some of which may be rarely updated. Centralized database security helps keep access policies consistent across all of them.</p><p>With so many applications, thorough code and security reviews may become less consistent. AI coding agents also may not understand an organization’s specific end-user authorization rules unless those rules are explicitly provided.</p><h4>Oracle Deep Data Security Usage Scenario</h4><p>Consider a human resources database. Employees should see only their own salary and, where appropriate, the salaries of their direct reports. Sensitive identifiers, such as Social Security numbers, should be restricted to the individual they belong to. Employees may be allowed to update their home address, but not their salary.</p><p>Building all of these business, security, and legal rules into every AI application is difficult to maintain. Centralizing authorization in the database helps prevent unintended data exposure and unauthorized changes across applications and agents.</p><p>That’s where Oracle Deep Data Security comes in. By enforcing security at the database level, organizations can simplify policy setup, maintenance, and auditing. Developers can also place less trust in individual applications, which actually makes it easier to build and deploy securely.</p><h4>ODP.NET Deep Data Security End-user Names and Lookup Keys</h4><p>In the latest release, ODP.NET Deep Data Security adds support for end-user names and lookup keys in end-user security contexts. This gives applications more flexible ways to manage user and AI agent access. An external application identity can now be mapped to a database session without requiring a corresponding account in an external identity and access management system, such as Microsoft Entra ID.</p><p>A Deep Data Security end-user name can represent a human or AI agent authenticated by the application, rather than a traditional database user account. The end-user name can be used in a security context instead of a user access token.</p><p>A lookup key gives Oracle Deep Data Security a unique identifier for an application-managed end user. It maps the authenticated identity to the appropriate database policies, data roles, and data grants, enabling fine-grained access enforcement.</p><p>The lookup key is automatically generated when an end-user security context is created with an end-user name. The .NET security context then contains the lookup key, database access token, and end-user name.</p><p>Here’s a C# example that creates the security context using an end-user name. You can see the context created with the CreateWithTokenAndName method and end-user parameter.</p><pre>/* Setup an end user for the security context in lieu of a user access token.<br>* Create the user:<br>  CREATE END USER deepsec_end_user;<br>* Create data grant to give limited HR schema access to the end user:<br>  CREATE DATA GRANT enduser_grant AS SELECT (ALL COLUMNS EXCEPT salary) ON hr.employees TO deepsec_end_user;<br>*/<br><br>// Read database token from file. <br>string midtierToken = GetMidtierToken(); <br>// Create security context with deepsec_end_user.<br>OracleEndUserSecurityContext securityCtx = OracleEndUserSecurityContext.CreateWithTokenAndName(midtierToken, &quot;deepsec_end_user&quot;); <br><br>// Create and open connection. Deep Data Security requires a TCPS connection. <br>// low_privilege_user only has connection privileges. <br>OracleConnection conn = new OracleConnection(&quot;user id=low_privilege_user;password=&lt;PASSWORD&gt;;data source=oracle&quot;);<br>conn.Open(); <br>// Set security context on connection <br>conn.SetEndUserSecurityContext(securityCtx); <br><br>// Execute SQL <br>using (var command = new OracleCommand(&quot;SELECT FIRST_NAME, SALARY from hr.employees&quot;, conn)) <br>{<br>  using (var reader = command.ExecuteReader()) <br>  {<br>    while (reader.Read()) <br>    {<br>      // Deepsec_end_user has access to employee first names but not salaries based on data grant.  <br>      // Salary data will return as null values.<br>      Console.WriteLine(&quot;Name: &quot; + (reader.IsDBNull(0) ? &quot;&lt;NULL&gt;&quot; : reader.GetString(0)));<br>      Console.WriteLine(&quot;Salary: &quot; + (reader.IsDBNull(1) ? &quot;&lt;NULL&gt;&quot; : reader.GetString(1)));<br>    }<br>  }<br>}</pre><p>Managed ODP.NET and ODP.NET Core 23.26.3 both support Oracle Deep Data Security end-user names and lookup keys.</p><p>Learn more in the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/featConnecting.html#ODPNT-GUID-5A35E30D-8252-4ED1-9903-80C28E9DE011">ODP.NET Deep Data Security documentation</a>.</p><h3>Oracle .NET AI Skills for More Productivity</h3><p>Perhaps the biggest gain in developer efficiency comes from AI skills. These reusable Markdown files contain instructions, knowledge, and workflows that extend AI agents for specific tasks or domains. Our focus here is ODP.NET and Oracle AI Database development and optimization.</p><p>My team has published an <a href="https://github.com/oracle/skills/blob/main/db/appdev/dotnet-oracle.md">Oracle .NET AI skills file</a> for use with AI tools and coding assistants. You can use it as is or adapt it to your project. It works with new or existing managed ODP.NET, ODP.NET Core, and Oracle EF Core applications.</p><p>We plan to continue expanding the Oracle .NET AI skills over time.</p><p>These Oracle .NET AI skills are part of the <a href="https://github.com/oracle/skills">Oracle AI Skills repository</a>, which covers a broader range of Oracle products and services, including Oracle AI Database. The repository also includes an <a href="https://github.com/oracle/skills/blob/main/db/SKILL.md">Oracle AI Database skills file</a> for improving database code and design, including PL/SQL, SQL, and security.</p><p>You can use individual skill files to focus on specific areas, such as performance or high availability, or combine them to improve your application more holistically.</p><h3>Get Started with New AI Features</h3><p>You can start building AI applications with ODP.NET 23.26.3 and the Oracle AI Database Vector Store Connector today. Download them from NuGet Gallery:</p><ul><li><a href="https://www.nuget.org/packages/Oracle.VectorData/">Oracle AI Database Vector Store Connector</a></li><li><a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core">ODP.NET Core</a></li><li><a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess">Managed ODP.NET</a></li></ul><p>You can also download the Oracle .NET AI skills from GitHub:</p><ul><li><a href="https://github.com/oracle/skills/blob/main/db/appdev/dotnet-oracle.md">Oracle .NET AI skills file</a></li></ul><p>Give them a try to accelerate Oracle .NET AI development and build better applications with less effort.</p><p>#OracleDotNet</p><h3>FAQs</h3><ul><li><strong>What is the Oracle AI Database Vector Store Connector?</strong><br> It is a .NET connector that lets applications use Oracle AI Database to store and retrieve vector data with minimal code changes. It’s available in production.</li><li><strong>Which AI technologies does the connector support?</strong><br> It works with .NET vector libraries and Microsoft Agent Framework for AI agents, LLM applications, MCP solutions, and related workflows.</li><li><strong>How does Deep Data Security help AI applications?</strong><br> It enforces authorization in the database, helping prevent agents and applications from accessing sensitive data or making unauthorized changes.</li><li><strong>What are Oracle .NET AI skills?</strong><br> They are reusable instruction files that help AI coding assistants build and optimize ODP.NET, ODP.NET Core, and Oracle EF Core applications.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75cf9c6e4946" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oracledevs/new-odp-net-releases-for-ai-agent-development-and-ai-skills-75cf9c6e4946">New ODP.NET Releases for AI Agent Development and AI Skills</a> was originally published in <a href="https://medium.com/oracledevs">Oracle Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Oracle AI Database Vector Store Connector Support for Microsoft Agent Framework]]></title>
            <link>https://medium.com/oracledevs/announcing-oracle-ai-database-vector-store-connector-support-for-microsoft-agent-framework-2b1b5bb51b5a?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b1b5bb51b5a</guid>
            <category><![CDATA[odpnet]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[microsoft-agent-framework]]></category>
            <category><![CDATA[oracle-database]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Tue, 02 Jun 2026 17:05:49 GMT</pubDate>
            <atom:updated>2026-10-30T15:03:29.893Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Oracle AI Database vector-store connector provides a .NET integration path for storing and retrieving vectors in the Microsoft Agent Framework workflow described here. Verify the connector, framework, driver, and database versions as one compatible set.</h4><h4>Build enterprise .NET agents with Oracle AI Database RAG and Microsoft’s newest AI framework</h4><figure><img alt="Featured image with title and subtitle" src="https://cdn-images-1.medium.com/max/1024/1*iSlGDL5zs4clDKp2K4Qihw.png" /></figure><h3>Key Takeaways</h3><ul><li>Oracle AI Database Vector Store Connector now supports Microsoft Agent Framework, letting .NET developers use the database as a vector store.</li><li>The connector allows .NET apps to use semantic search with Oracle AI Database retrieval-augmented generation and create, read, update, and delete vectors in Oracle AI Database.</li><li>Developers can use it for enterprise-grade agents, LLM apps, MCP solutions, workflows, and retrieval-augmented generation.</li></ul><figure><img alt="Diagram illustrating a .NET application connecting bidirectionally between Oracle Database and Microsoft Semantic Kernel, showing the application acting as the integration layer between the database and AI framework." src="https://cdn-images-1.medium.com/max/1024/1*46wX3hPH2ECpaZiuj70-7A.png" /><figcaption><strong>.NET Application Integration Architecture</strong></figcaption></figure><p>The Oracle AI Database Vector Store Connector (Oracle.VectorData) now supports Microsoft Agent Framework 1.7 and later, so .NET developers can use Oracle AI Database 26ai as a vector store for AI-based applications.</p><p>The connector lets .NET apps search, create, read, update, and delete vectors in Oracle AI Database. Use it to build agentic, language model (LLM), Model Context Protocol (MCP), and workflow solutions that rely on native AI features in ODP.NET and Oracle AI Database. <a href="https://www.nuget.org/packages/Oracle.VectorData">Download the Oracle connector</a> from NuGet Gallery.</p><p>The connector brings the Oracle data, vectors, and vector indexes to Microsoft Agent Framework services. In an <a href="https://medium.com/oracledevs/announcing-the-oracle-database-vector-store-connector-for-semantic-kernel-adb83e806d4e">earlier post about the Oracle AI Database Vector Store Connector</a>, I covered its main features, .NET vector and Semantic Kernel support, and a comprehensive sample application demonstrating its capabilities. Those features also work with Microsoft Agent Framework.</p><h3>Using Oracle AI Database Vector Store Connector with Microsoft Agent Framework</h3><p>Microsoft Agent Framework is an SDK and runtime for building, orchestrating, and deploying AI agents and multi-agent workflows. It combines AutoGen’s simple agent patterns with Semantic Kernel’s enterprise features and was first released in production in April.</p><p>Microsoft Agent Framework, like any AI technology, requires data to operate, learn, and adapt. It uses Microsoft’s published connector model to manage and access data in a vector store, which is typically a database. In our case, the Oracle AI Database Vector Store Connector links Microsoft Agent Framework and Oracle AI Database vectors and data for retrieval-augmented generation (RAG).</p><p>Because the connector model is designed to work with multiple data sources with minimal to no data source specific code required, it’s easy to incorporate existing Microsoft Agent Framework, .NET vector, and Semantic Kernel apps with Oracle AI Database 26ai into existing AI apps.</p><h3>Oracle AI Database AI Capabilities</h3><p>Oracle AI Database 26ai is built to solve enterprise AI challenges. With Oracle AI Vector Search, .NET developers can add AI-powered similarity search to structured and unstructured data while keeping the database’s security, consistency, and operational features. Applications can combine semantic search with exact-match queries to support more precise AI workflows.</p><p>Oracle AI Vector Search can work with many LLMs. With RAG, .NET apps can combine an LLM with your database’s business data to return more relevant, better-grounded results.</p><p>In this video, I present the Oracle vector store capabilities, then demo an AI chat app that uses RAG from an Oracle AI Database with Microsoft Agent Framework. The sample app uses two agents for its RAG: one for Oracle AI Database and one for Microsoft Foundry.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpiQaQGtys14%3Fstart%3D3010%26feature%3Doembed%26start%3D3010&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpiQaQGtys14&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpiQaQGtys14%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/90c32f173eb4ca05e52fb4ecfb0256d6/href">https://medium.com/media/90c32f173eb4ca05e52fb4ecfb0256d6/href</a></iframe><p>Whether you’re building one assistant or coordinating specialized agents in a workflow, Oracle AI Database and Microsoft Agent Framework provide .NET apps multi-agent orchestration, multi-provider model support, and MCP interoperability. Start developing AI apps with these technologies today!</p><h3>Learn more</h3><ul><li><a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/VSConnector4SKClasses.html">ODP.NET Oracle Database Vector Store Connector class documentation</a></li><li><a href="https://www.oracle.com/database/features/">Oracle AI Database features</a></li></ul><h3>FAQs</h3><ul><li><strong>What does the Oracle AI Database Vector Store Connector do?</strong><br>It connects applications to Oracle AI Database so they can manage and search vector data using Microsoft Agent Framework, .NET vectors, and Semantic Kernel.</li><li><strong>Who is this update for?</strong><br>This update is for .NET developers building AI assistants, agent workflows, LLM apps, or MCP-based solutions with the new Microsoft Agent Framework.</li><li><strong>When will the Oracle AI Database Vector Store Connector be production?</strong><br>Oracle plans to release a production .NET vector store connector around the same time as when Microsoft releases its .NET vector store connectors in production. Currently, they are all in preview.</li><li><strong>What software components do I need to create an app with the Oracle connector and Microsoft Agent Framework?</strong><br><a href="https://www.nuget.org/packages/Oracle.VectorData">Download Oracle.VectorData</a> from NuGet Gallery, add Microsoft Agent Framework 1.7 or higher to your project, and connect to Oracle AI Database 26ai. The database can be on-premises, cloud-based, or autonomous.</li></ul><h3><strong>What should the first connector test prove?</strong></h3><p>Create or select the intended collection, write a known vector record, retrieve it with a compatible query embedding, and verify its identifier. Check delete behavior and a failed authorization path before wiring the result into an agent. A package installation alone is not a working RAG application.</p><p><strong>Continue the implementation:</strong> <a href="https://blogs.oracle.com/developers/how-to-troubleshoot-vector-search-in-an-ai-application">How to Troubleshoot Vector Search in an AI Application</a>. Use the validation described above as the acceptance check for your next step.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b1b5bb51b5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oracledevs/announcing-oracle-ai-database-vector-store-connector-support-for-microsoft-agent-framework-2b1b5bb51b5a">Announcing Oracle AI Database Vector Store Connector Support for Microsoft Agent Framework</a> was originally published in <a href="https://medium.com/oracledevs">Oracle Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Database-Enforced Authorization for Agentic AI .NET Applications]]></title>
            <link>https://medium.com/oracledevs/database-enforced-authorization-for-agentic-ai-net-applications-b383408453f6?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/b383408453f6</guid>
            <category><![CDATA[deep-data-security]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[odpnet]]></category>
            <category><![CDATA[oracle-ai-database]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Sat, 02 May 2026 03:09:02 GMT</pubDate>
            <atom:updated>2026-11-06T16:10:35.410Z</atom:updated>
            <content:encoded><![CDATA[<h4>Database-enforced authorization keeps the data-access decision tied to the authenticated end user before results reach an AI application. In a .NET workflow, the important boundary is how that identity reaches the database and how its context is cleared when a connection is reused.</h4><h4>Protect .NET applications from over-broad agent access, prompt injection, and tool misuse with Oracle Deep Data Security and ODP.NET</h4><figure><img alt="Diagram showing secure end-user access to enterprise data. Users authenticate through an identity provider and interact with AI agents, analytics tools, applications, or direct database access. Requests connect to a database protected by deep data security controls, ensuring users only access authorized data." src="https://cdn-images-1.medium.com/max/1024/1*lbchAmJppWLK_SnXyqeXSQ.avif" /><figcaption>Oracle Database deep data security enforcing identity-aware access for AI agents, analytics, and applications.</figcaption></figure><h3>Key Takeaways</h3><ul><li>Agentic AI can perform complex tasks, but it often requires broad and dynamic data access, which increases security and compliance risk.</li><li>Enforcing authorization in the database reduces duplicated application logic and keeps access rules consistent across applications, agents, and tools.</li><li>Oracle Deep Data Security provides database-native policy enforcement. ODP.NET 23.26.2 adds support for passing end-user security context from .NET applications.</li><li>.NET applications can adopt this model by integrating end-user security context into the data access layer.</li></ul><p>Agentic AI changes how applications access data. Instead of following fixed application flows, agents can choose tools and generate actions at runtime.</p><p>When given relevant data, agents can further optimize workflows to meet objectives. However, broader access also increases the risk of unauthorized use and data exfiltration.</p><p>As organizations deploy agentic AI, keeping enterprise data protected and auditable becomes harder with the wrong security model. When agents access the database directly or through Model Context Protocol (MCP) server tools, authorization must still be enforced before data is returned. If the agent’s database access is broader than the end user’s authorization, it can expose sensitive data or modify protected records.</p><p>The key design question is where authorization should be enforced: in every application, or in the database. At scale, maintaining separate authorization logic in every application becomes difficult to validate and easy to get wrong. When requirements, queries, or schemas change, teams must update authorization logic across every affected application. This becomes unmanageable as more AI applications are deployed across the enterprise.</p><p>As attackers adopt AI-driven penetration testing tools to find application vulnerabilities faster than before, securing access control at every app level entry point becomes even more critical.</p><p>On the other hand, database-layer enforcement centralizes authorization and applies policies consistently before data is returned. Instead of relying on every developer to secure their part of the app perimeter, the same database policies can apply whether access comes from an application, an AI agent, or an MCP-based tool. Oracle AI Database 26ai (23.26.2) enables this capability with Deep Data Security.</p><h3>Why Agentic AI Apps Need Deep Data Security</h3><p>Oracle Deep Data Security is a database-native authorization model that extends traditional system and object privileges by using end-user, agent, role, and attribute context in authorization decisions. It is designed for workloads where users, applications, agents, and tools may access the same data through different paths.</p><p>Deep Data Security securely propagates end-user and agent identities, roles, and attributes to the database at runtime using an end-user security context. It is important to note that the end-users may not necessarily be database users. They can be any user type, such as Microsoft Entra ID or web application users. The database uses this context to enforce policies that define what users and agents can do — and when — and to generate audit records that capture activity. For example, a policy can allow a sales manager to see only customer rows for their assigned region, even if an agent generates a broader query.</p><p>The Deep Data Security authorization model enforces fine-grained security at the row, column, and cell levels, enabling least-privilege access so end-users and agents see only authorized data. The database can return only authorized rows and masks sensitive column values when the end-user or agent lacks the required entitlement. Because the database enforces these policies during SQL execution, authorization remains consistent even when different applications or agents access the same data.</p><p>Since policies are enforced in the database, developers do not have to duplicate the same authorization rules in every application or agent workflow. When requirements change, teams can update the database policy instead of rewriting authorization logic across multiple applications.</p><p>For sensitive workflows, access can be granted only for the duration and scope of that workflow, instead of giving the application broad standing privileges. This reduces reliance on shared high-privilege service accounts that can read or write more data than the end user should have access to.</p><p>Access boundaries must stay manageable, enforceable, and auditable as workflows change. Deep Data Security enforces least-privilege access for users and agents while preserving user identity in audit records to support safer, compliant AI adoption. .NET applications should incorporate Deep Data Security and pass end-user context to the database in a way they can manage consistently.</p><h3>Develop .NET Apps with Deep Data Security</h3><p>.NET applications can pass end-user identity, claims, roles, and application context to the database, where Deep Data Security evaluates policies during SQL execution before unauthorized rows, columns, or values can be returned. Managed ODP.NET and ODP.NET Core 23.26.2 add extension methods to use this context payload.</p><p>With minimal code changes, existing ODP.NET applications can use Deep Data Security’s protection with agentic AI. Applications do not need to map each end user to a separate database user. The database evaluates authorization using the supplied end-user security context. The database manages session lifecycles automatically based on OAuth2 tokens, which include user authorization claims for resources and applications.</p><p>To do this, you will set the end-user security context on the ODP.NET connection using OracleConnection.SetEndUserSecurityContext. The connection then executes commands on behalf of an end user identified by a token. The application supplies the end-user context separately from the database access token used by the mid-tier. Deep Data Security then evaluates policies using the end-user claims, roles, and attributes. Data roles and attributes allow Oracle AI Database to evaluate role mappings and token claims during authorization. This enables Deep Data Security to deliver fine-grained, end-user-aware access control in .NET without database user credentials.</p><p>Deep Data Security evaluates policies during SQL execution, before unauthorized rows, columns, or values are returned. By default, unauthorized data is masked as NULL, though SQL functions can apply other formats.</p><p>ODP.NET uses the OracleEndUserSecurityContext class to represent the security identity for an application end user’s database operations.</p><p>Putting it altogether, the following .NET code sample shows how to set a connection’s end-user security context and clear it after use.</p><pre>OracleConnection conn = new OracleConnection(connStr);<br>conn.Open();<br>string userToken = GetUserToken();<br>string midTierToken = GetMidtierToken();<br><br>// Create security context using tokens<br>OracleEndUserSecurityContext securityContext = OracleEndUserSecurityContext.CreateWithTokens(midTierToken, userToken);<br><br>// Set security context on the connection<br>conn.SetEndUserSecurityContext(securityContext);<br><br>// Execute database operations<br><br>// Clear security context from connection<br>conn.ClearEndUserSecurityContext();<br><br>// Close connection<br>conn.Close();</pre><h3>Start Developing with ODP.NET Deep Data Security</h3><p>With ODP.NET and Oracle Deep Data Security, you can build end-to-end agentic AI .NET applications while protecting data from current and emerging threats. Data protection rules can evolve with simple changes, and access can be centrally managed and audited.</p><p>Get started by downloading <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess">managed ODP.NET</a> or <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core">ODP.NET Core</a> 23.26.2 with Deep Data Security and reviewing the <a href="https://www.oracle.com/security/database-security/features/deep-data-security/">Oracle Deep Data Security web page</a> and <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/featConnecting.html#GUID-5A35E30D-8252-4ED1-9903-80C28E9DE011">ODP.NET Developer’s Guide Deep Data Security section</a>.</p><p>To learn more, watch this video on ODP.NET Deep Data Security:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpiQaQGtys14%3Fstart%3D3010%26feature%3Doembed%26start%3D3010&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpiQaQGtys14&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpiQaQGtys14%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/90c32f173eb4ca05e52fb4ecfb0256d6/href">https://medium.com/media/90c32f173eb4ca05e52fb4ecfb0256d6/href</a></iframe><h3><strong>FAQ</strong></h3><ul><li><strong>What is agentic AI?</strong><br>It’s AI that can plan, reason, and execute multi-step tasks independently, often without human supervision.</li><li><strong>Why is managing data security at the database-level preferred?</strong><br>It centralizes data access control, making it easier to manage, update, and audit compared to securing each application individually.</li><li><strong>How does Deep Data Security protect data?</strong><br>It enforces policies at row, column, and cell levels, ensuring users and AI agents only access authorized data.</li><li><strong>How do .NET apps use Deep Data Security?</strong><br>They pass user and app identity via tokens into an ODP.NET connection security context, allowing the database to enforce access rules without exposing credentials.</li></ul><h3><strong>What should the authorization test include?</strong></h3><p>Run the same operation as two users with different permissions, then reuse a pooled connection and repeat the checks. Include an attempted unauthorized read and verify that prohibited content never reaches the model. Successful authentication is not evidence that row or column authorization is correct.</p><p><strong>Continue the implementation:</strong> <a href="https://blogs.oracle.com/developers/how-to-enforce-role-based-data-access-in-ai-applications-with-oracle-deep-data-security">How to Enforce Role-Based Data Access in AI Applications with Oracle Deep Data Security</a>. Use the validation described above as the acceptance check for your next step.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b383408453f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oracledevs/database-enforced-authorization-for-agentic-ai-net-applications-b383408453f6">Database-Enforced Authorization for Agentic AI .NET Applications</a> was originally published in <a href="https://medium.com/oracledevs">Oracle Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[End-to-End Database OpenTelemetry, Priority Transactions, and More]]></title>
            <link>https://medium.com/oracledevs/end-to-end-database-opentelemetry-priority-transactions-and-more-in-odp-net-23-26-2-25cb020f9037?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/25cb020f9037</guid>
            <category><![CDATA[oracle-ai-database]]></category>
            <category><![CDATA[odpnet]]></category>
            <category><![CDATA[opentelemetry]]></category>
            <category><![CDATA[transactions]]></category>
            <category><![CDATA[spatial]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 18:30:10 GMT</pubDate>
            <atom:updated>2026-04-21T08:42:22.229Z</atom:updated>
            <content:encoded><![CDATA[<h4>New ODP.NET 23.26.2 Features</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*Sb8gIbN2Sx86c7BBYr_WtQ.png" /></figure><h3><strong>Key Takeaways</strong></h3><ul><li>ODP.NET 23.26.2 has been released for managed and core providers.</li><li>New features include end-to-end Oracle AI Database OpenTelemetry tracing, priority transactions, EF Core spatial, post quantum cryptography, in-memory certificates and credentials, TLS state transfer, and metrics filtering.</li><li>Oracle Database Vector Store Connector for .NET (production), ODP.NET SQL script execution (preview), and Oracle Deep Data Security for ODP.NET will be arriving soon.</li></ul><p>ODP.NET 26ai (23.26.2) is now available on NuGet for both <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core">core</a> and <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess">managed</a> providers. This release adds new capabilities for observability, transaction management, EF Core spatial, and security — helping you build more robust Oracle .NET apps. Let’s take a closer look at each of these features and benefits.</p><h3>End-to-end App Observability</h3><p>OpenTelemetry is a popular observability framework and a standard for application end-to-end tracing. Your app, ODP.NET, and Oracle AI Database each can emit their own traces, but spotting bottlenecks requires a single, combined view over the entire stack. Client apps and ODP.NET can unify traces on the same host via one OpenTelemetry collector; the database, however, emits a separate trace — forcing admins to align client and database traces manually.</p><p>With end-to-end OpenTelemetry, traces are unified and aligned automatically, making cross‑stack analysis faster and easier. Here’s an ODP.NET ExecuteReader query execution combined trace, visualized in Jaeger, an open‑source distributed tracing tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BgTHO-6cCg6dTxXqRr2LGA.png" /><figcaption>An ODP.NET ExecuteReader query execution trace, visualized in Jaeger, an open-source distributed tracing tool.</figcaption></figure><p>The entire operation takes 14 ms. The database activity (orange) runs early on and lasts 3 ms, while ODP.NET activity (blue) spans the entire operation. ODP.NET and Oracle Database OpenTelemetry tags — such as db.namespace, db.response.returned_rows, and db.user—appear combined in an easy‑to‑read graphical view.</p><p>Identifying errors and performance issues is easier when database and ODP.NET operations align visually for each round trip. The db.odp.roundtrip.duration and db.odp.roundtrip.count tag data help pinpoint latency and excessive activity.</p><p>As an OpenTelemetry collector, Jaeger provides a holistic view of app activity. Here, it aggregates seven query executions from ODP.NET and Oracle Database traces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0eVl8jOjWj1vy0ch0IB9GA.png" /><figcaption>Aggregating query executions from ODP.NET and Oracle AI Database traces</figcaption></figure><p>In the screen shot, we see most queries finish in about half a second or less — except the fourth, which takes 3.8 seconds. This view makes slow operations easy to spot, then lets you drill into the query’s trace to see whether the delay is on the client or database side — and why.</p><p>While this blog post example uses Jaeger, any OpenTelemetry Protocol (OTLP)–compliant collector, such as Prometheus or Splunk, works with Oracle OpenTelemetry. The only other requirement is ODP.NET and Oracle AI Database must use the same exporter for unified tracing.</p><p>Oracle’s end-to-end tracing works by embedding database OpenTelemetry child spans within ODP.NET traces. ODP.NET passes the client app context to the database, which then links its own trace to ODP.NET’s to create a unified view. The combined trace is exported to a collector. Notably, ODP.NET never gains access to the database trace itself.</p><p>Database spans are generated on each round trip — such as command executions, reads, and fills. By default, database OpenTelemetry is off. To enable end-to-end tracing, set the ODP.NET property DatabaseOpenTelemetryTracing = true. You can set it on OracleConfiguration, OracleConnection, OracleDataSource, OracleDataSourceBuilder, or in app/web.config.</p><p>You can toggle database OpenTelemetry on and off at any point in an ODP.NET connection’s lifetime. This lets you trace only the code you need to without adding unnecessary overhead to the rest of the app.</p><p>End-to-end tracing gives developers a holistic view of app activity, speeding performance analysis and error resolution.</p><h3>Unblock Critical Updates with Priority Transactions</h3><p>Not every app transaction matters equally. Some are more critical to business operations than others. When a low‑priority transaction unintentionally holds row locks, it can block higher‑priority work from updating the same rows. This can occur after an exception leaves the low‑priority transaction uncommitted. In these cases, an administrator must kill the blocker so the app can continue its work. That manual cleanup adds overhead, degrades user experience, and can trigger downtime.</p><p>Starting in Oracle AI Database 26ai (23.26.2), Priority Transactions solve this issue. If a low‑priority transaction blocks a higher‑priority one, the former automatically rolls back and the latter can then commit. Low priority transactions no longer block high priority ones.</p><p>While the low-priority transaction session stays active afterwards, the application must acknowledge the rollback — typically by calling ODP.NET Rollback(). Until then, any command execution on the low-priority transaction session returns ORA‑63302 or ORA‑63300.</p><p>In ODP.NET 23.26.2, both managed and core providers support Priority Transactions. The priority levels are High (default), Medium, and Low. High‑priority transactions can roll back Medium and Low ones; Medium transactions can roll back Low ones.</p><p>Rollbacks don’t happen immediately when a high‑priority transaction is blocked. The database waits for the target time to elapse, then rolls back lower‑priority transactions.</p><ul><li>High priority transactions wait until PRIORITY_TXNS_HIGH_WAIT_TARGET.</li><li>Medium priority transactions wait until PRIORITY_TXNS_MEDIUM_WAIT_TARGET.</li></ul><p>Set ODP.NET transaction priority with the OracleTransactionPriority enum (High, Medium, Low). Configure it via OracleConfiguration, OracleConnection, OracleDataSourceBuilder, or in the .NET Framework config file using the TransactionPriority property. You can also set it when starting a transaction using OracleConnection.BeginTransaction.</p><p>This code snippet below shows how to use ODP.NET transaction priority. Two transactions are created that update the same row; one is low priority and the other high. The low priority transaction executes its data change first but does not commit. The high priority transaction executes and waits until PRIORITY_TXNS_HIGH_WAIT_TARGET expires. When it does, it can then commit the data change.</p><pre>OracleTransaction low_priority_txn = conA.BeginTransaction(OracleTransactionPriority.Low);<br>OracleCommand cmdA = new OracleCommand(“update…sal=sal+1 where empno=7654”, conA);<br>cmdA.ExecuteNonQuery();<br><br>OracleTransaction high_priority_txn = conB.BeginTransaction(OracleTransactionPriority.High);<br>OracleCommand cmdB = new OracleCommand(“update…sal=sal+10 where empno=7654”, conB);<br><br>// Waits for PRIORITY_TXNS_HIGH_WAIT_TARGET seconds<br>cmdB.ExecuteNonQuery();<br>high_priority_txn.Commit();</pre><h3>EF Core Spatial Data</h3><p>Oracle EF Core spatial support previewed last year. It enables Oracle spatial types to map to EF Core types via NetTopologySuite and performs create, query, update, and delete operations on them. In this release, the <a href="https://www.nuget.org/packages/Oracle.EntityFrameworkCore.NetTopologySuite/">Oracle.EntityFrameworkCore.NetTopologySuite</a> library is production-ready. To learn more, I covered these <a href="https://medium.com/oracledevs/new-release-oracle-spatial-data-in-entity-framework-core-ad2e1f046ee1">Oracle EF Core spatial features in a prior post</a>.</p><h3>New Security Features</h3><p>ODP.NET 23.26.2 adds new security algorithms, configuration options, and performance optimizations to better protect your .NET apps.</p><h4>Post Quantum Cryptography</h4><p>Today’s public‑key cryptography relies on math problems that are hard for classical computers to solve. Quantum computers could eventually break many of these schemes, so some bad actors are harvesting encrypted data now to decrypt in the future when quantum computing is powerful enough.</p><p>Post‑quantum cryptography (PQC) uses algorithms designed to resist quantum attacks. For security‑minded organizations, moving to PQC is a proactive step to protect data for the long term.</p><p>ODP.NET and Oracle AI Database support PQC with the Module Lattice Key Encapsulation Mechanism (ML-KEM) and Module Lattice Digital Signature Algorithm (ML-DSA) algorithms. This support is available in ODP.NET Core, managed, and unmanaged.</p><h4>In-memory Certificates and Credentials</h4><p>ODP.NET connections can now load additional in‑memory certificate and credential types, including single sign-on (SSO), PKCS #12 wallet (P12), and Privacy Enhanced Mail (PEM). Each user can hold multiple certificates and credentials, giving apps more configuration choices and fine grain control. Apps no longer have to read wallets only from directories or URLs — they can configure and load them directly in code.</p><p>Three new classes store in‑memory certificates and credentials for OracleConnection:</p><ul><li>OracleSSO — SSO certificates and credentials (Managed ODP.NET and ODP.NET Core)</li><li>OracleP12 — P12 certificates and credentials (Managed ODP.NET and ODP.NET Core)</li><li>OraclePEM —PEM certificates and credentials (ODP.NET Core only)</li></ul><p>After configuring these objects, you must make them read‑only before associating them with OracleConnection for use. Here’s an ODP.NET sample that connects using an SSO file.</p><pre>OracleConnection conn = new OracleConnection(&quot;User Id=/;Data Source=oracle&quot;);<br><br>// Create and populate OracleSSO with SEPS credential.<br>OracleSSO oracleSSO = new OracleSSO();<br>byte[] sso = File.ReadAllBytes(&quot;C:\\myWallets\\cwallet.sso&quot;);<br><br>oracleSSO.Set(sso, OracleCertificateFunctionality.None, OracleCredentialFunctionality.SEPS);<br>oracleSSO.MakeReadOnly();<br>conn.SetSSO(oracleSSO);<br>conn.Open();</pre><h4>TLS State Transfer</h4><p>Managed ODP.NET and ODP.NET Core can share TLS context across processes, avoiding renegotiation and saving compute and network round trips.</p><p>You can enable TLS state transfer by setting NET_TLS_STATE_TRANSFER in listener.ora or cman.ora.</p><h3>ODP.NET Metrics Filtering</h3><p>ODP.NET metrics track connection statistics for monitoring and alerting purposes. By default, they publish at the application domain, connection pool, and database instance levels. If you only need one or two of these levels, ODP.NET 23.26.2 can be configured to filter for only the level(s) needed— so administrators see only the data that matters.</p><p>To configure, set the filter via the MetricsLevel value using the OracleMetricsLevel enum, which is available in managed ODP.NET config files or through OracleConfiguration in both core and managed.</p><p>Each metric publishes a “Level” tag to show its source:</p><ul><li>Application Domain — Level = ”AppDomain”</li><li>Connection Pool — Level = ”ConnectionPool”</li><li>Database Instance — Level = ”DbInstance”</li></ul><h3>Learn More</h3><p>That’s a quick tour of what’s new in ODP.NET 23.26.2. For details, see the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/release_changes.html">ODP.NET Developer’s Guide</a>. Try these features in your next project and tell me what you think.</p><h3>Coming Soon</h3><p>These NuGet packages deliver an initial ODP.NET 23.26.2 feature set — but there’s more coming soon:</p><ul><li><a href="https://www.nuget.org/packages/Oracle.VectorData">Oracle Database Vector Store Connector</a> (production): supports .NET vectors, Microsoft Agent Framework, and Semantic Kernel. Build and run AI vectors, agents, LLMs, and workflows using ODP.NET’s and Oracle AI Database’s native AI features seamlessly.</li><li>SQL Script Execution (preview): execute SQL and PL/SQL scripts directly from files, making database changes easy to apply and automate in .NET.</li><li>Oracle Deep Data Security Security for .NET apps: enforce fine-grained, database-level authorization for agentic AI, analytics, and .NET apps — applying controls based on user identity and runtime context to prevent unintended data exposure from prompt injection, excessive agency, and other risks.</li></ul><p>I’ll cover these in upcoming posts. Stay tuned.</p><h3>FAQ</h3><h4>What problem does end-to-end OpenTelemetry tracing solve?</h4><p>It removes the need to manually line up separate client and database traces by automatically embedding database spans within ODP.NET traces for a unified, collector-friendly view.</p><h4>How do Priority Transactions change blocking behavior?</h4><p>If a lower-priority transaction blocks a higher-priority one, the database can roll back the lower-priority transaction (after a wait target), allowing the higher-priority transaction to proceed and commit.</p><h4>What are the main security and operational enhancements in this release?</h4><p>It introduces post-quantum cryptography algorithms, lets apps load certain wallets/certificates in memory (SSO/P12/PEM), enables TLS state transfer to reduce renegotiation overhead, and allows filtering ODP.NET metrics by level (AppDomain/ConnectionPool/DbInstance).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25cb020f9037" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oracledevs/end-to-end-database-opentelemetry-priority-transactions-and-more-in-odp-net-23-26-2-25cb020f9037">End-to-End Database OpenTelemetry, Priority Transactions, and More</a> was originally published in <a href="https://medium.com/oracledevs">Oracle Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplify Oracle .NET  Cloud Deployments with Centralized Configuration Providers]]></title>
            <link>https://medium.com/oracledevs/simplify-oracle-net-cloud-deployments-with-centralized-configuration-providers-7003ff5bce08?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/7003ff5bce08</guid>
            <category><![CDATA[multi-cloud]]></category>
            <category><![CDATA[odpnet]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[configuration-management]]></category>
            <category><![CDATA[gcp]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 23:53:07 GMT</pubDate>
            <atom:updated>2026-01-30T10:00:06.288Z</atom:updated>
            <content:encoded><![CDATA[<h3>Simplify Oracle .NET Cloud Deployments with Centralized Configuration Providers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*DQBHrNp77ZtDOzjAi2NgBw.png" /></figure><p>Cloud apps are everywhere, often running on multiple hyperscalers. This multicloud reality means more secrets to manage, more configuration to juggle, and more risk of things breaking. Each cloud handles secrets, app settings, and notification updates its own way — so developers end up writing extra code, chasing new bugs, and struggling with app integration. Testing drags on, and every provider switch introduces fresh incompatibilities.</p><p>Oracle AI Database clients cut through this complexity with centralized configuration providers. Instead of different connection setups for each cloud, you use one method that works on every hyperscaler. Centralized configuration simplifies secrets management and client setup, especially for evolving architectures like microservices and serverless apps.</p><p>ODP.NET offers cloud configuration providers for .NET apps — with new support for Amazon Web Services and Google Cloud Platform.</p><h3>ODP.NET Centralized Configuration Providers</h3><p>Managed ODP.NET and ODP.NET Core securely manage application configuration data across all major clouds and on-premises. With these providers, you can:</p><ul><li>Store and retrieve connection details — like connect descriptors and tuning parameters — in cloud storage.</li><li>Manage sensitive data, such as passwords and wallets, in a cloud vault or secrets manager.</li><li>Cache and auto-update connection information using each cloud’s notification system, so your apps stay current and responsive even when credentials change.</li></ul><p>Now, let’s look at each centralized configuration provider.</p><h4><strong>Amazon Web Services (AWS)</strong></h4><p>This provider saves database connection details in AWS Simple Storage Service (S3) and AWS Secrets Manager, then keeps your app updated using AWS Simple Notification Service (SNS) and Simple Queue Service (SQS). You can start using it with the <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.Aws">Oracle.ManagedDataAccess.Aws</a> NuGet package, beginning in the recently released ODP.NET 23.26.1.</p><h4>Google Cloud Platform (GCP)</h4><p>This provider holds connection information in GCP Cloud Storage and GCP Secret Manager with change notifications using GCP Pub/Sub. It is available in the <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.Gcp">Oracle.ManagedDataAccess.Gcp</a> NuGet package, also recently introduced with ODP.NET 23.26.1.</p><h4>Microsoft Azure</h4><p>The <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.Azure">Oracle.ManagedDataAccess.Azure</a> NuGet package stores connection details in Azure App Configuration and Azure Key Vault, and keeps your app current with change notifications via Azure Event Grid and Azure Service Bus.</p><h4>Oracle Cloud Infrastructure (OCI)</h4><p>The <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.Oci">Oracle.ManagedDataAccess.Oci</a> NuGet package stores connection information in OCI Object Storage and OCI Vault, while keeping your app updated with notifications from OCI Events Service and Notifications.</p><h4>Local File System</h4><p>Use the <a href="https://www.nuget.org/packages/Oracle.ManagedDataAccess.ConfigFile">Oracle.ManagedDataAccess.ConfigFile</a> NuGet package for on-premises and Infrastructure as a Service deployments. It stores connection details on the local file system.</p><p>I covered the Azure, OCI, and file config providers in a <a href="https://medium.com/oracledevs/announcing-odp-net-23c-dev-release-fbd92861e466">previous blog post about the ODP.NET 23ai launch</a>. For this post, I will explore the new AWS and GCP providers.</p><h3>ODP.NET AWS Centralized Configuration Provider</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*SbkJdfK5Jgx2yH_G0afzTg.png" /></figure><p>The ODP.NET AWS centralized configuration provider uses a JSON file to store connection details in AWS S3. Like other ODP.NET providers, it locates configurations using connection string URLs, which in this case can point to S3 or Secrets Manager endpoints.</p><p>Set this URL on the OracleConnection.ConnectionString property — replacing the traditional ADO.NET connection string. The URL encodes the provider type, configuration storage, and connection parameters. Standard attributes, like User Id and Max Pool Size, are stored in the cloud.</p><p>Every hyperscaler, including AWS, offers a cloud vault for secret storage. ODP.NET supports using AWS Secrets Manager to store tokens, wallets, passwords, and related secrets for your Oracle .NET apps.</p><p>The AWS provider uses this connection URL syntax:</p><blockquote>config-awss3://{AWS S3 URI or URL}[?key=name&amp;option1=value1&amp;option2=value2…]</blockquote><p>Here, config-awss3 specifies the AWS S3 location. The following section is the URI, URL, or Amazon Resource Name (ARN) of your AWS JSON config file. You can add optional keys and options to define connection names and set authentication, configuration, and change notification settings.</p><p>Here’s a sample ODP.NET AWS S3 connection string URL to open a connection:</p><pre>OracleConnection con = new OracleConnection(&quot;config-awss3://odpnet-config/directory/jsconfig.json?key=connection1&amp;aws_region=us-west-1&quot;);<br>con.Open();</pre><p>The connection string URL points to a provider JSON file, where you can define ODP.NET connection settings. The following example shows how to specify AWS Secrets Manager URLs for the password and wallet location with the config-awssecretsmanager protocol.</p><h3>ODP.NET GCP Centralized Configuration Provider</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*KEVwGLsdh9L6akhinvNiIA.png" /></figure><p>The ODP.NET GCP centralized configuration provider uses a connection string URL — just like the AWS provider — with a similar syntax. This URL points to a JSON configuration file in GCP Cloud Storage that holds your database connection information.</p><p>The syntax:</p><blockquote>config-gcpstorage://project={project-name};bucket={bucket-name};object={object-name}[?key={connectionKey}&amp;option1=value1…]</blockquote><p>Authentication is managed with GCP Application Default Credentials, so you don’t need to add authentication parameters.</p><p>Here’s an example code snippet to open a connection with the ODP.NET GCP provider:</p><pre>string projectId = &quot;dotnet-1&quot;;<br>string bucketName = &quot;odpnet-sample&quot;;<br>string objectName = &quot;hr.json&quot;;<br>OracleConnection conn = new OracleConnection($&quot;config-gcpstorage://project={projectId};bucket={bucketName};object={objectName}?key=Connection1&amp;subscriptionname=projects/dotnet-1/subscriptions/dotnet-sub&quot;);<br>conn.Open();</pre><p>For secrets, use the config-gcpsecretmanager protocol to retrieve sensitive information stored in GCP Secret Manager.</p><h3>Demonstration</h3><p>I recently introduced the AWS and GCP centralized configuration providers at Oracle .NET Office Hours, featuring live demos of both connecting to Oracle Autonomous AI Database. If you missed it, here’s the video:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhVOe7IlQctU%3Fstart%3D1545%26feature%3Doembed%26start%3D1545&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhVOe7IlQctU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhVOe7IlQctU%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8026c564dc23754308814c07eb5b83df/href">https://medium.com/media/8026c564dc23754308814c07eb5b83df/href</a></iframe><h3>Next Steps</h3><p>If you are deploying ODP.NET apps to a hyperscaler, or even on-premises, try these providers. They simplify connection management wherever you run.</p><p>For more details, see the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/InstallCentralConfig.html">ODP.NET Centralized Configuration Providers for Deployments documentation</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7003ff5bce08" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oracledevs/simplify-oracle-net-cloud-deployments-with-centralized-configuration-providers-7003ff5bce08">Simplify Oracle .NET  Cloud Deployments with Centralized Configuration Providers</a> was originally published in <a href="https://medium.com/oracledevs">Oracle Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Release: Oracle Spatial Data in Entity Framework Core]]></title>
            <link>https://medium.com/oracledevs/new-release-oracle-spatial-data-in-entity-framework-core-ad2e1f046ee1?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad2e1f046ee1</guid>
            <category><![CDATA[oracle-database]]></category>
            <category><![CDATA[odpnet]]></category>
            <category><![CDATA[nettopologysuite]]></category>
            <category><![CDATA[ef-core]]></category>
            <category><![CDATA[spatial]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 17:58:18 GMT</pubDate>
            <atom:updated>2025-12-23T10:54:04.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*UbM-WaYrzdDW5tBFmrY9IA.png" /></figure><p>I am pleased to share that <a href="https://www.nuget.org/packages/Oracle.EntityFrameworkCore.NetTopologySuite/10.23.26000-Preview.1">Oracle database spatial support is now available in preview for EF Core</a>. With this enhancement, you can map Oracle spatial data types to EF Core spatial types, making it possible to create, query, modify, and delete spatial data directly.</p><p>Spatial data represents geographic locations and shapes — such as points, lines, and polygons — which allows applications to analyze, search, and interact with location-based information alongside other data in your database. By leveraging this new spatial mapping, developers can build richer, location-aware applications with Oracle AI Database and EF Core.</p><p>I have created three helpful resources to get started developing with Oracle EF Core spatial types:</p><ul><li>This blog post provides a feature overview and the basics for Oracle EF Core app setup.</li><li>An <a href="https://github.com/oracle/dotnet-db-samples/blob/master/samples/ef-core/spatial/oracle-ef-core-nts-spatial.cs">Oracle EF Core code sample</a> using all supported spatial types along with DML operations, such as selects and updates.</li><li>A video (embedded below) covering the features, architecture, and a code sample walk through.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhVOe7IlQctU%3Fstart%3D382%26feature%3Doembed%26start%3D382&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhVOe7IlQctU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhVOe7IlQctU%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bdc65fa80f61e182c045d1a14177d661/href">https://medium.com/media/bdc65fa80f61e182c045d1a14177d661/href</a></iframe><p>Oracle Database and ODP.NET have long provided support for spatial types, allowing the creation of user-defined types for both standard and custom Oracle Spatial entities. This has established a flexible and powerful foundation for handling spatial data.</p><p>With EF Core, spatial data handling occurs through integration with the NetTopologySuite (NTS) library — a .NET implementation of the Java Topology Suite. NTS enables modeling and manipulation of a wide range of geometric shapes, commonly used to represent locations and geographic features.</p><p>With the preview release of the <a href="https://www.nuget.org/packages/Oracle.EntityFrameworkCore.NetTopologySuite/10.23.26000-Preview.1">Oracle.EntityFrameworkCore.NetTopologySuite</a> package on NuGet Gallery, developers can now build spatial applications for Oracle using NTS and EF Core 10 or higher. This integration simplifies spatial data access and expands the capabilities for building robust, geography-aware applications within the .NET ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*xqiWfRtMwN0VFiQ0iLD1tA.png" /></figure><h3>Features</h3><p>Oracle supports mapping all EF Core NTS data types to database spatial columns. The supported NTS data types are:</p><ul><li>Point</li><li>LineString</li><li>Polygon</li><li>MultiPoint</li><li>MultiLineString</li><li>MultiPolygon</li><li>GeometryCollection</li></ul><p>Developers can now create classes using geometry types and perform full CRUD (create, read, update, delete) operations on Oracle spatial data directly through LINQ and EF Core. LINQ spatial operations are automatically translated into Oracle SQL spatial functions, simplifying data access and manipulation.</p><p>Oracle EF Core also supports migrations and scaffolding for spatial columns, making it easier to define and evolve your database schema alongside your codebase.</p><p>.NET developers have control over the spatial tolerance level, which sets the precision for spatial operations — defining how close two points must be to be considered identical. This helps ensure consistent query results based on your app’s business requirements. The default tolerance value is 0.005.</p><p>A broad range of NTS methods and properties, such as Geometry.Distance(geom) and Geometry.Area, are supported in Oracle EF Core. Each maps to corresponding Oracle Spatial functions, ensuring accurate processing and storage of spatial data. For a complete list of supported NTS methods and additional details, refer to the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/SpatialDataandNetTopologySuite.html">Oracle EF Core spatial data documentation</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*7AD18uth5Xjen-OCzrjVdA.png" /></figure><h3>Get Started</h3><p>When you add the Oracle.EntityFrameworkCore.NetTopologySuite package to your project, the NuGet package manager can automatically download all required dependencies for Oracle EF Core spatial development. This ensures you have a streamlined setup process with everything you need to begin working with spatial data.</p><p>After installing the package, follow these steps to start building your spatial application.</p><ol><li>Add the <a href="https://www.nuget.org/packages/Oracle.EntityFrameworkCore.NetTopologySuite">Oracle.EntityFrameworkCore.NetTopologySuite</a> package to your .NET project.</li><li>Use the extension method UseNetTopologySuite(), from DbContext to enable the library. The method configures Oracle’s spatial provider settings, including the tolerance level.</li></ol><pre>services.AddDbContext&lt;MyContext&gt;(options =&gt;<br>    options.UseOracle(&quot;&lt;CONNECTION STRING&gt;&quot;,<br>    o =&gt; o.UseNetTopologySuite(tolerance: 0.01)));</pre><p>3. Define your NTS spatial data types in an EF Core data model.</p><pre>public class MySpatialEntity<br>{<br>    public int Id { get; set; }<br>    <br>    // NetTopologySuite.Geometries.Point<br>    public Point Location { get; set; } <br>}</pre><p>4. Operate on the data with NTS, LINQ, and EF Core.</p><pre>Point myPoint = new Point(10, 20);<br>var nearby = context.MySpatialEntities<br>    .Where(e =&gt; e.Location.IsWithinDistance(myPoint, 1000))<br>    .ToList();</pre><p>And that’s all there is to start developing with Oracle EF Core spatial data.</p><p>For a comprehensive code example, refer to the <a href="https://github.com/oracle/dotnet-db-samples/blob/master/samples/ef-core/spatial/oracle-ef-core-nts-spatial.cs">Oracle EF Core spatial sample</a> on GitHub. This sample demonstrates how to:</p><ul><li>Create a table with a location column for storing NTS geometry data.</li><li>Insert the seven supported NTS geometry types: point, linestring, polygon, multipoint, multilinestring, multipolygon, and geometry collection.</li><li>Retrieve all inserted data and perform a LINQ query to find locations within 2 kilometers of a specific point.</li><li>Update a single location and then update multiple locations.</li><li>Delete all table rows.</li></ul><p>This comprehensive sample demonstrates a complete lifecycle of spatial data operations and provides practical guidance for handling spatial data using Oracle EF Core.</p><h3>Next Steps</h3><p>If you are working with EF Core and want to add spatial data, give this new package a try.</p><p>We value your feedback — please share your experiences, report any bugs, or suggest features either in the <a href="https://forums.oracle.com/ords/apexds/domain/dev-community/category/odp-dot-net">Oracle .NET discussion forum</a> or on <a href="https://github.com/oracle/dotnet-db-samples/issues">GitHub</a>. Your input helps us improve and better meet your development needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad2e1f046ee1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oracledevs/new-release-oracle-spatial-data-in-entity-framework-core-ad2e1f046ee1">New Release: Oracle Spatial Data in Entity Framework Core</a> was originally published in <a href="https://medium.com/oracledevs">Oracle Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploy apps in production with Oracle Entity Framework Core 10]]></title>
            <link>https://medium.com/oracledevs/announcing-oracle-entity-framework-core-10-595fd4d1e984?source=rss-6ed071550929------2</link>
            <guid isPermaLink="false">https://medium.com/p/595fd4d1e984</guid>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[ef-core]]></category>
            <category><![CDATA[dotnet-10]]></category>
            <category><![CDATA[odpnet]]></category>
            <dc:creator><![CDATA[Alex Keh]]></dc:creator>
            <pubDate>Mon, 24 Nov 2025 23:58:58 GMT</pubDate>
            <atom:updated>2026-06-24T17:21:00.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h8tph2HnsHWPWhY_nfpOOw.png" /><figcaption>Oracle AI Database and EF Core 10</figcaption></figure><p>Oracle now supports Microsoft Entity Framework (EF) Core 10 with Oracle AI Database 19c or higher. You can download and deploy <a href="https://www.nuget.org/packages/Oracle.EntityFrameworkCore/10.23.26000">Oracle EF Core 10.23.26000 to production for free from NuGet Gallery</a>.</p><p>Beyond compatibility, this release adds new EF Core 10-specific features that Oracle apps can use. Let’s take a look at each of them.</p><h3>LeftJoin and RightJoin Operators</h3><p>.NET 10 adds first-class LINQ support for the <a href="https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/whatsnew#support-for-the-net-10-leftjoin-and-rightjoin-operators">LeftJoin and </a><a href="https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/whatsnew#support-for-the-net-10-leftjoin-and-rightjoin-operators">RightJoin methods</a>. This makes LEFT JOIN and RIGHT JOIN queries easier to write, respectively.</p><p>The RIGHT JOIN operator keeps all second collection data and only the matching first collection data.</p><p>Oracle EF Core supports both the LeftJoin and RightJoin .NET methods. This example LINQ uses LeftJoin.</p><pre>var query = context.Students<br>    .LeftJoin(<br>        context.Departments,<br>        student =&gt; student.StudentID,<br>        department =&gt; department.DepartmentID,<br>        (student, department) =&gt; new <br>        { <br>            student.FirstName,<br>            student.LastName,<br>            Department = department.Name<br>        });</pre><p>Oracle EF Core generates the following SQL that uses LEFT JOIN:</p><pre>SELECT [s].[FirstName], [s].[FirstName], [d].[Department]<br>FROM [Students] AS [s]<br>LEFT JOIN [Departments] AS [d] ON [s].[StudentID] = [d].[DepartmentID]</pre><h3>ExecuteUpdate for Relational JSON Columns</h3><p>Previously, the ExecuteUpdate method could not update JSON column data. Oracle EF Core now supports referencing <a href="https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/whatsnew#executeupdate-support-for-relational-json-columns">JSON columns and properties within </a><a href="https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/whatsnew#executeupdate-support-for-relational-json-columns">ExecuteUpdate</a>, a new EF Core 10 feature. This allows efficient document-modeled bulk updates in the Oracle database.</p><h3>ExecuteUpdateAsync Accepts Regular Non-Expression Lambda</h3><p>The ExecuteUpdateAsync method performs arbitrary database update operations. In past releases, an expression tree parameter supplied the database row changes, making it difficult for developers to incorporate dynamic updates. Manually creating expression trees was a challenging and error prone process.</p><p>Oracle EF Core 10 apps can now <a href="https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/whatsnew#executeupdateasync-now-accepts-a-regular-non-expression-lambda">pass a lambda expression in the </a><a href="https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/whatsnew#executeupdateasync-now-accepts-a-regular-non-expression-lambda">ExecuteUpdateAsync method</a> to update the records conditionally.</p><h3>Redacting Inlined Constants</h3><p>Earlier EF Core versions logged inline SQL statement parameter values, rather than redact them, even when sensitive data logging was disabled. Oracle EF Core 10 now <a href="https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/whatsnew#redact-inlined-constants-from-logging-by-default">redacts inlined parameters by default</a> to further protect sensitive data from being unintentionally logged.</p><h3>Optimize Count Operation Use on ICollection&lt;T&gt;</h3><p>The <a href="https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/whatsnew#bug-fixes-and-optimizations">Count operation is now optimized to use SQL EXISTS</a> instead of COUNT with .NET collections. For example, let’s start with a modified version of the common Blog and Post classes. We can perform a Count operation on them within a query.</p><pre>public class Blog<br>{<br>    public int Id { get; set; }<br>    public ICollection&lt;Post&gt; Posts { get; set; } = default!;<br>}<br><br>public class Post<br>{<br>    public int Id { get; set; }<br>}<br><br>context.Blogs.Where(b =&gt; b.Posts.Count &gt; 0);</pre><p>In older EF Core versions, the SQL created would use COUNT:</p><pre>SELECT [b].[Id]<br>FROM [Blogs] AS [b]<br>WHERE (<br> SELECT COUNT(*) <br> FROM [Post] AS [p] <br> WHERE [b].[Id] = [p].[BlogId]<br>) &gt; 0</pre><p>With Oracle EF Core 10, the SQL uses EXISTS in the WHERE clause.</p><pre>SELECT [b].[Id]<br>FROM [Blogs] AS [b]<br>WHERE EXISTS (<br> SELECT 1 <br> FROM [Post] AS [p] <br> WHERE [b].[Id] = [p].[BlogId]<br>)</pre><h3>Parameter Name Simplification</h3><p>This <a href="https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/whatsnew#bug-fixes-and-optimizations">enhancement removes the query parameter underscore prefix and improves parameter uniqueness</a> only when needed. A parameter name that would previously be :_city_0 now becomes simpler as :p_city.</p><p>Parameter names that match Oracle reserved keywords will not be simplified to avoid conflicts.</p><h3>Coming Soon — Spatial Data and NetTopologySuite</h3><p>With this release, the infrastructure is in place for EF Core spatial data support with the Oracle database.</p><p>Spatial data can represent physical locations and object shapes. The Oracle database has supported this data type for many years.</p><p>The NetTopologySuite library maps database spatial data types in EF Core.</p><p>A new Oracle NetTopologySuite preview release will allow Oracle database spatial types to be accessed and mapped using EF Core. It is expected to be released before the end of this year.</p><h3>Try Oracle EF Core 10</h3><p>With this release, Oracle database developers can start developing and deploying EF Core 10 apps in production.</p><p>Try it out and let us know your feedback on <a href="https://github.com/oracle/dotnet-db-samples/issues">GitHub</a> or <a href="https://forums.oracle.com/ords/apexds/domain/dev-community/category/odp-dot-net">ODP.NET forum</a>.</p><p>For more information, go to the <a href="https://docs.oracle.com/en/database/oracle/oracle-database/26/odpnt/EFCore10features.html">Oracle EF Core 10 documentation section</a> and watch this video segment on Oracle .NET 10 and EF Core 10 support.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhVOe7IlQctU%3Fstart%3D108%26feature%3Doembed%26start%3D108&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhVOe7IlQctU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhVOe7IlQctU%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/23b5f8a3e6a48fd6bde00b4beebe687a/href">https://medium.com/media/23b5f8a3e6a48fd6bde00b4beebe687a/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=595fd4d1e984" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oracledevs/announcing-oracle-entity-framework-core-10-595fd4d1e984">Deploy apps in production with Oracle Entity Framework Core 10</a> was originally published in <a href="https://medium.com/oracledevs">Oracle Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>