Limitations of EA hosted on SQL server

[nara_c]

Does anyone know the limitations or problems of hosting a single EA repository on a SQL Server within a corporate LAN?  
- What are the maximum suggested concurrent users?
- Max recommended size of DB
- Any known issues?

Thanks for your help!

[Bruno.Cossi]

Hi,

I think that answers to all of your question are driven more by SQL Server itself and less by EA. I have seen implementations of EA with SQL Server based repository with dozens of users (not sure about the number of concurrent users, but can get that information, if you need it). Size-wise, even a huge model by EA standards is still going to be small by SQL db standards, I have not come across an instance where the db size would be an issue.
I have some issue with the shared repository functionality in general, but none related to SQL server in particular.

Hope this helps!
Bruno

Does anyone know the limitations or problems of hosting a single EA repository on a SQL Server within a corporate LAN?  
- What are the maximum suggested concurrent users?
- Max recommended size of DB
- Any known issues?

Thanks for your help!

[nara_c]

Thanks for your response Bruno!  Sure gives me more confidence to give it a go and see how it proceeds.  

Hopefully my backup strategy of baselining & Version controlling using CVS should minimise any risks

Cheers

[Bruno.Cossi]

Happy to inspire such confidence :-) Just out of curiousity, how many concurrent users are you looking at?

Bruno

[nara_c]

Not sure at this point since we are still in the proof of concept stage.  

The IT solutions team is around 200 resources and I am guessing it could peak to around 50 concurrent users since the BAs will always be documenting requirements & Use cases in the Shared EA repository while the Development team will be updating models.

In fact it could be more since this could become the central team in case even the testers document their test cases in EA.  Then the primary working tool for BAs & Testers will be EA and Developers may use it around 20% of the time with peaks during initial project phases.

As I said above these are all just guesstimates  

Will know following the proof-of-concept stage once the various team resources are able to critique the suitability of the tool for their work.

[Bruno.Cossi]

That's not dissimilar to one of the implementations I saw recently (I think the number of concurrent users was around 40) and no performance issues whatsoever.
A few issues with security (as per the thread above), but I am still hopeful this will be improved in the build... or the next one...

Bruno