Antes de adotar o ADO, é bom saber dessas informações.
Microsoft is Aligning with ODBC for Native Relational Data Access
What are you doing since ADO is being depreciated?
https://www.linkedin.com/grp/post/4843954-5847832597740142595
http://blogs.msdn.com/b/sqlnativeclient/archive/2011/08/29/microsoft-is-aligning-with-odbc-for-native-relational-data-access.aspx
... The other reason often mentioned in the surveys is the ease of programming with ODBC. The interfaces are simple and straight forward. With this alignment, C/C++ developers can now focus on one set of APIs for all their native client applications. This will also make porting applications to cloud more seamless.
https://social.technet.microsoft.com/Forums/sqlserver/en-US/e696d0ac-f8e2-4b19-8a08-7a357d3d780f/microsoft-is-aligning-with-odbc-for-native-relational-data-access-faq?forum=sqldataaccess
Question2: Why is Microsoft making this change now? What are the advantages?
Answer: More customers are adopting cloud these days. To enable client applications running on various different platforms to connect to cloud, Microsoft chose ODBC as the de-facto standard client connectivity API for native client applications connecting to SQL Azure. If you are writing applications that run against standalone SQL Server and SQL Azure, or if you are planning to port your application to SQL Azure, using ODBC APIs make the transitions pretty seamless. ODBC APIs use industry standard interfaces and are very simple and straight forward to use. Using multiple result sets, memory management and specifying required/optional properties in OLE DB is more complex. Overall, customers get the benefit of easy programming and cross-platform support with this alignment and can now build applications that can be uniformly ported between various platforms.
E o programador que vá mudando e aprendendo tudo isso! Rodou, rodou, rodou... Agora é ODBC de onde o pessoal do SL "Software Livre" nunca saiu !
Adotar padrões fechados, tem suas vantagens e desvantagens, sujeito ficarmos de joguete nas mãos deles.
Bom de ler são os comentários desse link aqui:
http://blogs.msdn.com/b/sqlnativeclient/archive/2011/08/29/microsoft-is-aligning-with-odbc-for-native-relational-data-access.aspx
This seems crazy! I agree that OLE DB is complicated - but then most people are using ADO.NET for simple scenarios. For performance and flexibility, OLE DB has been vastly superior to ODBC. Can we expect the same performance from the new ODBC driver implementation? Will we have full access to all features? What is the overriding motivation?
Tipo assim: Todos para o lado de cá!!! agora todos para o lado de lá!!! E ela a M$, procurando o din, din, aqui e ali!
E a comunidade Open Source crescendo... todos procurando usar padrões abertos para sair desse labirinto.
Saudações,
Itamar M. Lins Jr.