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.
By Steve Jones
I love Chicago. I went to visit three times in 2023: a Redgate event,...
By Brian Kelley
I have found that non-functional requirements (NFRs) can be hard to define for a...
You can find the slidedeck for my Techorama session “Microsoft Fabric for Dummies” on...
Hi, I have SQL Server 2019 installed and when go the Clear Trace database...
Hello I need to get txt files from directory and send email, when I...
Hello, I have a question regarding Availability group server architecture. A little background: We...
Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:
create table t1 (id int primary key, city varchar(50)); insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);If we execute the following query, how will the records be sorted in both environments?
select city from t1 order by city;See possible answers