Andrea is right. Try to share the common SQLEXPRESS instance if possible.
Consider that each instance consumes RAM. I agree with the admonition
against the User Instance approach. While it seems attractive, it's
expensive and must be fully understood before you commit to this strategy. I
discuss these strategies in my book.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva www.betav.com Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit
www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
[quoted text, click to view] "Bunert" <rizenbone@yahoo.com> wrote in message
news:e0xO8ogVHHA.2256@TK2MSFTNGP02.phx.gbl...
> Thanks. I like the analogy too :)
>
> I am new to SQL Express - does one generally have multiple SQL Express
> instances going like one did with MSDE when each app needed its own Or
> will SQL Express allow apps to coexist within one SQL Express instance?
>
> Thanks again!
>
>
> "William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
> news:uNEx8egVHHA.4796@TK2MSFTNGP05.phx.gbl...
>> Memory. Each loaded instance consumes RAM. Otherwise they should
>> peacefully coexist--kinda like lots of cooks in the kitchen. The bigger
>> the kitchen the fewer problems you'll have.
>>
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>>
www.betav.com/blog/billva >>
www.betav.com >
>