Grant Fritchey (10/20/2016)
Brandie Tarvin (10/20/2016)
Lins,I think you misunderstand what Grant meant by cross-database querying.
If you separate out the data into individual databases, how many queries will have to touch these multiple databases to get their results?
If the answer is "a lot" or anything higher than... say... 20%, you should probably keep the data in one database. If the answer is very little, then by all means separate them. But cross-database querying isn't the same as cross-chatter. It's all about what data / tables / functions & procs the devs for each dataset project are utilizing.
I agree.
Although, if you have a discrete reporting area, or are making a discrete reporting area, that's a good reason to have a separate database.
Brandie: Ah yeah you're right, I think I did misunderstand the difference between Cross-Querying and Cross-chatter. (Both new terms to me tbh!). That makes me think that I should try to work out which objects / data both teams would be hitting. My feeling is that they're quite separate really, but there is overlap.
Grant: My plan would be to move reporting into a discrete area yeah. When you say "that's a good reason to have a separate database".. why is that? (I'm kind of asking for my own understanding and because I just know that management will ask me "But why is it better?"!