Webcast: Basics of Administering Databases for The Layman – Part 3
Okay, so you’ve gotten your data into your database. Did you do it right? Do you have too much data? Do you have the right data? Can you actually get the data out that you want? Now how do you get it out? This session will take you through some examples of why you want to have less data in a database to be more accurate (normalization), how that’s done, and how it makes the data in your database more accurate. It also explains why, in certain circumstances, it could be beneficial not to do that. Topics included will be indexes: what, why, and how to use them, what the benefits are, what the tradeoffs are. Also, different ways to maintain them and why you want to do that, and why some of Microsoft’s canned maintenance plans can be a problem and where to look for solutions to those problems. Presented by: Tom Roush
> Register Now
> Live date: 4/21/2010 at 12:00 Pacific
Featured Script
dba3_Identity_Value_RollBack_Skipping_demo
Identities do not guarantee gap free incremented row values… (read more)
Tracking Your Servers
We’ve been working through DBASchool this week and having a blast (http://www.vconferenceonline.com/dbaschool). One of the things we’ve been talking about is inventorying your servers, keeping track of configuration elements and the like.
I thought I’d toss this out to you – what items do you keep track of on your servers? The things covered thus far are server name, ports, essential server configuration elements like disk sizes, memory, CPUs, etc. The goal is to find a common set of information that you gather as an initial starting point with your server, so you have a good idea about what the box is capable of and what your overall utilization is like.
So, what elements do you look for and record? Remember, this isn’t so much stats from performance monitor as it is information that helps you understand what a box is all about.
What do you think? Drop me a note – let me know.
Are You Concerned?
Not like "holy cow we’re in deep trouble" kind of concerned, but just "hmmm…." concerned. Are you concerned about the coming release of SQL Server, the emphasis on BI and the tools that are both available now and that will be available for extracting information, reporting on it and the like?
I find myself less concerned than I have been, but it comes from looking to attach more controls to information coming from the systems. I think the tools are solid for doing that and I think it’ll be necessary going forward. BUT – I thought I’d ask you – does the openness of data, the ability to extract, modify and report on information – do these concern you or do you see things as more of a movement to "that’s the way it is, we have to provide the security to make it work correctly and safely"?
You guessed it – let me know your thoughts – drop me a note here.
Webcast: SQL Server Forensics
Have you ever received a call from one of your users asking why they received an error 3 days ago? Or maybe they want to know when a particular piece of data was deleted and who did it. Troubleshooting past events is difficult in SQL Server, but not always impossible. Learn how to set up a SQL Server to be able to respond these questions and how to use resources within SQL Server and other application logs to track down activity that otherwise might be lost. Presented by: Sarah Barela