There are times when you may find yourself needing to drop many tables in your database but not all. Some criteria defines what must go. It could be archived tables, tables before or after a certain date time stamp, dummy data tables, etc.
Let’s look at 2 simple methods for dropping lots of tables in your database.
On Saturday April 27th I’ll be speaking at SQL Saturday Raleigh. I am excited to be presenting a lively and practical session about Environmental SQL Server Troubleshooting.
When called in to diagnose a performance issue what are the 1st things you review? Many DBAs and developers make the mistake of diving straight into the code looking for an answer. However, often times the solution is not in the code but rather in the overall environment.
Environmental troubleshooting is often a quick and overlooked method for discovering and configuring SQL Server to perform at a higher level without the need for application change controls.
In this session we will discuss both performance pitfalls and optimizations that can be made to the system outside of code changes. We will diagnose configurations commonly misapplied and review best practices in SQL Server, Windows Server, and VMware!
If you want a preview of the talk and some supplemental info please look at these:
The topic for this months T-SQL Tuesday #113 hosted by Todd Kleinhans (Blog / Twitter) is about “what do YOU use a database for”. We work all day, night, and weekend sometimes on our database craft. Todd asks:
So what do you use databases for in your personal life that you are willing to share?
The topic for this months T-SQL Tuesday #112 hosted by Shane O’Neill (Blog / Twitter) is about “dipping into your cookie jar”. This reference means “when times get tough how do you dip into your reserves to keep going”. Shane asks the following:
That is what I want from the contributors of this T-SQL Tuesday, those memories that they can think back on for sustenance. Like the humble cookie, I want a humble brag.