SQL05, application speed.

If this is wrong forum, I apoligize. This is a general question about a
current project.
In terms of speed and security, which would one expect to be faster at the
client side, C# or a browser application, when accessing the Database on SQL?

This is like, which is faster, rear-wheel drive or front-wheel drive? The
answer is that, as a car's speed has a lot more to do with the engine,
driver and conditions, the speed of an application depends more on the code
in the application than whether it was written in C# or ASP.Net or VB or
Java. Well, Java is probably slower by definition, but hopefully you get my
point. Security is a different issue altogether and I'm not sure if you
really meant to include it in your question?


On 8/27/08 5:51 PM, in article
68DA254B-AC5E-42A5-AC49-5C203220CA66-at-microsoft.com, "BrianMultiLanguage"
wrote:

> If this is wrong forum, I apoligize. This is a general question about a
> current project.
> In terms of speed and security, which would one expect to be faster at the
> client side, C# or a browser application, when accessing the Database on SQL?
>
>
>
>

A compiled program and a browser application are on equal ground. Ok.

Yes I mentioned security because accessing customer data should include
security.
So what do you mean?

"Aaron Bertrand [SQL Server MVP]" wrote:

> This is like, which is faster, rear-wheel drive or front-wheel drive? The
> answer is that, as a car's speed has a lot more to do with the engine,
> driver and conditions, the speed of an application depends more on the code
> in the application than whether it was written in C# or ASP.Net or VB or
> Java. Well, Java is probably slower by definition, but hopefully you get my
> point. Security is a different issue altogether and I'm not sure if you
> really meant to include it in your question?
>
>
> On 8/27/08 5:51 PM, in article
> 68DA254B-AC5E-42A5-AC49-5C203220CA66-at-microsoft.com, "BrianMultiLanguage"
> wrote:
>
> > If this is wrong forum, I apoligize. This is a general question about a
> > current project.
> > In terms of speed and security, which would one expect to be faster at the
> > client side, C# or a browser application, when accessing the Database on SQL?
> >
> >
> >
> >
>
>

> Yes I mentioned security because accessing customer data should include
> security.
> So what do you mean?

I mean, you are asking about speed. What does "in terms of speed and
security, which is faster, A or B?" mean? Security and performance should
be two separate priorities, IMHO. If security is more important than speed
(which is usually the case), then you code for the security and then do the
best you can. This does not mean that speed is not important, of course.
If you lock down the database in a similar way then your security should not
affect the speed differently depending on your choice of client application
/ language etc.

A poorly written application will be slow in any language. The .NET
languages can take advantage of classes that are designed to optimize SQL
Server access, so there may be some benefit there over Java + JDBC when
connecting to SQL Server. On the other hand, a poorly written .NET app can
be thoroughly outperformed by a well written Java app. And a bad database
design/poorly written queries/incorrect indexing strategies can destroy
performance of the best .NET or Java apps.

As Aaron pointed out, database and application design are a lot more
important performance-wise than your choice of C-style language.

--

========
Michael Coles
"Pro T-SQL 2008 Programmer's Guide"
http://www.amazon.com/T-SQL-2008-Pro.../dp/143021001X


"BrianMultiLanguage" wrote in
message news:68DA254B-AC5E-42A5-AC49-5C203220CA66-at-microsoft.com...
> If this is wrong forum, I apoligize. This is a general question about a
> current project.
> In terms of speed and security, which would one expect to be faster at
> the
> client side, C# or a browser application, when accessing the Database on SQL?
>
>
>
>

SQL Server security might be easier in .NET languages, since you can take
advantage of trusted security, etc., but speed and security are two separate
issues. In fact, you might even subdivide speed into multiple categories:
application performance speed, coding speed, etc., which themselves depend
on different factors. It always helps me to list my objectives for an
application and prioritize them. A very simple short list might look like
this:

1. Security
2. Application Performance
3. Speed of Development (Turnaround, Time to Market)
....

You might consider prioritizing your objectives for your application the
same way. It'll help you when making decisions about which tools to use.

--

========
Michael Coles
"Pro T-SQL 2008 Programmer's Guide"
http://www.amazon.com/T-SQL-2008-Pro.../dp/143021001X


"BrianMultiLanguage" wrote in
message newsB42F712-9968-4479-85AD-4C245614C548-at-microsoft.com...
>A compiled program and a browser application are on equal ground. Ok.
>
> Yes I mentioned security because accessing customer data should include
> security.
> So what do you mean?
>
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
>> This is like, which is faster, rear-wheel drive or front-wheel drive?
>> The
>> answer is that, as a car's speed has a lot more to do with the engine,
>> driver and conditions, the speed of an application depends more on the
>> code
>> in the application than whether it was written in C# or ASP.Net or VB or
>> Java. Well, Java is probably slower by definition, but hopefully you get
>> my
>> point. Security is a different issue altogether and I'm not sure if you
>> really meant to include it in your question?
>>
>>
>> On 8/27/08 5:51 PM, in article
>> 68DA254B-AC5E-42A5-AC49-5C203220CA66-at-microsoft.com, "BrianMultiLanguage"
>> wrote:
>>
>> > If this is wrong forum, I apoligize. This is a general question about a
>> > current project.
>> > In terms of speed and security, which would one expect to be faster at
>> > the
>> > client side, C# or a browser application, when accessing the Database on SQL?
>> >
>> >
>> >
>> >
>>
>>

On Wed, 27 Aug 2008 14:51:02 -0700, BrianMultiLanguage
wrote:

>If this is wrong forum, I apoligize. This is a general question about a
>current project.
>In terms of speed and security, which would one expect to be faster at the
>client side, C# or a browser application, when accessing the Database on SQL?

I would expect the performance of the client to be such a small part
of the overall performance of a typical database application that the
end user could not tell much difference. That said, the added layer
of a browser based application going through the web server sounds
like extra overhead.

Roy Harvey
Beacon Falls, CT