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:
SQL Server 2000 has a rock solid backup scheme , but do you really need to run full backups every day? What if you could decide on the fly if it was more efficient for a full or a differential backup? Darwin Hatheway brings us the basis for a scheme that can predict the size of a differential backup by examining how much of the database has changed.
Server 2005 now supports a more programmable error trapping convention in T-SQL code. This error handling is known as the TRY/CATCH block. The TRY/CATCH block allows T-SQL to handling errors like other programming languages, such as Microsoft Visual C# and C++. In addition to the TRY/CATCH block, Microsoft has expanded the set of available system functions in SQL Server 2005 for returning error codes and messages when an error occurs in your T-SQL code. This article will explore the new TRY/CATCH block and explain the new system functions for returning error codes and messages.
By HeyMo0sh
DevOps is about shortening the system development lifecycle. Plan faster, build faster, test faster,...
A short blog post about an issue with Fabric Mirroring (with Azure SQL DB...
By Steve Jones
I wrote an article recently on the JSON_OBJECTAGG function, but neglected to include an...
Comments posted to this topic are about the item PostgreSQL String Functions Part 1
Comments posted to this topic are about the item Working Better Under Pressure
Comments posted to this topic are about the item Identities and Sequences V
When thinking about the identity property and sequence objects, which of these can generate values before an insert statement is executed?
See possible answers