Transactions in SQL Server can be very complicated, and are often misunderstood. Don Peterson brings us part 2 of his series on transactions. This part deals with XACT_ABORT, compilation errors and error handling in transactions.
Over the last few years, corporations have invested billions of dollars to integrate the automations of core business systems in large ERP applications. This paper looks at the risk of downtime and solutions for building an around-the-clock database.
Mattias Fagerlund, a longtime author and contributor here is developing a new product to help developers migrate between versions of their databases. He's searching for a few Beta developers to assist.
SQL Server has a great build in messaging system with SQLMail. Unfortunately it requires Outlook and Exchange to work properly. Some people don't like this or do not run Exchange and have issues getting it to work. Gregory Larsen takes a look at how you can use SMTP to send email from SQL Server.
E
very day a developer somewhere needs to write code to iterate through SQL Server™ system objects, query and update tables in linked servers, handle optimistic concurrency, and retrieve column and stored procedure metadata. In this month's column, I will address these and other T-SQL development scenarios based on some of the questions I most frequently receive from readers.
How prepared are you for your next interview? How prepared are you to give one? SQLServerCentral.com has compiled a number of questions from our ever popular Question of the Day into a book. Read about the project and show your support today by picking up a copy.
There are plenty of good sources of information about how to deploy SQL Server in a secure fashion. However, these resources are often targeted at database administrators tasked with securing already developed applications. In addition, there is a rich body of information that discusses writing secure .NET and ASP.NET code, including .NET code that accesses SQL Server. However, many of these resources focus on the data access code that runs on the application servers rather than the Transact-SQL (T-SQL) code that executes within SQL Server. Developing T-SQL code that runs securely on SQL Server is the primary focus of this column.
Andy started a contest this summer to see who could develop a T-SQL method of keeping a bowling score. He's finally gotten around to the results after the damage from the hurricanes was cleaned up. See who won and see the code that does the trick.
One of the biggest performance gains built into SQL Server is the stored procedure. In this article by Brian Kelley, he shows you how to fully utilize, debug and monitor the caching of such objects.
A common requirement when building a data warehouse is to be able to get all rows from a staging table where the business key is not in the dimension table. For example, I may want to get all rows from my STG_DATE table where the DateID is not in DIM_DATE.DateID.
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