Possible to locate active trans. log on different computer?

It does not appear possible to locate the active transaction log on a
computer other than the one on which the DB exists. Am I correct? Is there
no way to isolate the log from the box on which the data exists?
Thanks,
Randy NeallThere's an undocumented trace flag that allows you to do this. I don't
remember it off the top of my head, but I don't recommend it unless you're
in a well configured SAN environment. Even then it's not always the best
idea...
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in message
news:epOxPqZnDHA.2404@.TK2MSFTNGP12.phx.gbl...
> It does not appear possible to locate the active transaction log on a
> computer other than the one on which the DB exists. Am I correct? Is there
> no way to isolate the log from the box on which the data exists?
> Thanks,
> Randy Neall
>|||That's not possible and you don't want to do that, even if
you could.
Linchi
>--Original Message--
>It does not appear possible to locate the active
transaction log on a
>computer other than the one on which the DB exists. Am I
correct? Is there
>no way to isolate the log from the box on which the data
exists?
>Thanks,
>Randy Neall
>
>.
>|||Thanks, Brian for pointing this out! I totally forgot
about this trace flag. The trace flag is 1807, and KB
article is
http://support.microsoft.com/default.aspx?scid=304261
Linchi
>--Original Message--
>There's an undocumented trace flag that allows you to do
this. I don't
>remember it off the top of my head, but I don't recommend
it unless you're
>in a well configured SAN environment. Even then it's not
always the best
>idea...
>
>--
>Brian Moran
>Principal Mentor
>Solid Quality Learning
>SQL Server MVP
>http://www.solidqualitylearning.com
>
>"Randolph Neall" <randolphneall@.veracitycomputing.com>
wrote in message
>news:epOxPqZnDHA.2404@.TK2MSFTNGP12.phx.gbl...
>> It does not appear possible to locate the active
transaction log on a
>> computer other than the one on which the DB exists. Am
I correct? Is there
>> no way to isolate the log from the box on which the
data exists?
>> Thanks,
>> Randy Neall
>>
>
>.
>|||Hi Brian,
Why isn't this a good idea? The idea I had was to get the log and backups on
a completely separate box for added redundancy, saving us even if the DB box
were somehow destroyed, stolen, or if more than one drive within the DB box
failed. But you suggest, and Linchi confirms, this is a bad idea. Why?
Randy
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:OqOsUyZnDHA.1708@.TK2MSFTNGP12.phx.gbl...
> There's an undocumented trace flag that allows you to do this. I don't
> remember it off the top of my head, but I don't recommend it unless you're
> in a well configured SAN environment. Even then it's not always the best
> idea...
>
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in message
> news:epOxPqZnDHA.2404@.TK2MSFTNGP12.phx.gbl...
> > It does not appear possible to locate the active transaction log on a
> > computer other than the one on which the DB exists. Am I correct? Is
there
> > no way to isolate the log from the box on which the data exists?
> >
> > Thanks,
> > Randy Neall
> >
> >
>|||SQL Server log files are absolutely critical for database integrity.
Physical writes to log files must be guaranteed or committed data can be
lost and/or physical database corruption result. Standard network i/o
does not guarantee these writes and the loss of a single packet can be
disastrous. You'll need to be prepared to restore from backup in the
event of a simple network outage.
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in message
news:uatwTCcnDHA.3304@.tk2msftngp13.phx.gbl...
> Hi Brian,
> Why isn't this a good idea? The idea I had was to get the log and
backups on
> a completely separate box for added redundancy, saving us even if the
DB box
> were somehow destroyed, stolen, or if more than one drive within the
DB box
> failed. But you suggest, and Linchi confirms, this is a bad idea. Why?
> Randy
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in message
> news:OqOsUyZnDHA.1708@.TK2MSFTNGP12.phx.gbl...
> > There's an undocumented trace flag that allows you to do this. I
don't
> > remember it off the top of my head, but I don't recommend it unless
you're
> > in a well configured SAN environment. Even then it's not always the
best
> > idea...
> >
> >
> >
> > --
> >
> > Brian Moran
> > Principal Mentor
> > Solid Quality Learning
> > SQL Server MVP
> > http://www.solidqualitylearning.com
> >
> >
> > "Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in
message
> > news:epOxPqZnDHA.2404@.TK2MSFTNGP12.phx.gbl...
> > > It does not appear possible to locate the active transaction log
on a
> > > computer other than the one on which the DB exists. Am I correct?
Is
> there
> > > no way to isolate the log from the box on which the data exists?
> > >
> > > Thanks,
> > > Randy Neall
> > >
> > >
> >
> >
>|||Thanks. Yes you've helped a lot. I hadn't thought of the risks of network
failure.
Randy
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u1Ki88cnDHA.708@.TK2MSFTNGP10.phx.gbl...
> SQL Server log files are absolutely critical for database integrity.
> Physical writes to log files must be guaranteed or committed data can be
> lost and/or physical database corruption result. Standard network i/o
> does not guarantee these writes and the loss of a single packet can be
> disastrous. You'll need to be prepared to restore from backup in the
> event of a simple network outage.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> --
> SQL FAQ links (courtesy Neil Pike):
> http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> http://www.sqlserverfaq.com
> http://www.mssqlserver.com/faq
> --
> "Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in message
> news:uatwTCcnDHA.3304@.tk2msftngp13.phx.gbl...
> > Hi Brian,
> >
> > Why isn't this a good idea? The idea I had was to get the log and
> backups on
> > a completely separate box for added redundancy, saving us even if the
> DB box
> > were somehow destroyed, stolen, or if more than one drive within the
> DB box
> > failed. But you suggest, and Linchi confirms, this is a bad idea. Why?
> >
> > Randy
> >
> > "Brian Moran" <brian@.solidqualitylearning.com> wrote in message
> > news:OqOsUyZnDHA.1708@.TK2MSFTNGP12.phx.gbl...
> > > There's an undocumented trace flag that allows you to do this. I
> don't
> > > remember it off the top of my head, but I don't recommend it unless
> you're
> > > in a well configured SAN environment. Even then it's not always the
> best
> > > idea...
> > >
> > >
> > >
> > > --
> > >
> > > Brian Moran
> > > Principal Mentor
> > > Solid Quality Learning
> > > SQL Server MVP
> > > http://www.solidqualitylearning.com
> > >
> > >
> > > "Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in
> message
> > > news:epOxPqZnDHA.2404@.TK2MSFTNGP12.phx.gbl...
> > > > It does not appear possible to locate the active transaction log
> on a
> > > > computer other than the one on which the DB exists. Am I correct?
> Is
> > there
> > > > no way to isolate the log from the box on which the data exists?
> > > >
> > > > Thanks,
> > > > Randy Neall
> > > >
> > > >
> > >
> > >
> >
> >
>|||> Why isn't this a good idea?
Did you read the KB article? As I remember, it is pretty clear on the subject.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in message
news:uatwTCcnDHA.3304@.tk2msftngp13.phx.gbl...
> Hi Brian,
> Why isn't this a good idea? The idea I had was to get the log and backups on
> a completely separate box for added redundancy, saving us even if the DB box
> were somehow destroyed, stolen, or if more than one drive within the DB box
> failed. But you suggest, and Linchi confirms, this is a bad idea. Why?
> Randy
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in message
> news:OqOsUyZnDHA.1708@.TK2MSFTNGP12.phx.gbl...
> > There's an undocumented trace flag that allows you to do this. I don't
> > remember it off the top of my head, but I don't recommend it unless you're
> > in a well configured SAN environment. Even then it's not always the best
> > idea...
> >
> >
> >
> > --
> >
> > Brian Moran
> > Principal Mentor
> > Solid Quality Learning
> > SQL Server MVP
> > http://www.solidqualitylearning.com
> >
> >
> > "Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in message
> > news:epOxPqZnDHA.2404@.TK2MSFTNGP12.phx.gbl...
> > > It does not appear possible to locate the active transaction log on a
> > > computer other than the one on which the DB exists. Am I correct? Is
> there
> > > no way to isolate the log from the box on which the data exists?
> > >
> > > Thanks,
> > > Randy Neall
> > >
> > >
> >
> >
>|||I just did. You're right. It's clear. Thanks
Randy
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ODUsa4enDHA.3304@.tk2msftngp13.phx.gbl...
> > Why isn't this a good idea?
> Did you read the KB article? As I remember, it is pretty clear on the
subject.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in message
> news:uatwTCcnDHA.3304@.tk2msftngp13.phx.gbl...
> > Hi Brian,
> >
> > Why isn't this a good idea? The idea I had was to get the log and
backups on
> > a completely separate box for added redundancy, saving us even if the DB
box
> > were somehow destroyed, stolen, or if more than one drive within the DB
box
> > failed. But you suggest, and Linchi confirms, this is a bad idea. Why?
> >
> > Randy
> >
> > "Brian Moran" <brian@.solidqualitylearning.com> wrote in message
> > news:OqOsUyZnDHA.1708@.TK2MSFTNGP12.phx.gbl...
> > > There's an undocumented trace flag that allows you to do this. I don't
> > > remember it off the top of my head, but I don't recommend it unless
you're
> > > in a well configured SAN environment. Even then it's not always the
best
> > > idea...
> > >
> > >
> > >
> > > --
> > >
> > > Brian Moran
> > > Principal Mentor
> > > Solid Quality Learning
> > > SQL Server MVP
> > > http://www.solidqualitylearning.com
> > >
> > >
> > > "Randolph Neall" <randolphneall@.veracitycomputing.com> wrote in
message
> > > news:epOxPqZnDHA.2404@.TK2MSFTNGP12.phx.gbl...
> > > > It does not appear possible to locate the active transaction log on
a
> > > > computer other than the one on which the DB exists. Am I correct? Is
> > there
> > > > no way to isolate the log from the box on which the data exists?
> > > >
> > > > Thanks,
> > > > Randy Neall
> > > >
> > > >
> > >
> > >
> >
> >
>