Hi there, was just wondering...
I setup database replication , creating a publisher and a subscriber....
all seemed to go well.
Anyway, my question is... Can Log Shipping be setup accidently while doing
this process? I know nothing
about log shipping.. and someone is trying to point blame on me for creating
'Log shipping'.
Is it possible that I could have created log shipping without even knowing..
or does it require a bit of know how.
Also... if Log shipping was setup... Does it run automatically?
And last but not least.. If it was setup, and the standby server was turned
off.. and not running... Would log shipping run?
Sorry about my ignorance.. but I have a feeling the people who are making
these accusations are out to create / pass blame across to poor old me for
their own mistakes.
thanks in advance everyone
-Simon
That depends. On SQL Server Enterprise Edition and Developer Edition it is
conceivable that someone could blunder their way through the wizard being
totally ignorant about what they are doing. However most noobs would get
scared and back out of the dialogs pretty soon fearing they were doing
something destructive.
On other editions log shipping requires significant "programming" and the
chances of setting it up unintentionally are very remote.
It is possible that you scheduled transaction log dumps which are an
important step in log shipping (but only the first step and not the only
step). This can be done using the maintenance wizard.
All in all its pretty remote.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Simon" <none@.none.com> wrote in message
news:deeKf.12140$yK1.10202@.news-server.bigpond.net.au...
> Hi there, was just wondering...
> I setup database replication , creating a publisher and a subscriber....
> all seemed to go well.
> Anyway, my question is... Can Log Shipping be setup accidently while doing
> this process? I know nothing
> about log shipping.. and someone is trying to point blame on me for
> creating 'Log shipping'.
> Is it possible that I could have created log shipping without even
> knowing.. or does it require a bit of know how.
> Also... if Log shipping was setup... Does it run automatically?
> And last but not least.. If it was setup, and the standby server was
> turned off.. and not running... Would log shipping run?
> Sorry about my ignorance.. but I have a feeling the people who are making
> these accusations are out to create / pass blame across to poor old me for
> their own mistakes.
> thanks in advance everyone
> -Simon
>
>
|||Hi Hilary, Thanks very much for your response.
If it was in my error, Would there have to be transactions in the
msdb.logshipping_primaries / secondaries table on the standby server to show
that Log shipping actually took place?
Where on the stanby server could I check history of Log shipping taking
place.
Thanks in advance once again
P.S. They have already 'supposedly' turned off Log shipping on the primary
machine... but the 'accused' standby machine hasnt been connected to the
network for months.. so if log shipping did take place months ago before it
was removed from the network, would I be able to check its history some how.
Thanks again
-Simon
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ueq2k1fNGHA.984@.tk2msftngp13.phx.gbl...
> That depends. On SQL Server Enterprise Edition and Developer Edition it is
> conceivable that someone could blunder their way through the wizard being
> totally ignorant about what they are doing. However most noobs would get
> scared and back out of the dialogs pretty soon fearing they were doing
> something destructive.
> On other editions log shipping requires significant "programming" and the
> chances of setting it up unintentionally are very remote.
> It is possible that you scheduled transaction log dumps which are an
> important step in log shipping (but only the first step and not the only
> step). This can be done using the maintenance wizard.
> All in all its pretty remote.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Simon" <none@.none.com> wrote in message
> news:deeKf.12140$yK1.10202@.news-server.bigpond.net.au...
>
|||You would really have to be day dreaming pretty badly to "accidentally" set
this up. Using the wizards in 2000 or 2005, you would have to wade through
at least half a dozen screens, some of which have at least a dozen options
that have to be set. You could conceivably load up a script from a Resource
Kit, hit the button and create a log shipping set up, but you would have to
edit the script in the first place with at least server names and share
names, not something that I would call accidental. So, I would pretty much
have to say that it is not possible to "accidentally" setup log shipping.
That would be pretty analogous to someone accidentally building a house, it
just doesn't happen.
If log shipping is setup, you will see at least 3 jobs. Backup, copy, and
restore. The backup jb will generally be on the primary. The copy and
restore would generally be on the secondary. You will have the backup job
creating the backups in a share on the primary. The copy job would pull
them from the share on the primary to the share on the secondary. So you
can look in two places for the pieces. SQL Server Agent will have the jobs.
The file system on both primary and secondary will have a share created
which will contain tran log backups.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Simon" <none@.none.com> wrote in message
news:deeKf.12140$yK1.10202@.news-server.bigpond.net.au...
> Hi there, was just wondering...
> I setup database replication , creating a publisher and a subscriber....
> all seemed to go well.
> Anyway, my question is... Can Log Shipping be setup accidently while doing
> this process? I know nothing
> about log shipping.. and someone is trying to point blame on me for
> creating 'Log shipping'.
> Is it possible that I could have created log shipping without even
> knowing.. or does it require a bit of know how.
> Also... if Log shipping was setup... Does it run automatically?
> And last but not least.. If it was setup, and the standby server was
> turned off.. and not running... Would log shipping run?
> Sorry about my ignorance.. but I have a feeling the people who are making
> these accusations are out to create / pass blame across to poor old me for
> their own mistakes.
> thanks in advance everyone
> -Simon
>
>
Saturday, February 25, 2012
Accidental Log Shipping?
Labels:
accidental,
creating,
database,
log,
microsoft,
mysql,
oracle,
publisher,
replication,
server,
setup,
shipping,
sql,
subscriber
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment