Having been at the sharp end of many successful SQL Server solutions, I believe there are some fundamental principles that all successful SQL Server installations have in common. Whilst the challenges in delivering an enterprise-scale database-intensive application can be wide and varied, there are a few basic practises that will give you the best possible chance of success.
2007-04-05
2,570 reads
Here's the scenario: 1. You have been given a script to run.2. You do not know the database name.3. You know which server.Substitute the word "TABLENAME" with the table name in the script and run in query analyzer. This query will check every database on the server and return the name of the database with […]
2007-04-26 (first published: 2007-04-04)
480 reads
Importing data files is always a challenge for a DBA, especially when the files might vary in format. Having one codebase is important and new author Mark Balasundram brings us the template for a high performance application to do just that.
2008-03-13 (first published: 2007-04-04)
17,528 reads
In the previous articles, Jacob Sebastian looked at using XML to save a sales order with variable numbers of line items to a SQL Server
2000 database. In this part, he expands upon the processing to access that data from multiple nodes.
2007-04-03
7,146 reads
Dice.com recently completed a salary survey for 2007. If you didn't participate, Steve Jones summarizes the results for DBAs.
2008-03-24 (first published: 2007-04-03)
10,148 reads
I regularly use SQLIO.EXE to gauge the maximum throughput a disk subsystem can sustain. Recently Microsoft released SQLIOSIM.EXE to provide better results for this type of test. However they didn't release any documentation on the tool and I could never figure out what it was trying to tell me. It looks like they finally did release a Knowledge Base article on SQLIOSIM. Give it a spin. I'd be curious to hear what you think of the tool.
2007-03-30
2,768 reads
In part 2 of this series, Jacob Sebastion continues looking at XML in SQL Server 2000 with some advanced XML processing.
2007-03-29
7,711 reads
The script details about the workaround for using Dynamic SQL inside T-SQL user defined functions. Basically, T-SQL doesn't allow developers to perform/write any actions/statments which would affect the database's state. As a key note factor for any migration process from oracle to sql server developers need to do a work around on using execute immediate(for […]
2007-04-18 (first published: 2007-03-27)
4,071 reads
How many times have you tried to save a sales order to your database? For many DBAs this is a common scenario and one of the challenges is the many round trips for the various line items. Jacob Sebastian brings us the first part of a four part series looking at how you can use XML to reduce the round trips in SQL Server 2000.
2007-03-27
12,898 reads
SQL Server 2005 has greatly expanded the XML capabilities of this platform, but should you use it in your database? New author and
MVP Simon Munro brings us a look at how he has used XML and where it might fit in your database.
2008-03-11 (first published: 2007-03-26)
6,266 reads
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Short version You want to get this running as fast as possible. Do these...
I changed my email address in Edit Profile page, but it has no effect...
Comments posted to this topic are about the item The case for "Understanding our...
Comments posted to this topic are about the item Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers