2015-04-14
1,795 reads
computed columns
2014-04-30
1,954 reads
2013-11-15
2,007 reads
2013-01-31
2,299 reads
A Computed Column Defined with a User-Defined Function Might Impact Query Performance
A benefit of using computed columns is that they can save developers from having to write calculation logic at the application layer; at the table level, the application can simply reference the computed column. In addition, performance can be improved by persisting a computed column and building an index on it.
2012-02-03
2,708 reads
2012-01-31
2,363 reads
2010-09-30
2,936 reads
2010-07-21
4,081 reads
Blogs
Don’t Miss Out – SQL Server 2025 Unleashed Training Starts Next Monday!
Next Monday, March 9, 2026, my one-day live online training SQL Server 2025 Unleashed:...
What is ALM in Fabric?
By HeyMo0sh
As someone who’s worked with data for over 20 years and with many cloud...
The Most Successful Startups in 2025 — And What They Have in Common
By HeyMo0sh
2025 belongs to the AI startups. If you peek into the tech headlines, you’ll...
Forums
A Quick Restore
Comments posted to this topic are about the item A Quick Restore
Guarding Against SQL Injection at the Database Layer (SQL Server)
Comments posted to this topic are about the item Guarding Against SQL Injection at...
Ola Hallengren Index Optimize Maintenance can we have data compression = page
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
Question of the Day
A Quick Restore
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers