Brian Knight has started a new series base on his impressions of SQL Server 2005, Beta 2, aka "Yukon". Read about his first impressions of the product as he starts down the path of learning about the next version of SQL Server.
Are you familiar with using the Command object in ADO? If so, migrating to ADO.NET should be a snap.
The 2004 premier SQL Server event, the PASS Summit is coming to Orlando in September. Once again we'er working with PASS to sponsor and promote this event. Read Steve Jones' take on this event and why it's worth your time and your company's money.
The second part of the series by Darren Fuller on SQL Server change management, version control, and ways that you can automate this approach. If you do any type of SQL Server development, having a version control system is key to ensuring stability and keeping to your deadlines. Whether you agree with this approach or not, it's good information to have.
Developing applications for SQL Server usually results in a variety of access methods that the programmers use. A data access layer class, given to the developers, is usually seen as the best practice, but one that isn't usually implemented. In fact, in most software I've built, each developer uses his own method, or may cut and paste from another, but rarely is there a central access class. New Author Patryk Nowakowski brings us his solution using ADO.NET.
Automating SQL Server tasks is the sign of an experienced DBA. One who doesn't waste time on repetitive tasks that can be easily setup in a job, task, or some other scheduling process to run when they need to run. Haidong Ji has written a number of articles on how to perform automation and brings us yet another technique. This time he looks at managing your backup files, something that we all need to do, but all too often forget to do.
Murphy's law has struck us all, as evidenced by the disaster entries we've received in the past. Imceda software, makers of Litespeed are sponsoring a new contest, looking for your nightmares.
NGS Software is in the security business and have been very successful in finding vulnerabilities in many products, notable SQL Server. They have used their expertise to build products to help you better secure your systems. Dale Corey looks at one of those products, NGSSquirrel, which does vulnerability assessment.
What do your programmers do with nulls? Do they know nullif, isnull, what about the powerful coalesce function? Do they think DBA's look at the world differently? Why, it's all code isn't it?
SQL Server change management is tough. The tools don't integrate with version control systems, there isn't good administrative controls to enforce control, and often you need to buy a third party tool to make this work. New Author Darren Fuller takes a look at the various ways in which you can implement version control in SQL Server. This is part one of a four part series on version control in SQL Server.
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