Haha, you know what they say, 'Too many databases, not enough cores!' But seriously, I think a combination of B and D would be the way to go. Define the resource limit per group and the maximum allocated storage. That should cover all the bases.
Hmm, I'm not so sure about that. What if the workload is CPU-intensive? Wouldn't it make more sense to define the maximum of CPU cores instead? That way, you can guarantee a minimum level of performance.
I agree, defining the maximum resource limit per group is a smart way to go. That way, the database can scale up as needed without hitting any hard limits. Plus, it gives you more flexibility to manage the resources efficiently.
Wow, this is a tricky one. We need to make sure the new IPSCustomers database can handle the workload demands, but defining the maximum of CPU cores seems too limiting. I'd go with option B and define the maximum resource limit per group of databases.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Misty
8 months agoAyesha
8 months agoGerman
8 months agoXochitl
8 months agoFarrah
8 months agoLyla
8 months agoTeddy
8 months ago