<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQLServerCentral.com
»
Editorials
»
The Log Shipping Standard
14 posts, Page 1 of 2
1
2
»»
The Log Shipping Standard
Rate Topic
Display Mode
Topic Options
Author
Message
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Sunday, April 11, 2010 8:28 PM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 3:30 PM
Points: 31,436,
Visits: 13,751
Comments posted to this topic are about the item
The Log Shipping Standard
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #901332
James Stover
James Stover
Posted Monday, April 12, 2010 1:16 AM
SSC Veteran
Group: General Forum Members
Last Login: Tuesday, October 30, 2012 10:37 AM
Points: 263,
Visits: 859
I'm a fan of log shipping. It's a hardened bit of technology that works very well.
Having said that, isn't it time to improve on the file-based transaction log? Maybe something in-memory with a delayed write to disk? My data-mart ETL would love this. C'mon Microsoft, you can do it!!
James Stover, McDBA
Post #901388
Tom Garth
Tom Garth
Posted Monday, April 12, 2010 6:00 AM
SSC Eights!
Group: General Forum Members
Last Login: Friday, February 04, 2011 7:20 AM
Points: 977,
Visits: 1,499
James Stover (4/12/2010)
I'm a fan of log shipping. It's a hardened bit of technology that works very well.
Having said that, isn't it time to improve on the file-based transaction log? Maybe something in-memory with a delayed write to disk? My data-mart ETL would love this. C'mon Microsoft, you can do it!!
Great idea! A CTRL-Z for us buffoons that occasionally forget that WHERE clause.
Tom Garth
Vertical Solutions
"There are three kinds of men. The one that learns by reading. The few who learn by observation. The rest of them have to pee on the electric fence for themselves." -- Will Rogers
Post #901506
Andy Warren
Andy Warren
Posted Monday, April 12, 2010 6:14 AM
SSCertifiable
Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462,
Visits: 1,384
I agree that the ability to inject some latency is valuable, probably used less often than it should be!
Andy
SQLShare - Learn One New Thing Each Day
SQLAndy - My Professional Blog
Connect with me on LinkedIn
Follow me on Twitter
Post #901520
brett.hawton
brett.hawton
Posted Monday, April 12, 2010 7:04 AM
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, December 07, 2010 2:06 PM
Points: 4,
Visits: 56
Hi Steve
A great suggestion and good use for log-shipping. As an ex-DBA I was often called upon to fix an "
oops
" and one does need to fix a way of rapidly correcting a problem rapidly.
It does seem though that much of the SQL community seems to be moving toward mirroring as a high-availability option and less log-shipping and only seems to be retaining log shipping for purposes of multiple recipients etc..
With a product like SQL Virtual Database (http://www.idera.com/Products/SQL-toolbox/SQL-virtual-database/) a DBA can take the previous backup together with any number of offloaded logs and create a virtual database back to any point in time. All of this without having to actually create a physical database (with all of the space problems etc.) The virtual database just uses the backups and logs as its "source" but to a SQL Server instance the virtual database looks exactly like a real database and TSQL can be run to, for example join the table as it was to as it is now the determine changes to be inserted/updated without even having to take the production database offline. As an example:
INSERT INTO TableA WHERE SELECT * FROM backup.TableA where NOT EXISTS (SELECT TableA WHERE…)
Brett Hawton
Idera Product Design
Post #901574
GSquared
GSquared
Posted Monday, April 12, 2010 7:53 AM
SSCoach
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 1:55 PM
Points: 15,442,
Visits: 9,571
Tom Garth (4/12/2010)
James Stover (4/12/2010)
I'm a fan of log shipping. It's a hardened bit of technology that works very well.
Having said that, isn't it time to improve on the file-based transaction log? Maybe something in-memory with a delayed write to disk? My data-mart ETL would love this. C'mon Microsoft, you can do it!!
Great idea! A CTRL-Z for us buffoons that occasionally forget that WHERE clause.
Any time you're running a script manually against a production database, you should ALWAYS wrap it in a transaction, and not issue the commit till you've verified the data is correct.
My usual practice is wrap and roll back, with verification scripts before the rollback. That way I can see what will be modified, without holding locks on tables/rows (which is what happens if you start a transaction and don't roll it back or commit it). Then, when I'm certain the script will do exactly what I need, I change the rollback to a commit, and run it.
If you're in that habit, a missing Where clause won't bite you.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #901615
noeld
noeld
Posted Monday, April 12, 2010 9:56 AM
SSCertifiable
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 4:39 PM
Points: 6,260,
Visits: 1,977
We have been using that for the past 5 years with the FAT FINGER case in mind!
* Noel
Post #901731
SQLRNNR
SQLRNNR
Posted Monday, April 12, 2010 10:10 AM
SSCoach
Group: General Forum Members
Last Login: Today @ 10:25 AM
Points: 18,754,
Visits: 12,337
I like the injection of latency into log-shipping. We could have used that in our implementation.
Jason
AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #901741
kevin77
kevin77
Posted Tuesday, April 13, 2010 11:31 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 9:18 AM
Points: 1,727,
Visits: 1,042
GSquared's comment is a good one, but I'm still waiting for Microsoft or someone else to write a plug-in that warns you if you try to execute a query without a WHERE clause. GSquared's method of being able to roll back is nice, but it still puts a lot of stress on the server if, for example, the table you were working on has 10 million rows and you forgot the WHERE clause.
Post #902642
GSquared
GSquared
Posted Wednesday, April 14, 2010 6:12 AM
SSCoach
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 1:55 PM
Points: 15,442,
Visits: 9,571
kevin77 (4/13/2010)
GSquared's comment is a good one, but I'm still waiting for Microsoft or someone else to write a plug-in that warns you if you try to execute a query without a WHERE clause. GSquared's method of being able to roll back is nice, but it still puts a lot of stress on the server if, for example, the table you were working on has 10 million rows and you forgot the WHERE clause.
In those extreme cases, you should be able to notice that the query is taking too long and cancel it.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #903039
« Prev Topic
|
Next Topic »
14 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
