Re: ADO & SQL Server.
- From: Sam Davis <SamDavis@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 3 Jun 2005 10:24:01 -0700
Yes we are using the backup command in T-SQL. It is strange though where the
open transaction is coming from. It is the same two routines that cause the
lock-up but we have gone through each one over and over to find any place
where an open transaction could be left. I know there was mention of this in
the latest service pack but didn't know if it was entirely related.
"William (Bill) Vaughn" wrote:
> Again, I concur. Using a SP to backup your data is not such a good idea
> unless it's calling the TSQL BACKUP DATABASE command. Using a SELECT etc.
> would be subject to blocking by other concurrent operations.
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Uwa Agbonile [MSFT]" <uwaag@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:enBPc2tZFHA.2768@xxxxxxxxxxxxxxxxxxxxxxx
> > Not really. Is the stored proc using the SQL Server BACKUP statement? If
> > not, then you are going to have to figure out how to work around this
> > issue.
> > You might want to look into picking a Transaction isolation levels
> > suitable
> > for your needs. The SQL Books online on MSDN will provide you more
> > information on transaction isolation levels.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > Regards,
> > Uwa Agbonile[MSFT]
> >
> > "Sam Davis" <SamDavis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:1C687575-644B-4252-BCF7-D469E92452E7@xxxxxxxxxxxxxxxx
> >> It is a backup intiated through a stored procedure to a file. I hope that
> >> answers the question. Thanks!
> >>
> >> "Uwa Agbonile [MSFT]" wrote:
> >>
> >> > Are you using the SQL Server BACKUP command? As far as I know, this
> >> > shouldn't block on a transaction. Could you provide more details on
> >> > your
> >> > backup operation?
> >> >
> >> > --
> >> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >> > Regards,
> >> > Uwa Agbonile[MSFT]
> >> >
> >> > "Sam Davis" <SamDavis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> > news:D6C591EF-2CFF-437F-BD1C-15ABA8DFD2F1@xxxxxxxxxxxxxxxx
> >> > > I was wondering if anyone can help me figure out an issue that we
> >> > encounter
> >> > > between ADO & SQL Server. We have a process that kicks off in the
> > evening
> >> > > that processes the days events, during this process a back up occurs.
> > For
> >> > > some reason we aren't sure but if someone is using or posting
> > information
> >> > to
> >> > > the system an open transaction is left which in turns keeps the
> >> > > backup
> >> > from
> >> > > happening. These transactions that are left open are a problem due to
> > a
> >> > page
> >> > > has to go out to one of us :).. The code is utilized during the day
> >> > without
> >> > > issue, just during this timeframe that backups are occuring .. Any
> > ideas
> >> > on
> >> > > what I should be doing to address the issue? We have tried everything
> > we
> >> > know
> >> > > of.
> >> >
> >> >
> >> >
> >
> >
>
>
>
.
- Follow-Ups:
- Re: ADO & SQL Server.
- From: William \(Bill\) Vaughn
- Re: ADO & SQL Server.
- References:
- ADO & SQL Server.
- From: Sam Davis
- Re: ADO & SQL Server.
- From: Uwa Agbonile [MSFT]
- Re: ADO & SQL Server.
- From: Sam Davis
- Re: ADO & SQL Server.
- From: Uwa Agbonile [MSFT]
- Re: ADO & SQL Server.
- From: William \(Bill\) Vaughn
- ADO & SQL Server.
- Prev by Date: Message to Bill Vaughn
- Next by Date: MDAC on Win2k3 SP1
- Previous by thread: Re: ADO & SQL Server.
- Next by thread: Re: ADO & SQL Server.
- Index(es):
Relevant Pages
|
Loading