I just want to make it sure that this ODP.NET is the native provider for oracle design for .net and since when exit's? because some of my partners say that it's pretty new and want to know when was the first release. This all discussion came because they chooses not used entity framework because oracle was not release a native provider for .net in the 2008 and want to check if it's true
Originally the Net Framework 1.1 provided a native Oracle ADO.NET provider in the namespace System.Data.OracleClient, but then Microsoft declared it obsolete and stated that these types are deprecated and will be removed in a future version of the .NET Framework. (But are still here in Net 4.0). In the meantime Oracle build ODP.NET and now this could be considered the official Oracle Net Provider.
You can download it for free here
It comes in 32bit and 64bit versions and, as stated by Oracle, it includes Entity Framework, LINQ, WCF Data Services, and implicit REF CURSOR parameter binding support.
At this link you could read numerous FAQ on this provider
Related
We recently upgraded our C# projects from .NET Framework 4.5.2 to .NET 6.0, and now the line
System.Data.Sql.SqlDataSourceEnumerator.Instance.GetDataSources()
no longer works. As far as I can tell, the class SqlDataSourceEnumerator is just not included in the System.Data assembly for .NET 6.0.
I've looked online for other ways to get available SQL Servers, but all of ones I've found either recommend using SqlDataSourceEnumerator, or SmoApplication.EnumAvailableSqlServers() which relies on it internally.
What other ways are there to get available SQL Servers in our C# code that are compatible with .NET 6.0? We need a solution that returns the same info as before (including Server, Name, Instance, Version, and IsLocal).
I am using Sqlite ADO.NET provider 2.0 in my c# application .net framework 4.0.
Question1: Does this .dll come with a back up Database functionality?. If the suer wants to backup, looks like I have to get the source code and write my own backup feature.
Or is it already provided and I just need to use it?
Question2 :
I tried downloading a recent version of Sqlite ADO.NET provider(line 3.5/4.0)
from this website
http://www.sqlite.org/download.html/
sqlite-dll-win32-x64-3071300.zip
After attaching the dll as reference, it still says
Version v2.0.50727.
Description: ADO.NET 2.0 Data Provider for SQLite. Is this correct stable version or is there a recent one to be used.
Thank u
For Question 1: The ADO.NET provider isn't meant to have a backup capability. That's something the RDBMS software should have. ADO.NET is just a tool used to simplify communicating with the RDBMS.
- However, SQLLite backups are documented at http://www.sqllite.org/backup.html
For #2 I don't see a question - just a statement that you got a warning from Visual Studio. BUT based on what I'm seeing, you will get an error. You're trying to use an SqlLite provider for .NET 3.5 or above, and your .NET project is set to 2.0. Either upgrade your app to 3.5 or above, or look for an older .dll to download and use.
As a general rule of thumb, in a .NET project, you can use .dll files specified for an older version of the Framework, but not .dlls specified for newer versions.
I did substantial work developing CLR routines to implement DAL functionality using VS2010 intending to port them to SQL2008R2 clr assemblies;
Did the unit testing, everything seemed fine..
Then the day came to put them in to SQL CLR assemblies..
Alas!, SQL2008 only support assemblies that are below framework 3.5 !
Days spent adopting c# 4.0 functionality, now have to be thrown away and slide back to c#2.0. spending yet few more days.
Can I use Framework 4 CLR assemblies with SQL2010 ?
Will there be support for framework 4.0 support in SQL2008R2 ? if so when ?
Will there be support for framework 4.0 support in SQL2008R2 ? if so when ?
http://software.intel.com/en-us/blogs/2009/10/16/sql-server-2008-sqlclr-net-framework-version/
SQL Server 2008 and the forthcoming
SQL Server 2008 R2 release, previously
codenamed "Kilimanjaro", will both
continue to load the latest service
release of the version 2.0 CLR.
You might be wondering, what is the
rationale behind SQL Server continuing
to load version 2.0 of the CLR? Is it
merely a healthy cautious attitude so
existing UDT's, UDA's, etc. are not
broken; or is it because additional
engineering would be required to
support the new CLR?
It seems the answer is actually a
little of both.
With the .net framework 4.0 we now
have the ability to load two or more
distinct versions of the CLR within a
single process. In previous releases
of the .net framework, a process could
only load a single instance of the
CLR. Given this restriction the CLR
team recommended that hosts, such as
SQL Server, use the LockClrVersion
function to determine the version of
the CLR to load prior to
initialization. So, as stated
previously, SQL Server 2008 and SQL
Server 2008 R2 will continue to load
the latest service release of the
version 2.0 CLR as the version is
locked before initialization of the
CLR begins.
While future versions of SQL Server
may load newer versions of the CLR, or
even support the loading of multiple
CLR's within the process, version 2.0
of the CLR is here to stay for SQLCLR
within SQL Server 2008 and SQL Server
2008 R2.
Also, a little bit more here.
i just download MSCharts, it says i need .NET 3.5 SP1 installed. i already have .net 3.5, whats the deal with sp1
Quoting MSDN:
The .NET Framework 3.5 Service Pack 1 (SP1) delivers:
Performance increases between 20-45%
for WPF-based applications – without
having to change any code
WCF improvements that give developers
more control over the way they access
data and services Streamlined
installation experience for client
applications
Improvements in the area of data
platform, such as the ADO.NET Entity
Framework, ADO.NET Data Services and
support for SQL Server 2008’s new
features
The download can be found here:
http://msdn.microsoft.com/en-us/netframework/aa569263.aspx
I have Oracle9i Release 2 ODAC installed and we are migrating from Microsoft .NET Data Provider for Oracle.
We have some SqlCommand caching implemented, that uses
System.Data.SqlCommandBuilder.DeriveParameters(result) (var result is type of SqlCommand),
but there is no DeriveParameters() method until ODP.NET version 10.
Perhaps anyone has experience using ODP.NET 10.1.XXXXXX or greater with Oracle 9i and has no problems?
You can use ODP.NET R2 for 10g on 9i without problems, as stated in the readme documentation of odp.net R2. I'd go for the R2 version (so 2.10.2.xxx) as it has a native .NET 2.0 build and many bugfixes not present in the 10.1 version. It also is less buggy than the 9.2.0.xxx version.
It will install the 10g client, which can access Oracle databases of version 8i R3 or higher.
You can even use odp.net 11.1.0.6.20 together with Oracle 9i. However use Oracle server 9.2.0.7, not 9.2.0.6 .
Take a look at the following document from Metalink, it might help. It contains a support matrix of ODP Driver Version, Supported Operating System, SQL*Net, RDBMS, .NET Framework, and Visual Studio.
Subject: Oracle Data Provider for .NET (ODP) Supported Configurations
Doc ID: 726240.1