Question : Splitting db and performance

Experts,

It seems as though the performance slows once you split the db?  This is in comparison to db without spliting.  Are there advantages in splitting vs not splitting?  Is it advisable for all users (around 3) to use on the network and not split?  I am guessing that if the users dont have the front end on their computer then there might be issues with forms and reports because maybe another user could be on teh same form and makes a data change.  I know that the typical setup is to have a front end on each users computer and have backend on the network.  

Thank you

Answer : Splitting db and performance

You can do this but, in Reporting Services Configuration but, you will have to reset all the connection strings on your shared data sources and every report that has a data source of its own. If you have more than 20 reports this will be a large project. If you don't reset the passwords reports and scheduled reports will fail to be delivered or generated on the fly.

If you do this back up the key after you reset it and place that *.snk file some where on the server where you will find it again to restore from the key. I usually back up the key as the name of the service account that runs SSRS. svc_SSRS_agent.snk and use the password for the service account as the password for the key. The password for the account that SSRS is running on should not be changing frequently or you will have to do this again.