|
|
You're in the
vb.net
group:DAO vs ADO
vb.net:
ADO Code 66 Seconds
Set dcndb = New ADODB.Connection dcndb.Provider = "Microsoft.Jet.OLEDB.4.0" dcndb.ConnectionString = "Data Source=" + dtbs$ dcndb.Open Set rsUsers = New ADODB.Recordset rsUsers.Open Sql$, dcndb, adOpenForwardOnly, adLockReadOnly DAO Code 20 Seconds Set rDb = DBEngine.Workspaces(0).OpenDatabase(dtbs$) Set rsUsers = rDb.OpenRecordset(Sql$)
DAO is specially optimized for ACCESS ( Native )
ADO is just a uniform way of acessing datasources through a provider so they can`t be compared in this way And for .Net they are both Obsolete so irrelevant ( DAO was / is even obsolete for VB6 ) As we are here in microsoft.public.dotnet , we do it now the recomended way import all data to a SQL 2005 MDF with SMS , now create T-SQL query`s , and now analyze this query in the database engine tuning advisor , apply al recomendations , now run this query from your VB.Net application ( with the sql native client provider ) what do you see now ? You wil probably see that the access database performance is blown away and we ar not even at max , cause we could also create SP`s , indexed views , create functions etc etc to do some final tuning , however this requires skills that most VB proggers do not posess regards Michel [quoted text, click to view] "Alan Welsford" wrote:
> ADO Code 66 Seconds > > Set dcndb = New ADODB.Connection > dcndb.Provider = "Microsoft.Jet.OLEDB.4.0" > dcndb.ConnectionString = "Data Source=" + dtbs$ > dcndb.Open > Set rsUsers = New ADODB.Recordset > rsUsers.Open Sql$, dcndb, adOpenForwardOnly, adLockReadOnly > > DAO Code 20 Seconds > > Set rDb = DBEngine.Workspaces(0).OpenDatabase(dtbs$) > Set rsUsers = rDb.OpenRecordset(Sql$) > > > > *** Sent via Developersdex http://www.developersdex.com ***
[quoted text, click to view]
"Alan Welsford" <men1720@kingsley.co.za> wrote in message news:u82HNxwLHHA.3668@TK2MSFTNGP02.phx.gbl... > ADO Code 66 Seconds > > Set dcndb = New ADODB.Connection > dcndb.Provider = "Microsoft.Jet.OLEDB.4.0" > dcndb.ConnectionString = "Data Source=" + dtbs$ > dcndb.Open > Set rsUsers = New ADODB.Recordset > rsUsers.Open Sql$, dcndb, adOpenForwardOnly, adLockReadOnly > > DAO Code 20 Seconds > > Set rDb = DBEngine.Workspaces(0).OpenDatabase(dtbs$) > Set rsUsers = rDb.OpenRecordset(Sql$) > > > > *** Sent via Developersdex http://www.developersdex.com *** Well, the 66 seconds for ADO does seem an inordinate time as does 20 seconds for DAO, however, the query may be designed to be resource intensive. DAO has always far outperformed ADO (ADO.Net appears to have bridged that gap to some extent). It should be noted that ADO does have a higher overhead given the added functionallity it exposes. Having said that, DAO does perform beautifully and still exposes enough methods to please most. Just to get a new identity value in DAO leaves ADO for dead. If you want to use Access as a back end, DAO is your man. This statement may be inappropriate given the following: 1. Have not tested how DAO plays with Access 2007 2. Given the massive changes MS have made to VB, DAO may not work at some later date. Our tests with Vista show DAO is still fine there. 3. DAO can still exhibit some data instability, althought this seems to be a rare occurrence. Just by coincidence, I am currently finishing a VB6/DAO project for a friend. While I really love the power of VB.Net, the VB6/DAO combination is still really cool for a quick rollout. Cheers Harry
DAO isn't included in WIndows XP, Office 2000 or Office 2002
get a fucking clue kids DAO has been obsolete for a decade it's _NEVER_ been faster -Aaron [quoted text, click to view] Harry Strybos wrote:
> "Alan Welsford" <men1720@kingsley.co.za> wrote in message > news:u82HNxwLHHA.3668@TK2MSFTNGP02.phx.gbl... > > ADO Code 66 Seconds > > > > Set dcndb = New ADODB.Connection > > dcndb.Provider = "Microsoft.Jet.OLEDB.4.0" > > dcndb.ConnectionString = "Data Source=" + dtbs$ > > dcndb.Open > > Set rsUsers = New ADODB.Recordset > > rsUsers.Open Sql$, dcndb, adOpenForwardOnly, adLockReadOnly > > > > DAO Code 20 Seconds > > > > Set rDb = DBEngine.Workspaces(0).OpenDatabase(dtbs$) > > Set rsUsers = rDb.OpenRecordset(Sql$) > > > > > > > > *** Sent via Developersdex http://www.developersdex.com *** > > Well, the 66 seconds for ADO does seem an inordinate time as does 20 seconds > for DAO, however, the query may be designed to be resource intensive. > > DAO has always far outperformed ADO (ADO.Net appears to have bridged that > gap to some extent). It should be noted that ADO does have a higher overhead > given the added functionallity it exposes. Having said that, DAO does > perform beautifully and still exposes enough methods to please most. Just to > get a new identity value in DAO leaves ADO for dead. > > If you want to use Access as a back end, DAO is your man. This statement may > be inappropriate given the following: > > 1. Have not tested how DAO plays with Access 2007 > 2. Given the massive changes MS have made to VB, DAO may not work at some > later date. Our tests with Vista show DAO is still fine there. > 3. DAO can still exhibit some data instability, althought this seems to > be a rare occurrence. > > Just by coincidence, I am currently finishing a VB6/DAO project for a > friend. While I really love the power of VB.Net, the VB6/DAO combination is > still really cool for a quick rollout. > > Cheers > > Harry
[quoted text, click to view] aaron.kempf@gmail.com wrote: > DAO isn't included in WIndows XP, Office 2000 or Office 2002 > > get a fucking clue kids > > DAO has been obsolete for a decade > it's _NEVER_ been faster > > -Aaron DAO was always faster than ADO for Access DB. But since the new ADO.Net there is people saying it's faster some say it's equivalent.
you're so fucking full of shit dude
DAO was never faster ONCE than ADO -Aaron [quoted text, click to view] Franck wrote:
> aaron.kempf@gmail.com wrote: > > DAO isn't included in WIndows XP, Office 2000 or Office 2002 > > > > get a fucking clue kids > > > > DAO has been obsolete for a decade > > it's _NEVER_ been faster > > > > -Aaron > > DAO was always faster than ADO for Access DB. But since the new ADO.Net > there is people saying it's faster some say it's equivalent.
[quoted text, click to view] aaron.kempf@gmail.com wrote: I tried few query :> you're so fucking full of shit dude > > DAO was never faster ONCE than ADO at 1241 record output DAO is 4 sec faster than ADO at 11635 record output DAO is 17 sec faster than ADO DAO > ADO jet.4.0 in access so your comment doesnt apply to my case, i was always faster than ADO for me and it's still faster, maybe depend on your opinion that is wrong and youll keep stick to it because i know you are closed minded
these are my results
at 1241 record output ADO is 4 sec faster than DAO at 11635 record output ADO is 17 sec faster than DAO seriously.. you're fucking deranged MORON! provide your sql fucker, or are you scared to? give me a MDB that will compare and contrast, show me your VBA. and for the record; DAO does take LONGER during development; so it's pointless because DAO has a negative ROI and of course, DAO isn't included in Windows or Access. so it's slower execution, slower development, _HUGE_ risk of memory leaks.. and of course DAO is a fucking pain in the ass to deploy. DAO hasn't even been included in MDAC for a few years now buster and when you lose the fucking training wheels you fucking pansy-- try comparing JET DAO against SQL ADO I don't think that I've run into a single sql statement in the past month that takes more than a second in ADO MDB & ADO is an impractical choice because everyone knows that MDB is obsolete and worthless. Lose the training wheels fucknut; I can scan a billion records in SQL Server with sub-second response times. It is called Analysis Services, fucknut when MDB and your piddly little MDB supports their own Olap engine is when I go back to the 90s and start using DAO -Aaron [quoted text, click to view] Franck wrote:
> aaron.kempf@gmail.com wrote: > > you're so fucking full of shit dude > > > > DAO was never faster ONCE than ADO > I tried few query : > at 1241 record output DAO is 4 sec faster than ADO > at 11635 record output DAO is 17 sec faster than ADO > > DAO > ADO jet.4.0 in access > > so your comment doesnt apply to my case, i was always faster than ADO > for me and it's still faster, maybe depend on your opinion that is > wrong and youll keep stick to it because i know you are closed minded
OK peeps, hands up who really cares? It's much more interesting
watching aaron.kempf trying to be relevant! Keep trying, PHP guy!
[quoted text, click to view] mg wrote: > OK peeps, hands up who really cares? It's much more interesting > watching aaron.kempf trying to be relevant! Keep trying, PHP guy! hehe : ), i have to tell you your not the first one finding that about him. He screw a groups of 215 post in last November now all the subject are screw and multiple subject are mix for a unknown reason because of him :P. search for vb.net isn't stable or something like that. This guy is a jerk. he was like that since a while and he is still like that and i dont think it will ever change, i know how he is, He's sure he is always right and only what he does is the best. don't even try argue with his because he think everyone a looser, he's just a funny close minded guy.
im not close minded
mother fucking niggers and chinks invented a new language; and they don't put enough effort into VB.net to make it a competitive platform they killed the worlds most popular langauge and you retards don't even know the difference Vb6 had a great ROI. VB.net is a utter waste of time.. the framework isn't on ANY desktops _OR_ servers -Aaron
I agree Aaron you are not closed minded.
YOU HAVE TO HAVE ONE BEFORE YOU CAN CLOSE IT. Just go away. If you don't like VB.Net, get the hell out of here are leave us alsone. [quoted text, click to view] aaron.kempf@gmail.com wrote:
> im not close minded > > mother fucking niggers and chinks invented a new language; and they > don't put enough effort into VB.net to make it a competitive platform > > they killed the worlds most popular langauge and you retards don't even > know the difference > > Vb6 had a great ROI. > VB.net is a utter waste of time.. the framework isn't on ANY desktops > _OR_ servers > > -Aaron
the language isnt even CALLED vb.net anymore shithead
-Aaron
I screw a groups of 215 posts in last November?
speak english or die -Aaron [quoted text, click to view] Franck wrote:
> mg wrote: > > OK peeps, hands up who really cares? It's much more interesting > > watching aaron.kempf trying to be relevant! Keep trying, PHP guy! > > hehe : ), i have to tell you your not the first one finding that about > him. He screw a groups of 215 post in last November now all the subject > are screw and multiple subject are mix for a unknown reason because of > him :P. search for vb.net isn't stable or something like that. This guy > is a jerk. he was like that since a while and he is still like that and > i dont think it will ever change, i know how he is, He's sure he is > always right and only what he does is the best. don't even try argue > with his because he think everyone a looser, he's just a funny close > minded guy.
[quoted text, click to view] aaron.kempf@gmail.com wrote: > speak english or die Become relevant or be ignored.
use ADO and stop spreading LIES about DAO fucknut
ADO is faster, more scalable, more flexible.. I can do anything in ADO that you can do in DAO. eat shit DAO cripples! -Aaron
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
| home · blog · groups | Questions? Comments? Contact the dn |