Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sasan_vm
Yak Posting Veteran
51 Posts |
 Posted - 2009-10-07 : 02:13:35
|
| Hello,I seen 2 strategy in windows client/server application that use MS-SQL Server as RDBMS on server:1- client application installed on server on share folder and shortcut created on pc-client to access client application.2- client application installed on all pc-client.I use strategy 2 for a long time , but have question on benefit of strategy 1, and why ?Kind Regards,Sasan. |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2009-10-07 : 04:16:50
|
| This discussion has been a real pain in the a$$ for me...we haven't been able to find a proper solution to any of them. We first used #1, then #2 and now we don't really know what to do...luckily we only have 50 roughly clients so it's manageable. The benefits of #1 is that you only have the application in one place and deployment of new versions is usually pretty simple since all are using exactly the same files. The downside is that everyone is also using the same network resources and any network problems (minor or major) are bound to cause headaches. The applications (at least the ones I've tried) has a tendency to run a lot slower since it's relying on a network resource instead of a local resource. If you can get a decent distribution scheme going I'd vote for #2 to be my favorite.- Lumbagohttp://xkcd.com/327/ |
 |
|
|
|
|
|
Windows client/server application strategy ?