Skip to content

SQLGrease SQL Server Performance tips

Performance tuning tips from the SQLGrease team

  • Blog Home
  • About Me
  • Contact Me
  • SQLGrease Home Page

architecture

Creating a database per customer VS single database for all customers (SQL Server)

August 24, 2020January 30, 2022 ~ franklinyamamoto

With so many applications being built as SAAS offerings, an important decision that must be made when defining the data architecture is:  Should each customers’ data be in a separate database, or can a shared database (keyed by a customer identifier) be used for all customers. Pros of database per customer There’s a variety of […]

Read More

Subscribe to our mailing list

* indicates required

Follow @sqlgrease

What are you waiting on?

Recent Posts

  • How CURSOR processing logic shows up in Query Store
  • Using GO in SSMS versus not – what is the difference
  • Unmatched Indexes plan warnings
  • No Join Predicate plan warning may be a red herring
  • Parallel plans can be selected with scalar UDF’s
  • What’s my parallel query waiting on?
  • Improving performance of SUBSTRING queries
  • Execution plan shortcuts causing random long executions
  • SQL Server compile locks
  • Are you searching for a Precise I3 replacement?
  • How to measure query runtime when developing/testing – part 3
  • Deadlock graphs now contain query hashes
  • RESOURCE_SEMAPHORE waits caused by OBJECTSTORE_LOCK_MANAGER memory usage
  • Opening an actual plan in a separate SSMS tab
  • How to measure query runtime when developing/testing – part 2
  • How to measure query runtime when developing/testing – part 1
  • OLEDB waits: what they mean and a few ideas on addressing them
  • STATMAN queries causing you timeouts?
  • What does the status column of a session mean in SQL Server?
  • Query store queries losing forced plans
~