Sarvesh, I did not run the script, if it's running fine, why not put it under scripts section. Will be useful for future use as well. 😉

We were like studying backup/restoration and we forgot the main topic!!

Did you automate log shipping? I'm sure you're not running enterprise edition.

restore headeronly from disk='your backup file name'

This...

1. drop all connections by running alter database mydb set single_user with rollback immediate

2. select master database as active db and then run the query.

EDIT:- corrected query.

You can do stripped backup. Backup data will be written to two backup devices simulateneously.

backup database test

to disk='c:\test1.bak',

disk='c:\test2.bak'

2nd path can be your network path.

During restoration too, you...

You have got 2 records with T1 in transID column in trans table and 2 records in payment table. so joining the table on...

thang_ngo_2002 (6/22/2009)

---

OK, you are right.

Could you please show me the way to switch Standby DB from ReadOnly to main DB after apply LOG backup files

I try to uncheck "Read Only"...

allenjasonbrown (6/22/2009)

---

I am writing a query and it current looks like this:

select

cast(convert(decimal,a.totaltransactions) / convert(decimal,b.totaltransactions) as decimal (8,8))

from table1

I need to be able to add a 'NULLIF' because I currently get...

Dont you have a unique transaction ID on trans table? Joining these tables will produce double the number of records.

--============

create table trans

(

transid varchar(10),

transdate datetime,

status varchar(20),

userID varchar(20)

)

create table Payment

(

TransID varchar(10),

Payid int...

This article by Paul Ibison explains various methods to manage Identity Range in P2P...

Pls go through attached Microsoft whitepaper on P2P replication.

Thanks for sharing the solution 🙂

In transaction replication, identity column is automatically managed by the sql server. It allocates a range for publisher and different set of ranges for subsribers.

For p2p replication, you need to...

select collist into NewTable from OldTable is the right syntax.

Ref. http://msdn.microsoft.com/en-us/library/ms188029.aspx

Abhay, as rightly pointed by Homebrew01 in last post, you need to plan you restoration strategy carefully, based on which you should create your backup jobs.

First question that's asked is...