Where should SQL Server go in the future? Steve Jones continues to explore his wish list for future versions of SQL Server. This article looks at an area where much improvement is needed: the index tuning wizard.
Jon has been off in the land of C# and web apps for a while, but a recent project has him investigating OLAP and then coming up with a custom solution that met his needs. Jon helped us get this site off the ground, good to have him back for a guest appearance!
Troubleshooting performance problems takes a lot of time and work. This article outlines the process the author uses - pretty interesting.
This month Robert covers the process he uses for developing stored procedures. In many ways it reflects how software is developed, but it does have it's minor differences. This is a high level process discussion, not a line by line example of the entire process - by design of course.
Where should SQL Server go in the future? What enhancements are needed? Steve Jones takes a break from his wishes to include some feedback from users who have some wishes of their own. Read about what real users of SQL Server would like to see included in future versions.
Stateless programming can be tricky... In case you ever need to return a specified subset of a query without first returning the entire recordset, here's a method.
The second article in a 3 part series that presents another VBScript class file that creates a class that can be used to display the backup information from a SQL server's maintanence plans.
Where should SQL Server go in the future? Steve Jones continues to explore his wish list for future versions of SQL Server. This one examines an enhancement that could speed up some of your queries by enhancing the index structures.
Joe Sack returns (is back?) with some scripts you can use to log information you may need when disaster strikes.
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