Skip to content

SQLGrease SQL Server Performance tips

Performance tuning tips from the SQLGrease team

  • Blog Home
  • About Me
  • Contact Me
  • SQL Grease 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

See how SQLGrease can help fix your deadlocks

 

Subscribe to our mailing list

* indicates required

Follow @sqlgrease

Recent Posts

  • Filtered indexes and the new parameter sniffing option (spoiler alert it doesn’t help)
  • Negative blocking session ids
  • Query store doesn’t work on read replicas
  • Improving performance of your RIGHT query
  • Improving performance of your LEFT query
  • Perform RTRIM and LTRIM in your code not in your queries
  • Performance of parameterized LIKE queries with new parameter sniffing option
  • Don’t use UPPER in WHERE unless you really need it
  • Estimate rows Vs Estimated rows to be read what’s the difference
  • Performance implications of using DATEDIFF function in WHERE
  • Performance implications of using ISNULL vs IS NULL
  • Connecting to a read only replica with SSMS
  • Index seeks on date and CONVERT
  • Fixing an implicit type conversion without a code change
  • Dealing With “Bad” Plans
  • Making Queries With Leading Wildcards Faster
  • Creating a database per customer VS single database for all customers (SQL Server)
  • What’s filling up tempdb?
  • Plan guides made easy
  • Tuning Substring Query Without Changing the Query
~