SQL

On all of my databases, I cap the growth of the data and log files. I have not done my due diligence and performed capacity planning (Capacity Planning for SQL Server 2000 Database Storage), so I know I need to take those steps. I have been recent caught with a full database and I had to rush to expand it to keep the application up and running. Independent of the capacity planning process, I want to be able to monitor the database size and free space. Do you have a script that I can run to perform the checks on my SQL Server 2005 databases?


Additional Info


MSSQLTips.com webinars!

SQL Server Fragmentation - Fact vs. Fiction
Presenter: Chad Boyd
Sponsored By: Idera

Wednesday, October 17, 2007
4:00 PM - 5:00 PM EDT

Fragmentation - an often used word that is unfortunately also so often misunderstood. Fragmentation exists in multiple flavors, has different characteristics and effects on different types of data structures, and can be a major problem in some scenarios (also can be a non-issue at times as well). We'll discuss the different types of index structures, how and when they become fragmented (if they become fragmented), and when you should be concerned about fragmentation (and when not to be so concerned). We'll also be discussing multiple methods for monitoring and analyzing fragmentation, and discussing the different methods for removing fragmentation if appropriate.

DOTNET Framework 3.0

When speaking to developers about WinFX one question that repeatedly comes up is, “WinFX sounds great, but what happens to .NET?” .NET Framework has becomes the most successful developer platform in the world. Developers know and love .NET.The .NET Framework has always been at the core of WinFX, but the WinFX brand didn’t convey this. The WinFX brand helped us introduce the incredible innovations in terms of Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), Windows Workflow Foundation (WF) and the newly christened Windows CardSpace (WCS) formerly known under the codename “InfoCard.” The brand also created an unnatural discontinuity between previous versions of our framework and the current version.With this in mind we have decided to rename WinFX to the .NET Framework 3.0. .NET Framework 3.0 aptly identifies the technology for exactly what it is – the next version of our developer framework.The change is in name only and will not affect the technologies being delivered as part of the product. The .NET Framework 3.0 is still comprised of the existing .NET Framework 2.0 components, including ASP.NET, WinForms, ADO.NET, additional base class libraries and the CLR, as well as new developer-focused innovative technologies in WPF, WCF, WF and WCS.The .NET Framework 3.0 will still ship with Windows Vista, and will be available down-level for Windows XP and Windows Server 2003 as planned. This change doesn’t affect in any way the ship schedules of either Windows Vista or the .NET Framework 3.0 itself.We are confident that this change will go a long way towards reducing confusion people may have about our developer platform and the technologies in which they should invest.Namaste!

C# 3.0

Microsoft has announced the first details of the likely new features in C# 3.0. A technology called LINQ (Language Integrated Query) allows SQL, XML and object queries to be written in C# (and VB). To learn more about LINQ, please visit: http://msdn.microsoft.com/vcsharp/future/default.aspx LINQ and hopefully the other new features of C# are partly based on two Microsoft Research projects, C Omega and SpecSharp. Something similar happened with generics for C#2.0 - this was first released as the experimental GYRO project by Microsoft Research