Installing SQL Server
Because installing SQL Server is so easy it is tempting to cut corners, fail to plan properly and blindly accept default options without considering the alternatives.
2009-10-06
4,162 reads
Installation
12 Essential Steps After Installing SQL Server
Rolling out SQL Servers is a key task for DBAs, this articles provides 12 essential post-installation steps.
2009-08-03
7,255 reads
Prepare SQL Server 2005 in a Clustered Environment for SP3
This article from shows how to prepare your SQL Server 2005 clustered environment for Service Pack 3 and avoid some common problems.
2009-06-19
3,833 reads
Invalid SKU Error when Adding a Node to a SQL 2008 Cluster
When trying to add a node to an existing SQL Server 2008 cluster you get an Invalid SKU Error
2008-09-07
3,216 reads
All about the 'Case'
When installing SQL Server, regardless of versions and editions, SQL Server database administrators tend to choose the default collation and sort-order, which is SQL_Latin1_General_CP1_CI_AS. Though case insensitiveness makes the life of the database developers and database administrator's easy, there are situations where case sensitivity should be enforced just as password checking is enforced.
In this article, I would like to discuss different methods for achieving case sensitivity in a case insensitive database/server.
2005-03-25
2,616 reads
Building a Demo Server
Everyone does demos. Selling software relies upon people viewing your software in action and being confident it will work. Managing a demo server can be a challenge and this series will look at different problems and options you have.
2004-01-14
6,540 reads
Build a lot of DSN's in a hurry!
This article by Andy Warren offers a free utility that will generate DSN's for all or just a subset of the databases on a server in seconds.
2003-09-19
10,040 reads
Is Windows 2003 Really Faster?
Is Windows 2003 really faster for a SQL Server/IIS environment? Let us do all the leg work for you! We are about to upgrade the SQLServerCentral.com web and SQL Server from Windows 2000 to Windows 2003. As part of the case study, we are going to capture a baseline of the server's overall performance before the upgrade and then again after the upgrade. We will then document the experience and benchmark numbers.
2003-06-10
12,879 reads
Review of SQL 2000 Fast Answers
A monster book at 980 pages, it's written in 'how-to' format and has a ton of good material. Andy gave it the once over for us and reports back - see what he thinks!
2003-04-18
18,237 reads
SQL Server Upgrade Recommendations and Best Practices - Part 1
This article is the first of a multi-part series detailing the SQL Server Upgrade process from the technical, logistical and business perspective.
2003-03-03
10,484 reads
Blogs
Why Optimize CPU for RDS SQL Server is a game changer
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future
By DesertDBA
I haven’t posted in a while (well, not here at least since I’ve been...
Forums
FARE Labs Pvt. Ltd. is the best water testing facility in India.
Accurate water test results are provided by the Fare facility, an Indian water testing...
i noticed the sqlhealth extende event is on by default , so can i reduce
hi, i noticed the sqlhealth extended event is on by default , and it...
Looking for advice on improving SQL Server performance for a service management
Hi everyone, I’m looking for some guidance on a SQL Server performance issue I’ve...
Question of the Day
The Read Committed Snapshot Isolation behaviour
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers