Connection Strings in the Windows Registry --- Performance?

[Gerard Marshall Vignes]

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!

[Gerard Marshall Vignes]

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" <aaronlewisSPAMFREE@guildportal.com> wrote in message
news:%23EYdMuTUDHA.3796@tk2msftngp13.phx.gbl...

> 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" <programmer@gerardvignes.com> wrote in message
> news:u55EspSUDHA.2036@TK2MSFTNGP10.phx.gbl...

> > 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!
> >
> >

>
>