A SQL Server Hardware Nugget A Day – Day 14
Since 2006, Intel has adopted a Tick-Tock strategy for developing and releasing new processor models. Every two years, they introduce...
2011-04-14
603 reads
Since 2006, Intel has adopted a Tick-Tock strategy for developing and releasing new processor models. Every two years, they introduce...
2011-04-14
603 reads
For Day 13 of this series, we will cover Intel Turbo Boost Technology. This is not like the the old...
2011-04-13
503 reads
In Day 12 of this series, we will be talking about AMD Opteron Processor Numbering. Advanced Micro Devices (AMD) has...
2011-04-12
749 reads
I have added two new queries to this month’s version, to try to collect some more hardware information about the...
2011-04-11
497 reads
For Day 11, I want to talk about the new processor numbering system for Xeon processors that Intel introduced on...
2011-04-11
378 reads
Wow, we are 1/3 of the way through this series! Today’s post is “Classic Intel Xeon Processor Numbering Explained”. By...
2011-04-10
359 reads
For Day 9 of my SQL Server hardware series, I want to give my current recommended AMD Processor List for...
2011-04-10
596 reads
For Day 8 of my SQL Server hardware series, I want to give my current recommended Intel Processor List for...
2011-04-08
422 reads
I will be presenting my Dr. DMV presentation for the St. Louis SQL Server User’s Group on April 19. Here...
2011-04-07
1,131 reads
For Day 7 of this series, I will talk about the incredibly useful CPU-Z utility, which is available for free...
2011-04-07
1,308 reads
By Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
By Vinay Thakur
continuing from Day 1 where we covered the history of AI and GPT family,...
By Steve Jones
It’s a day off for Redgate today. This is our annual wellbeing day, where...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
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