Wrox Home  
Search P2P Archive for: Go

  Return to Index  

aspx thread: Language speeds + System.Data.SQL Vs. System.Data.Ado


Message #1 by "Anders Lundholm" <lundholm@s...> on Mon, 16 Oct 2000 16:55:36 +0200
Two quick questions!



I was wondering how speedy the different languages available in the .NET

framework are?! The way the framework has been design, then all languages

eventually end up in the same format (MSIL), before it is being executed by

the JIT.



So, is the real difference in the interpreter which 'converts' proprietary

source-code to the .NET MSIL language? That is, the C# interpreter is better

than the VB7 interpreter?



The reason I'm asking is, that I've laid the final touches on a big

blueprint for a very big content management system (CMS) and am about to

start programming. Speed is critical, and feel confident enough in C# to use

that language.



The other question I have is about the speed-difference between the two .NET

Data-Classes for database-interaction. My CMS will feature lots of database

requests (naturally), so obviously disconnected recordsets and the

System.Data.SQL (specific for the SQL Server, which I will be using) would

be a good choice.



But, out of curiousity, how fast is the specific SQL Server Class when

compared to the normal System.Data.Ado class?! I haven't unfortunately been

testing in this area yet, so I figured you could spare some of your

experience.



Thanks in advance!



with regards

anders lundholm ˇ lundholm@s...

the sphereworx / monoliner experience

--







Message #2 by =?Windows-1252?Q?Fredrik_Norm=E9n?= <fredrik.normen@e...> on Tue, 17 Oct 2000 09:26:52 +0200
There should not be any different in speed when using C# or VB7.

( Correct me if I'm wrong, but this is what I have heard from the MS .Net

team )



The System.Data.SQL namespace is optimized for SQL Server, and talks

directly to SQL server without going through OLEDB. System.Data.ADO can't

talk to the SQL Server directly it have to go through an OLEDB providers.



If you have MS SQL Server you should use System.Data.SQL, this will improve

the performance of data access.



I hope this is what you are looking for..



/Fredrik Normén











-----Original Message-----

From: Anders Lundholm [mailto:lundholm@s...]

Sent: den 16 oktober 2000 16:56

To: ASP+

Subject: [aspx] Language speeds + System.Data.SQL Vs. System.Data.Ado





Two quick questions!



I was wondering how speedy the different languages available in the .NET

framework are?! The way the framework has been design, then all languages

eventually end up in the same format (MSIL), before it is being executed by

the JIT.



So, is the real difference in the interpreter which 'converts' proprietary

source-code to the .NET MSIL language? That is, the C# interpreter is better

than the VB7 interpreter?



The reason I'm asking is, that I've laid the final touches on a big

blueprint for a very big content management system (CMS) and am about to

start programming. Speed is critical, and feel confident enough in C# to use

that language.



The other question I have is about the speed-difference between the two .NET

Data-Classes for database-interaction. My CMS will feature lots of database

requests (naturally), so obviously disconnected recordsets and the

System.Data.SQL (specific for the SQL Server, which I will be using) would

be a good choice.



But, out of curiousity, how fast is the specific SQL Server Class when

compared to the normal System.Data.Ado class?! I haven't unfortunately been

testing in this area yet, so I figured you could spare some of your

experience.



Thanks in advance!



with regards

anders lundholm ˇ lundholm@s...

the sphereworx / monoliner experience


  Return to Index