There are many changes in SQL Server 2005, especially for the SQL Server developer. New options, features, and changes in the way you program. New author M. Choirul Amri brings us the first in a series on the changes from the point of the developer.
Doug Reilly gives his personal perspective on the responsibilities of a cancer-surviving software developer.
One of our community is working on a thesis for his graduate degree on the effects of outsourcing on knowledge transfer among software engineers. He's got an anonymous survey setup, so if you have a few minutes, lend a helping hand.
Choosing a backup solution can be a trying exercise with all the various add on products these days. New author David Bird gives us some insight into his testing and decisions with a look at Litespeed and Tivoli's Storage Manager.
SQL Server 2005 has substantially enhanced its ETL capabilities, but many people will still be working with DTS in SQL Server 2000 for many years. New author James Greaves brings us a technique for working with imports and handling files that might not have any data.
Healthcare applications come and go, but data live on forever. We’ve seen that since the beginning of the computer industry; when we move from legacy systems into more “modern” architectures, we often leave behind applications, but we almost always take along the data into the future. Even though data are so important, we in health-IT don’t seem to spend the quality time necessary to structure our schemas and databases in such a way as to make it easier to maintain in the future. We often don’t design our data models solidly, and we don’t test them well by putting them through simulations or design them for multiple versions.
Are you mad? Not angry, more like crazy when it comes to designing databases in SQL Server? Don Peterson has met a few people he thinks are just that when it comes to building lookup tables. Does it stem from poor understanding of database design? Or do you disagree? Read Don's case against this particular design practice.
Gartner has stated in the past that "configuration management is at the very heart of IT service management." What do you mean by this?
There are a few upcoming SQL\SSIS\Developer events coming up in the next week. Andy Warren and Brian Knight will be speaking at Code Camp in Orlando (a free full day event) and Brian will be doing a SSIS event in Philadelphia. For more information, see this blog post.
You may be wonderfully up-to-date with an AJAX Web interface or the latest whizbang Windows user interface, but under the covers, you're probably still pumping data in and out of a database, just as we all did a decade or more ago. That makes it all the more surprising that developers are still making the same database mistakes that date back to those good old days of Windows 95 and before.
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Comments posted to this topic are about the item Where Your Value Separates You...
Comments posted to this topic are about the item Fixing the Error
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers