Mike Pearson


SQLServerCentral Article

Recovery Planning For SQL Reporting Services

SQL Server 2000 Reporting Services is becoming a more and more popular reporting option everyday. However, the disaster recovery plan for this add on is not a simple backup and restore since there are multiple pieces and servers usually involved. However the DBA may be responsible for the entire system. Mike Pearson brings us a look at some of the scenarios that you need to consider and what you might need to prepare for disaster recovery of SQL Server 2000 Reporting Services.

(4)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

29,299 reads

SQLServerCentral Article

Review: SQL Auditor

How solid is your SQL Server database design? Will it perform well in practice? SSW has a product, SQL Auditor, that compares your design against a number of well known design rules and gives you reports based on how well your design does. Read Mike Pearson's review of this product.

(1)

You rated this post out of 5. Change rating

2004-09-06

5,806 reads

SQLServerCentral Article

Review of ApexSQL Report v4.3

We had Mike take a look at this product recently and he found a lot to like. He also had some suggestions about ways the product could be improved - interesting since you get free upgrades for life with this product. This is a very good walk through of the product.

You rated this post out of 5. Change rating

2004-03-12

4,810 reads

SQLServerCentral Article

Changing Rogue Database Collations

Collations hard to sort out (I know, bad joke)? Mike did what a good DBA gets paid to do, figure out an easy way to fix something and remove the chance of a user mistake at the same time. Good explanation and a couple scripts show how to handle column level collations.

You rated this post out of 5. Change rating

2003-05-26

12,775 reads

Blogs

Advice I Like: Art

By

Superheroes and saints never make art. Only imperfect beings can make art because art...

Why Optimize CPU for RDS SQL Server is a game changer

By

One feature that I have been waiting for years! The new announcement around optimize...

Performance tuning KubeVirt for SQL Server

By

Following on from my last post about Getting Started With KubeVirt & SQL Server,...

Read the latest Blogs

Forums

The AI Bubble and the Weak Foundation Beam

By dbakevlar

Comments posted to this topic are about the item The AI Bubble and the...

data type gets lost in data flow

By stan

Hi, in a simple oledb source->derived column->oledb destination    data flow, 2 of my...

i noticed the sqlhealth extende event is on by default , so can i reduce

By rajemessage 14195

hi, i noticed the sqlhealth extended event is on by default , and it...

Visit the forum

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;
go
Then, 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