There are many changes in SQL Server with the release of SQL Server 2005, but none more telling than the client tool used to manage your servers. Check out this new e-book for learning about SQL Server 2005 Management Studio form SQLServerCentral.com.
It is an interesting question and one I hope every DBA can answer positively. New author Thomas LaRock brings us his method for ensuring that the backups have occurred and the files are still on disk.
One of the best programmers I ever met was referred to, in Essex jargon, as being ‘two stops short of Dagenham’ (Barking)*. This was once no obstacle to the world of work…the best development teams I’ve worked on embraced the whole gamut of humanity
Impressions of this new book from Brian Kelley.
Security support in the .NET Framework got a lot of love in version 2.0, and this column is going to take you on a whirlwind tour of the goodies you'll find there. I won't be able to cover everything, but you'll know where to start looking to stay on top of the new changes. I'll take this a namespace at a time.
Every DBA needs a few tricks up his/her sleeves to help them better manage their SQL Server 2000 environment. In this article I will explore a couple of such tricks. I will first explore how to cycle the SQL Server error log, and why you might want to do this. Secondly I will discuss backup history information and why you would need to periodically remove some of the older history information.
Are you thinking about consolidating your SQL Servers on to fewer machines? It is an interesting idea and one that is definitely more possible with SQL Server 2005 and 64-bit servers. Steve Jones takes a look at some of the pros and cons of moving to fewer servers.
Excerpted from Brian Larson's book Microsoft SQL Server 2005 Reporting Services 2005, this chapter will help you build a table report and matrix report without the use of the Report Wizard, and it will discuss two new report types -- the chart report and the list report.
One of the big complaints in SQL Server development has been error handling. SQL Server 2005, however, substantially enhances its capabilies in this area and Leo Peysakhovich brings some code that provides a template for adding error handling to your application.
One advantage of CLR assemblies is the ability to consume web services from within the database. This wouldn’t be easy with T-SQL, and would also require a lot of work in an unmanaged extended stored procedure. With .NET, it’s almost as simple as accessing a local DLL. There are just a couple of extra command-line utilities we need to run to be able to access web services from within a SQL assembly:
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Hi everyone I am looking at building a query to determine how much time...
Comments posted to this topic are about the item SQL Server Transactional Replication from...
Comments posted to this topic are about the item Hidden Heroes
When thinking of the Identity property for auto incrementing columns and sequences for the same action, which are explicitly linked to increment a number in a table when a new row is added?
See possible answers