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
TempDB Internals – What’s New (SQL Server 2016 to 2022)
By Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
Blog a Day – Day 2: Generative AI, Multimodal Systems, and Agent AI
By Vinay Thakur
continuing from Day 1 where we covered the history of AI and GPT family,...
A Wellbeing Day at Redgate
By Steve Jones
It’s a day off for Redgate today. This is our annual wellbeing day, where...
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