Summarised: Filtered record, changed at Publisher to take out of filter for Subscriber, at Subscriber record removed but related records dont go, bad.. Alternatively, Filtered record, changed at Subscriber to take out of filter, Replication removes all related records from Subscriber db when merge repl runs, good... :-|
Why the difference?
Have Row Filters & Join Filters.
Details: Ive set up Merge replication, with several articles with Row/Join Filters.
When I change a record on the Publication that exists at the Subscriber (that has been filtered/sync etc) that record gets communicated to the Subscriber, which is fine.
However, when I change a record on the server so that the record is no longer valid for that Subscriber because it falls outside the filter - the delete goes to the Subscriber, but its related records on the Subscriber do not get removed.
This is even more confusing, because if I change the record at the Subscriber, so that it falls outside the filter, it gets removed along with its related record.
Ive checked the logic & relations/joins which all appear to be valid. The fact that the Subscriber removes related records when it changes the record suggests that the Joins are valid. Doesnt it?
Is there an option/flag to force server changes to validate related records when sync happens?
Any help much appreciated.
Mr Le.Anybody, anybody? ;-)
Ive checked other posts in here and there appeared to be a couple of other people who had a similar issue, im following those threads to see if they offer a solution or hint.
Thanks for reading.|||Mr Le,
please can you post up a little more info. Are you adding rows on the
subscriber? Are these rows being propagated to the publisher but then not
removed on the subscriber as you'd expect due to the filter? If this is the
case I know of 2 posibilities:
(1) you've done a bulk insert without firing triggers on the subscriber.
(2) you have a filter like 1=2 and have added records while the merge agent
is running.
In each case you can:
run SP_ADDTABLETOCONTENTS then synchronize
run SP_MERGEDUMMYUPDATE for a single row then synchronize
HTH,
Paul Ibison
|||Paul,
Thanks for replying, its much appreciated, hopefully I can add a bit more info to clarify whats happening.
The Subscriber is a Pull-Subscription.
There are Row/Join filters defined for the Publication.
The initial Snapshot took a subset of records from the Publisher to the Subscriber, that were in-line with the filters defined for that Publication.
Test 1
1. The subscriber receives the Snapshot, and all expected records are added.
2. An update to a row at the Publisher is propogated to the Subscriber, where it is deleted because it no longer satisfies the Filters.
* Related records are not removed from the Subscriber though. This is the Problem.
* So we tried to see what would happen if we changed the record at the Subscriber instead of the Publication.
Test 2
1. We reinitialized the Subscriber, the initial Snapshot was then applied to the Subscriber. All valid records go across.
2. This time, we changed the row at the Subscriber, and this change meant that the record no longer satisfied the Filter. Merge Agent ran, and deleted the record on the Subscriber, except this time it also deleted all related records, which is what we expected to happen in the first place.
These "deletes" were not propogated back to the Publisher, which again is what we expected.
* No Bulk updates/inserts took place, other than those caused by the initial Snapshot.
* No records were added whilst the Merge Agent was running.
Hope ive described this well enough.
If you need more detail of the row filters were using and/or join filters, let me know.
Thanks again for your help.|||Mr Le,
thanks for the detailed description. Please can you post up a schema of the
tables involved and details of the joins/filters involved, and I'll
reproduce it here.
Cheers,
Paul
Showing posts with label failing. Show all posts
Showing posts with label failing. Show all posts
Friday, February 24, 2012
Sunday, February 19, 2012
Daily backup problem
My SQL 2000 server's daily (full) backup started failing due to a lack of
disk space. This daily backup has been running for quite a while so im
surprised. The file system was full but it seems the old backup are not
being deleted even though the maintenance plan is set to ""Remove files older
than 1 day". Any ideas why this would happen? Solutions?
Paul
Old fulls, or old t-log backups? If t-log make sure every db in the plan is
set to full recovery model. If you have databases in Simple recovery, make
a separate plan for them without the t-log backup step
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>
> My SQL 2000 server's daily (full) backup started failing due to a lack of
> disk space. This daily backup has been running for quite a while so im
> surprised. The file system was full but it seems the old backup are not
> being deleted even though the maintenance plan is set to ""Remove files
> older
> than 1 day". Any ideas why this would happen? Solutions?
>
> Paul
>
|||Old fulls.
I only do full backups.
"Kevin3NF" wrote:
> Old fulls, or old t-log backups? If t-log make sure every db in the plan is
> set to full recovery model. If you have databases in Simple recovery, make
> a separate plan for them without the t-log backup step
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>
>
|||Paul,
The delete happens after the backup is taken. If you do not have enough
space for the backup it will not delete the old backup. Could this be your
problem?
Chris
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...[vbcol=seagreen]
> Old fulls.
> I only do full backups.
> "Kevin3NF" wrote:
|||Check to see if the account running the SQL Server Agent has permissions to
delete those fulls. Look for the maintenance plan logs in the \LOG
directory (same location as the ERRORLOG file(s) )
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...[vbcol=seagreen]
> Old fulls.
> I only do full backups.
> "Kevin3NF" wrote:
|||No there is enough space for 3 days of backups
"Chris Wood" wrote:
> Paul,
> The delete happens after the backup is taken. If you do not have enough
> space for the backup it will not delete the old backup. Could this be your
> problem?
> Chris
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
>
>
|||The account has full admin permission so that not a problem. Like I said this
has not been a problem for months. I don't see a log specifacally for
maintenance logs.
"Kevin3NF" wrote:
> Check to see if the account running the SQL Server Agent has permissions to
> delete those fulls. Look for the maintenance plan logs in the \LOG
> directory (same location as the ERRORLOG file(s) )
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
>
>
|||The account have the permissions to delete these file. No problem there. I
don't see a maintenance plan specific log file.
Paul
"Kevin3NF" wrote:
> Check to see if the account running the SQL Server Agent has permissions to
> delete those fulls. Look for the maintenance plan logs in the \LOG
> directory (same location as the ERRORLOG file(s) )
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
>
>
|||Add a "text file" option in the Reporting tab of the Database maintenance
GUI (SQL 2000)
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:8670769E-BF6B-4C1F-BE67-84C830DBF144@.microsoft.com...[vbcol=seagreen]
> The account have the permissions to delete these file. No problem there. I
> don't see a maintenance plan specific log file.
> Paul
> "Kevin3NF" wrote:
disk space. This daily backup has been running for quite a while so im
surprised. The file system was full but it seems the old backup are not
being deleted even though the maintenance plan is set to ""Remove files older
than 1 day". Any ideas why this would happen? Solutions?
Paul
Old fulls, or old t-log backups? If t-log make sure every db in the plan is
set to full recovery model. If you have databases in Simple recovery, make
a separate plan for them without the t-log backup step
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>
> My SQL 2000 server's daily (full) backup started failing due to a lack of
> disk space. This daily backup has been running for quite a while so im
> surprised. The file system was full but it seems the old backup are not
> being deleted even though the maintenance plan is set to ""Remove files
> older
> than 1 day". Any ideas why this would happen? Solutions?
>
> Paul
>
|||Old fulls.
I only do full backups.
"Kevin3NF" wrote:
> Old fulls, or old t-log backups? If t-log make sure every db in the plan is
> set to full recovery model. If you have databases in Simple recovery, make
> a separate plan for them without the t-log backup step
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>
>
|||Paul,
The delete happens after the backup is taken. If you do not have enough
space for the backup it will not delete the old backup. Could this be your
problem?
Chris
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...[vbcol=seagreen]
> Old fulls.
> I only do full backups.
> "Kevin3NF" wrote:
|||Check to see if the account running the SQL Server Agent has permissions to
delete those fulls. Look for the maintenance plan logs in the \LOG
directory (same location as the ERRORLOG file(s) )
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...[vbcol=seagreen]
> Old fulls.
> I only do full backups.
> "Kevin3NF" wrote:
|||No there is enough space for 3 days of backups
"Chris Wood" wrote:
> Paul,
> The delete happens after the backup is taken. If you do not have enough
> space for the backup it will not delete the old backup. Could this be your
> problem?
> Chris
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
>
>
|||The account has full admin permission so that not a problem. Like I said this
has not been a problem for months. I don't see a log specifacally for
maintenance logs.
"Kevin3NF" wrote:
> Check to see if the account running the SQL Server Agent has permissions to
> delete those fulls. Look for the maintenance plan logs in the \LOG
> directory (same location as the ERRORLOG file(s) )
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
>
>
|||The account have the permissions to delete these file. No problem there. I
don't see a maintenance plan specific log file.
Paul
"Kevin3NF" wrote:
> Check to see if the account running the SQL Server Agent has permissions to
> delete those fulls. Look for the maintenance plan logs in the \LOG
> directory (same location as the ERRORLOG file(s) )
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
>
>
|||Add a "text file" option in the Reporting tab of the Database maintenance
GUI (SQL 2000)
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:8670769E-BF6B-4C1F-BE67-84C830DBF144@.microsoft.com...[vbcol=seagreen]
> The account have the permissions to delete these file. No problem there. I
> don't see a maintenance plan specific log file.
> Paul
> "Kevin3NF" wrote:
Daily backup problem
My SQL 2000 server's daily (full) backup started failing due to a lack of
disk space. This daily backup has been running for quite a while so im
surprised. The file system was full but it seems the old backup are not
being deleted even though the maintenance plan is set to ""Remove files older
than 1 day". Any ideas why this would happen? Solutions?
PaulOld fulls, or old t-log backups? If t-log make sure every db in the plan is
set to full recovery model. If you have databases in Simple recovery, make
a separate plan for them without the t-log backup step
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>
> My SQL 2000 server's daily (full) backup started failing due to a lack of
> disk space. This daily backup has been running for quite a while so im
> surprised. The file system was full but it seems the old backup are not
> being deleted even though the maintenance plan is set to ""Remove files
> older
> than 1 day". Any ideas why this would happen? Solutions?
>
> Paul
>|||Old fulls.
I only do full backups.
"Kevin3NF" wrote:
> Old fulls, or old t-log backups? If t-log make sure every db in the plan is
> set to full recovery model. If you have databases in Simple recovery, make
> a separate plan for them without the t-log backup step
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
> >
> >
> > My SQL 2000 server's daily (full) backup started failing due to a lack of
> > disk space. This daily backup has been running for quite a while so im
> > surprised. The file system was full but it seems the old backup are not
> > being deleted even though the maintenance plan is set to ""Remove files
> > older
> > than 1 day". Any ideas why this would happen? Solutions?
> >
> >
> >
> > Paul
> >
>
>|||Paul,
The delete happens after the backup is taken. If you do not have enough
space for the backup it will not delete the old backup. Could this be your
problem?
Chris
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> Old fulls.
> I only do full backups.
> "Kevin3NF" wrote:
>> Old fulls, or old t-log backups? If t-log make sure every db in the plan
>> is
>> set to full recovery model. If you have databases in Simple recovery,
>> make
>> a separate plan for them without the t-log backup step
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
>> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>> >
>> >
>> > My SQL 2000 server's daily (full) backup started failing due to a lack
>> > of
>> > disk space. This daily backup has been running for quite a while so im
>> > surprised. The file system was full but it seems the old backup are
>> > not
>> > being deleted even though the maintenance plan is set to ""Remove files
>> > older
>> > than 1 day". Any ideas why this would happen? Solutions?
>> >
>> >
>> >
>> > Paul
>> >
>>|||Check to see if the account running the SQL Server Agent has permissions to
delete those fulls. Look for the maintenance plan logs in the \LOG
directory (same location as the ERRORLOG file(s) )
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> Old fulls.
> I only do full backups.
> "Kevin3NF" wrote:
>> Old fulls, or old t-log backups? If t-log make sure every db in the plan
>> is
>> set to full recovery model. If you have databases in Simple recovery,
>> make
>> a separate plan for them without the t-log backup step
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
>> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>> >
>> >
>> > My SQL 2000 server's daily (full) backup started failing due to a lack
>> > of
>> > disk space. This daily backup has been running for quite a while so im
>> > surprised. The file system was full but it seems the old backup are
>> > not
>> > being deleted even though the maintenance plan is set to ""Remove files
>> > older
>> > than 1 day". Any ideas why this would happen? Solutions?
>> >
>> >
>> >
>> > Paul
>> >
>>|||No there is enough space for 3 days of backups
"Chris Wood" wrote:
> Paul,
> The delete happens after the backup is taken. If you do not have enough
> space for the backup it will not delete the old backup. Could this be your
> problem?
> Chris
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> > Old fulls.
> > I only do full backups.
> >
> > "Kevin3NF" wrote:
> >
> >> Old fulls, or old t-log backups? If t-log make sure every db in the plan
> >> is
> >> set to full recovery model. If you have databases in Simple recovery,
> >> make
> >> a separate plan for them without the t-log backup step
> >>
> >> --
> >>
> >> Kevin3NF
> >> SQL Server dude
> >>
> >> You want fries with that?
> >> http://kevin3nf.blogspot.com/
> >>
> >> I only check the newsgroups during work hours, M-F.
> >> Hit my blog and the contact links if necessary...I may be available.
> >>
> >>
> >>
> >> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> >> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
> >> >
> >> >
> >> > My SQL 2000 server's daily (full) backup started failing due to a lack
> >> > of
> >> > disk space. This daily backup has been running for quite a while so im
> >> > surprised. The file system was full but it seems the old backup are
> >> > not
> >> > being deleted even though the maintenance plan is set to ""Remove files
> >> > older
> >> > than 1 day". Any ideas why this would happen? Solutions?
> >> >
> >> >
> >> >
> >> > Paul
> >> >
> >>
> >>
> >>
>
>|||The account has full admin permission so that not a problem. Like I said this
has not been a problem for months. I don't see a log specifacally for
maintenance logs.
"Kevin3NF" wrote:
> Check to see if the account running the SQL Server Agent has permissions to
> delete those fulls. Look for the maintenance plan logs in the \LOG
> directory (same location as the ERRORLOG file(s) )
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> > Old fulls.
> > I only do full backups.
> >
> > "Kevin3NF" wrote:
> >
> >> Old fulls, or old t-log backups? If t-log make sure every db in the plan
> >> is
> >> set to full recovery model. If you have databases in Simple recovery,
> >> make
> >> a separate plan for them without the t-log backup step
> >>
> >> --
> >>
> >> Kevin3NF
> >> SQL Server dude
> >>
> >> You want fries with that?
> >> http://kevin3nf.blogspot.com/
> >>
> >> I only check the newsgroups during work hours, M-F.
> >> Hit my blog and the contact links if necessary...I may be available.
> >>
> >>
> >>
> >> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> >> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
> >> >
> >> >
> >> > My SQL 2000 server's daily (full) backup started failing due to a lack
> >> > of
> >> > disk space. This daily backup has been running for quite a while so im
> >> > surprised. The file system was full but it seems the old backup are
> >> > not
> >> > being deleted even though the maintenance plan is set to ""Remove files
> >> > older
> >> > than 1 day". Any ideas why this would happen? Solutions?
> >> >
> >> >
> >> >
> >> > Paul
> >> >
> >>
> >>
> >>
>
>|||The account have the permissions to delete these file. No problem there. I
don't see a maintenance plan specific log file.
Paul
"Kevin3NF" wrote:
> Check to see if the account running the SQL Server Agent has permissions to
> delete those fulls. Look for the maintenance plan logs in the \LOG
> directory (same location as the ERRORLOG file(s) )
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> > Old fulls.
> > I only do full backups.
> >
> > "Kevin3NF" wrote:
> >
> >> Old fulls, or old t-log backups? If t-log make sure every db in the plan
> >> is
> >> set to full recovery model. If you have databases in Simple recovery,
> >> make
> >> a separate plan for them without the t-log backup step
> >>
> >> --
> >>
> >> Kevin3NF
> >> SQL Server dude
> >>
> >> You want fries with that?
> >> http://kevin3nf.blogspot.com/
> >>
> >> I only check the newsgroups during work hours, M-F.
> >> Hit my blog and the contact links if necessary...I may be available.
> >>
> >>
> >>
> >> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> >> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
> >> >
> >> >
> >> > My SQL 2000 server's daily (full) backup started failing due to a lack
> >> > of
> >> > disk space. This daily backup has been running for quite a while so im
> >> > surprised. The file system was full but it seems the old backup are
> >> > not
> >> > being deleted even though the maintenance plan is set to ""Remove files
> >> > older
> >> > than 1 day". Any ideas why this would happen? Solutions?
> >> >
> >> >
> >> >
> >> > Paul
> >> >
> >>
> >>
> >>
>
>|||Add a "text file" option in the Reporting tab of the Database maintenance
GUI (SQL 2000)
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:8670769E-BF6B-4C1F-BE67-84C830DBF144@.microsoft.com...
> The account have the permissions to delete these file. No problem there. I
> don't see a maintenance plan specific log file.
> Paul
> "Kevin3NF" wrote:
>> Check to see if the account running the SQL Server Agent has permissions
>> to
>> delete those fulls. Look for the maintenance plan logs in the \LOG
>> directory (same location as the ERRORLOG file(s) )
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
>> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
>> > Old fulls.
>> > I only do full backups.
>> >
>> > "Kevin3NF" wrote:
>> >
>> >> Old fulls, or old t-log backups? If t-log make sure every db in the
>> >> plan
>> >> is
>> >> set to full recovery model. If you have databases in Simple recovery,
>> >> make
>> >> a separate plan for them without the t-log backup step
>> >>
>> >> --
>> >>
>> >> Kevin3NF
>> >> SQL Server dude
>> >>
>> >> You want fries with that?
>> >> http://kevin3nf.blogspot.com/
>> >>
>> >> I only check the newsgroups during work hours, M-F.
>> >> Hit my blog and the contact links if necessary...I may be available.
>> >>
>> >>
>> >>
>> >> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
>> >> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>> >> >
>> >> >
>> >> > My SQL 2000 server's daily (full) backup started failing due to a
>> >> > lack
>> >> > of
>> >> > disk space. This daily backup has been running for quite a while so
>> >> > im
>> >> > surprised. The file system was full but it seems the old backup are
>> >> > not
>> >> > being deleted even though the maintenance plan is set to ""Remove
>> >> > files
>> >> > older
>> >> > than 1 day". Any ideas why this would happen? Solutions?
>> >> >
>> >> >
>> >> >
>> >> > Paul
>> >> >
>> >>
>> >>
>> >>
>>
disk space. This daily backup has been running for quite a while so im
surprised. The file system was full but it seems the old backup are not
being deleted even though the maintenance plan is set to ""Remove files older
than 1 day". Any ideas why this would happen? Solutions?
PaulOld fulls, or old t-log backups? If t-log make sure every db in the plan is
set to full recovery model. If you have databases in Simple recovery, make
a separate plan for them without the t-log backup step
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>
> My SQL 2000 server's daily (full) backup started failing due to a lack of
> disk space. This daily backup has been running for quite a while so im
> surprised. The file system was full but it seems the old backup are not
> being deleted even though the maintenance plan is set to ""Remove files
> older
> than 1 day". Any ideas why this would happen? Solutions?
>
> Paul
>|||Old fulls.
I only do full backups.
"Kevin3NF" wrote:
> Old fulls, or old t-log backups? If t-log make sure every db in the plan is
> set to full recovery model. If you have databases in Simple recovery, make
> a separate plan for them without the t-log backup step
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
> >
> >
> > My SQL 2000 server's daily (full) backup started failing due to a lack of
> > disk space. This daily backup has been running for quite a while so im
> > surprised. The file system was full but it seems the old backup are not
> > being deleted even though the maintenance plan is set to ""Remove files
> > older
> > than 1 day". Any ideas why this would happen? Solutions?
> >
> >
> >
> > Paul
> >
>
>|||Paul,
The delete happens after the backup is taken. If you do not have enough
space for the backup it will not delete the old backup. Could this be your
problem?
Chris
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> Old fulls.
> I only do full backups.
> "Kevin3NF" wrote:
>> Old fulls, or old t-log backups? If t-log make sure every db in the plan
>> is
>> set to full recovery model. If you have databases in Simple recovery,
>> make
>> a separate plan for them without the t-log backup step
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
>> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>> >
>> >
>> > My SQL 2000 server's daily (full) backup started failing due to a lack
>> > of
>> > disk space. This daily backup has been running for quite a while so im
>> > surprised. The file system was full but it seems the old backup are
>> > not
>> > being deleted even though the maintenance plan is set to ""Remove files
>> > older
>> > than 1 day". Any ideas why this would happen? Solutions?
>> >
>> >
>> >
>> > Paul
>> >
>>|||Check to see if the account running the SQL Server Agent has permissions to
delete those fulls. Look for the maintenance plan logs in the \LOG
directory (same location as the ERRORLOG file(s) )
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> Old fulls.
> I only do full backups.
> "Kevin3NF" wrote:
>> Old fulls, or old t-log backups? If t-log make sure every db in the plan
>> is
>> set to full recovery model. If you have databases in Simple recovery,
>> make
>> a separate plan for them without the t-log backup step
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
>> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>> >
>> >
>> > My SQL 2000 server's daily (full) backup started failing due to a lack
>> > of
>> > disk space. This daily backup has been running for quite a while so im
>> > surprised. The file system was full but it seems the old backup are
>> > not
>> > being deleted even though the maintenance plan is set to ""Remove files
>> > older
>> > than 1 day". Any ideas why this would happen? Solutions?
>> >
>> >
>> >
>> > Paul
>> >
>>|||No there is enough space for 3 days of backups
"Chris Wood" wrote:
> Paul,
> The delete happens after the backup is taken. If you do not have enough
> space for the backup it will not delete the old backup. Could this be your
> problem?
> Chris
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> > Old fulls.
> > I only do full backups.
> >
> > "Kevin3NF" wrote:
> >
> >> Old fulls, or old t-log backups? If t-log make sure every db in the plan
> >> is
> >> set to full recovery model. If you have databases in Simple recovery,
> >> make
> >> a separate plan for them without the t-log backup step
> >>
> >> --
> >>
> >> Kevin3NF
> >> SQL Server dude
> >>
> >> You want fries with that?
> >> http://kevin3nf.blogspot.com/
> >>
> >> I only check the newsgroups during work hours, M-F.
> >> Hit my blog and the contact links if necessary...I may be available.
> >>
> >>
> >>
> >> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> >> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
> >> >
> >> >
> >> > My SQL 2000 server's daily (full) backup started failing due to a lack
> >> > of
> >> > disk space. This daily backup has been running for quite a while so im
> >> > surprised. The file system was full but it seems the old backup are
> >> > not
> >> > being deleted even though the maintenance plan is set to ""Remove files
> >> > older
> >> > than 1 day". Any ideas why this would happen? Solutions?
> >> >
> >> >
> >> >
> >> > Paul
> >> >
> >>
> >>
> >>
>
>|||The account has full admin permission so that not a problem. Like I said this
has not been a problem for months. I don't see a log specifacally for
maintenance logs.
"Kevin3NF" wrote:
> Check to see if the account running the SQL Server Agent has permissions to
> delete those fulls. Look for the maintenance plan logs in the \LOG
> directory (same location as the ERRORLOG file(s) )
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> > Old fulls.
> > I only do full backups.
> >
> > "Kevin3NF" wrote:
> >
> >> Old fulls, or old t-log backups? If t-log make sure every db in the plan
> >> is
> >> set to full recovery model. If you have databases in Simple recovery,
> >> make
> >> a separate plan for them without the t-log backup step
> >>
> >> --
> >>
> >> Kevin3NF
> >> SQL Server dude
> >>
> >> You want fries with that?
> >> http://kevin3nf.blogspot.com/
> >>
> >> I only check the newsgroups during work hours, M-F.
> >> Hit my blog and the contact links if necessary...I may be available.
> >>
> >>
> >>
> >> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> >> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
> >> >
> >> >
> >> > My SQL 2000 server's daily (full) backup started failing due to a lack
> >> > of
> >> > disk space. This daily backup has been running for quite a while so im
> >> > surprised. The file system was full but it seems the old backup are
> >> > not
> >> > being deleted even though the maintenance plan is set to ""Remove files
> >> > older
> >> > than 1 day". Any ideas why this would happen? Solutions?
> >> >
> >> >
> >> >
> >> > Paul
> >> >
> >>
> >>
> >>
>
>|||The account have the permissions to delete these file. No problem there. I
don't see a maintenance plan specific log file.
Paul
"Kevin3NF" wrote:
> Check to see if the account running the SQL Server Agent has permissions to
> delete those fulls. Look for the maintenance plan logs in the \LOG
> directory (same location as the ERRORLOG file(s) )
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
> > Old fulls.
> > I only do full backups.
> >
> > "Kevin3NF" wrote:
> >
> >> Old fulls, or old t-log backups? If t-log make sure every db in the plan
> >> is
> >> set to full recovery model. If you have databases in Simple recovery,
> >> make
> >> a separate plan for them without the t-log backup step
> >>
> >> --
> >>
> >> Kevin3NF
> >> SQL Server dude
> >>
> >> You want fries with that?
> >> http://kevin3nf.blogspot.com/
> >>
> >> I only check the newsgroups during work hours, M-F.
> >> Hit my blog and the contact links if necessary...I may be available.
> >>
> >>
> >>
> >> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
> >> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
> >> >
> >> >
> >> > My SQL 2000 server's daily (full) backup started failing due to a lack
> >> > of
> >> > disk space. This daily backup has been running for quite a while so im
> >> > surprised. The file system was full but it seems the old backup are
> >> > not
> >> > being deleted even though the maintenance plan is set to ""Remove files
> >> > older
> >> > than 1 day". Any ideas why this would happen? Solutions?
> >> >
> >> >
> >> >
> >> > Paul
> >> >
> >>
> >>
> >>
>
>|||Add a "text file" option in the Reporting tab of the Database maintenance
GUI (SQL 2000)
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
news:8670769E-BF6B-4C1F-BE67-84C830DBF144@.microsoft.com...
> The account have the permissions to delete these file. No problem there. I
> don't see a maintenance plan specific log file.
> Paul
> "Kevin3NF" wrote:
>> Check to see if the account running the SQL Server Agent has permissions
>> to
>> delete those fulls. Look for the maintenance plan logs in the \LOG
>> directory (same location as the ERRORLOG file(s) )
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
>> news:21B3A1CB-02A2-45B2-94EF-62A90E7ADACD@.microsoft.com...
>> > Old fulls.
>> > I only do full backups.
>> >
>> > "Kevin3NF" wrote:
>> >
>> >> Old fulls, or old t-log backups? If t-log make sure every db in the
>> >> plan
>> >> is
>> >> set to full recovery model. If you have databases in Simple recovery,
>> >> make
>> >> a separate plan for them without the t-log backup step
>> >>
>> >> --
>> >>
>> >> Kevin3NF
>> >> SQL Server dude
>> >>
>> >> You want fries with that?
>> >> http://kevin3nf.blogspot.com/
>> >>
>> >> I only check the newsgroups during work hours, M-F.
>> >> Hit my blog and the contact links if necessary...I may be available.
>> >>
>> >>
>> >>
>> >> "Paul_A" <PaulA@.discussions.microsoft.com> wrote in message
>> >> news:21E389B9-FADE-45A6-9DA6-22B27965EE32@.microsoft.com...
>> >> >
>> >> >
>> >> > My SQL 2000 server's daily (full) backup started failing due to a
>> >> > lack
>> >> > of
>> >> > disk space. This daily backup has been running for quite a while so
>> >> > im
>> >> > surprised. The file system was full but it seems the old backup are
>> >> > not
>> >> > being deleted even though the maintenance plan is set to ""Remove
>> >> > files
>> >> > older
>> >> > than 1 day". Any ideas why this would happen? Solutions?
>> >> >
>> >> >
>> >> >
>> >> > Paul
>> >> >
>> >>
>> >>
>> >>
>>
Subscribe to:
Posts (Atom)