dbdmora (1/9/2013)
I have a developer that wants to create 4 different databases on a specific server that what technically seems for 1 app.ITApplicationSecurity
ITApplicationState
ITApplicationService
ITApplicationLogging
The same application will write to each database based on what function is performing. I told him it would be a better idea to create one database and schema out each function that the application will perform.
Developer came back saying that this design is to support multiple applications and separating the databases out will help with System performance.
Just another fact, the DB server they want it on already has 60+ databases. I just think four databases for 1 app is over kill.
Your thoughts?
Without more details it is hard to have a strong feeling one way or the other. However just given the names of the databases they all sound like a single table db???
Maybe a database named ITApplication with 4 tables?
Security
State
Service
Logging
Of course I would not allow table names that are that vague but that is sort of how I am reading it.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/