«

I was recently cautioned against storing an ADO.NET Connection String in the
Windows Registry because access to the Windows Registry would be serialized
and therefore impact scalability.

I have been able to find reasons to not use the Registry for storing
Connection Strings, but the reasons given seem to be security-related.

Does anyone know if there are performance-related reasons for NOT storing
Connection Strings in the Windows Registry?

Thanks!

I see your point. Even if there is serialization, you can work around it by
caching and refreshing the cache periodically. Thank you

I am still also trying to verify if this serialization will indeed occur.

"Aaron Lewis" <> wrote in message
news:%...
> Could just go ahead and use the registry to store the strings, then at
> runtime cache the value the first time you access it into the
application's
> cache... Could also use an expiration policy on the cache so that it
> re-loads the string from the registry every x minutes.
>
> "Gerard Marshall Vignes" <> wrote in message
> news:...
> > I was recently cautioned against storing an ADO.NET Connection String in
> the
> > Windows Registry because access to the Windows Registry would be
> serialized
> > and therefore impact scalability.
> >
> > I have been able to find reasons to not use the Registry for storing
> > Connection Strings, but the reasons given seem to be security-related.
> >
> > Does anyone know if there are performance-related reasons for NOT
storing
> > Connection Strings in the Windows Registry?
> >
> > Thanks!
> >
> >
>
>