Spotlight on SQL Server
After a bit of a hiatus, the interviews are back. This time we take a few minutes with Dan Jones of the SQL Server development team.
After a bit of a hiatus, the interviews are back. This time we take a few minutes with Dan Jones of the SQL Server development team.
Testing is key to ensuring a process actually works when it comes time to implement, rather than finding out when time may be of the essence. This holds true for testing SQL Server restores as well.
Joe discusses why he prefers command line tools over GUI, then launches into a how-to about querying sysperfinfo to resolve performance issues. Couple nice sample queries included!
If you deliver applications to a customer, then you have struggled with the challenges of updating schemas as they change. New author Serhiy Snisarenko brings us his comprehensive process and code to make this task easier.
A SELECT query returns results as a rowset. You can optionally retrieve formal results of a SQL query as XML by specifying the FOR XML clause in the query.
The second part of a great data warehousing series from Vincent Rainardi looks at the decision to stage data prior to moving it into the warehouse versus directly loading it. This is a must read for those contemplating a data warehouse.
Throughout our series of articles dedicated to SQL Server 2005 Integration Services, we have been working mainly with packages using the Business Intelligence Development Studio interface (although more recently, we also discussed SSIS-related functionality available in SQL Server Management Studio). Even though, as part of our exercises, we have worked with a number of packages, we have not yet explored the various options related to their storage. We will cover them in this article
One thing that many people tried to implement in SQL Server 2000 is the auditing of logins. However getting this to work was a complex process. In SQL Server 2005, however, there are a few ways you can handle this and new author Frederik Vandeputte brings us a method using Service Broker for handling this.
In SQL Server 2005, you can explicitly or implicitly define the execution context. As we all know, a session starts when a user logs on to SQLServer or a connection to SQLserver is made. All operations in that session use the logon credentials used for connecting to SQL Server. When an EXECUTE AS statement is run, the execution context of the session is switched to the specified login or user name.
Have you started looking at what issues you might have migrating your existing applications to SQL Server 2005? If not then maybe as a first step, you should consider looking into what the SQL Server 2005 Upgrade Advisor can do for you. This article will discuss what the Upgrade Advisor is and how to use it.
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
By Brian Kelley
If you don't have a plan, you'll accomplish it. That's not a good thing.
By Steve Jones
Today Redgate announced that we are partnering with Bregal Sagemount, a growth-focused private equity...
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