SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


RE:


Author
Message
TerryMurphy
TerryMurphy
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 1
This works fine if you have a low number of users. Unfortunately what you gain in flexibility you lose in performance as the number of users rises (or that has been my experience) and that performance hit is not trivial. If you as you say have 300 users then the central resource i.e. your database server has the cooperation of 300 cpus to handle the presentation end of the app - here you are pushing part of that down to the shared resource and your throughput will suffer.



jcraddock
jcraddock
SSC-Enthusiastic
SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)

Group: General Forum Members
Points: 160 Visits: 99

I agree, you are definitely making a trade off.

That trade off is essentially developer time for performance. However, serving application based (internal) webpages is usually something where you can know about how many users to expect. In my case, while we have a good number of users, we don't typically have many concurrent users - I'd say it would rarely go over 40.

SQL Performance and web performance have not been an issue - so far - with basic editing or listing of data.

I have enountered performance problems with a crosstab/pivot table report design based on metadata, but a rewrite of the design solved that problem.

I'd never recommend this approach for someone expecting several hundred or more concurrent users, but in smaller databases (tables < 1,000,000 rows) it is lightening quick.

As a single developer I could never have coded pages for all the applications we are currently supporting - this approach allows me to implement and support more applications per $ spent.





Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search