A Script A Day - Day 26 - RESTART a Database Restore
Today’s script is another one based on database restores. There is a little known clause of the RESTORE DATABASE command...
2012-02-29
2,810 reads
Today’s script is another one based on database restores. There is a little known clause of the RESTORE DATABASE command...
2012-02-29
2,810 reads
Today’s script is one I have used many times in the past to check for missing backups. The script will...
2012-02-29
3,454 reads
Today’s script is one I use as an example to explain that there is method behind my standards that some...
2012-02-28
1,500 reads
Today’s post is about the HAVING clause which specifies a search condition for a group or an aggregate. HAVING is...
2012-02-27
543 reads
Today’s script follows on from Day 16’s script which was about database restores. In a backwards way the script is...
2012-02-27
602 reads
Today’s script is one which saves me a lot of time on occasion. On large systems with lets say more...
2012-02-27
760 reads
Today’s script is to help replication performance. It was something I learned from my resident replication expert Paul Anderton. Below...
2012-02-25
3,305 reads
Today’s script will execute DBCC LOGINFO for all user databases. This is a script I use to monitor the number...
2012-02-25
2,623 reads
Today’s script is one I’ve taken from a job I use to collect possible poor indexes. I’ve tweeked it slightly...
2012-02-23
538 reads
Today’s script is something I’ve learned today, it’s cool learning new stuff! When viewing server configurations in the past I’ve...
2012-02-23
550 reads
By Steve Jones
fardle-din – n. a long-overdue argument that shakes up a relationship, burning wildly through...
The post Lukáš Karlovský: I got the green light from management and built Fabric...
By Steve Jones
I had mentioned some new T-SQL functions for SQL Server 2022 and a commenter...
Hey All, My setup is as follows: Table with Clustered Index on ID col....
I am having problems with CPU performance on SQL Server 2005. CPU spikes frequently...
I am having problems with CPU performance on SQL Server 2005. CPU spikes frequently...
What is wrong (if anything) with this code?
SELECT * FROM Sales.SalesOrderHeader AS soh WHERE customerid IN (SELECT soh.CustomerID FROM Sales.Customer AS c WHERE soh.CurrencyRateID = 1 ORDER BY c.ModifiedDate)See possible answers