Yes, you are right, Telerik Data Access
has a context constructor that allows you to provide a connection string. In order to switch the connection string during runtime, once you have resolve the connection string, being from a settings files or somewhere else, you can pass it to a Telerik Data Access
context. Please refer to this documentation article
for further information on how to initialize Telerik Data Access
Alternatively, if your connection strings are known in advance, you can store them as separate connection string entries in the connection string section
of the web.config/app.config
of you application and let Telerik Data Access
resolve them for you. In order to achieve that, you can use the same constructor, but instead of passing a connection string - pass the name of the connection string as specified in the web.config/app.config. This will instruct Telerik Data Access
to read and use the connection string matching the passed name.
Additionally, are you targeting the same database server always? If not, you may be interesting in this documentation article
which describes how to achieve support for multiple backends.
I hope this is helpful. Do get back to us with any further questions.
Check out the latest announcement
about Telerik Data Access vNext as a powerful framework
able to solve core development problems.