We have setup Log Shipping in SQL 2005. Working flawlessly. It appears that
only tran log backup will occur forever unless we intervene. I do want a full
backup to happen, you know, eventually...
What is best way to automate this? Ideally, a full backup nightly would be
great. How to do in script, or is there anything in gui?
tia,
chrisYou want a full backup of the primary? Just do Backup database...
You cannot backup the secondary as far as I know.
If you want to re-init log shipping and start clean on a system that LS is
working flawlessly on, you aer simply wasting bandwidth and cpu. :)
--
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.
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:2E07F579-4A8A-47B6-B457-D7B543F00086@.microsoft.com...
> We have setup Log Shipping in SQL 2005. Working flawlessly. It appears
> that
> only tran log backup will occur forever unless we intervene. I do want a
> full
> backup to happen, you know, eventually...
> What is best way to automate this? Ideally, a full backup nightly would be
> great. How to do in script, or is there anything in gui?
> tia,
> chris|||I can't "just do backup database..." this will break log shipping. Correct?
I'm concerned w/ primary - to start log shipping you do a full backup to
init, then tran log backups thereafter w/ each log shipped to secondary. I DO
NOT want to do tran log backups forever... I eventually would like to do a
full backup.
Am I missing somehting...?
cb
"Kevin3NF" wrote:
> You want a full backup of the primary? Just do Backup database...
> You cannot backup the secondary as far as I know.
> If you want to re-init log shipping and start clean on a system that LS is
> working flawlessly on, you aer simply wasting bandwidth and cpu. :)
> --
> 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.
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:2E07F579-4A8A-47B6-B457-D7B543F00086@.microsoft.com...
> >
> > We have setup Log Shipping in SQL 2005. Working flawlessly. It appears
> > that
> > only tran log backup will occur forever unless we intervene. I do want a
> > full
> > backup to happen, you know, eventually...
> >
> > What is best way to automate this? Ideally, a full backup nightly would be
> > great. How to do in script, or is there anything in gui?
> >
> > tia,
> > chris
>
>|||Full backups do NOT break the log chain sequence so you can do a FULL backup
at any time. The next log backup after a FULL backup will still capture any
transactions since the previous Log backup, regardless of if there was a
FULL in between or not.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:D69D6BFF-3674-4894-92DF-35EB8261E9DA@.microsoft.com...
> I can't "just do backup database..." this will break log shipping.
> Correct?
> I'm concerned w/ primary - to start log shipping you do a full backup to
> init, then tran log backups thereafter w/ each log shipped to secondary. I
> DO
> NOT want to do tran log backups forever... I eventually would like to do a
> full backup.
> Am I missing somehting...?
> cb
> "Kevin3NF" wrote:
>> You want a full backup of the primary? Just do Backup database...
>> You cannot backup the secondary as far as I know.
>> If you want to re-init log shipping and start clean on a system that LS
>> is
>> working flawlessly on, you aer simply wasting bandwidth and cpu. :)
>> --
>> 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.
>>
>> "Chris" <Chris@.discussions.microsoft.com> wrote in message
>> news:2E07F579-4A8A-47B6-B457-D7B543F00086@.microsoft.com...
>> >
>> > We have setup Log Shipping in SQL 2005. Working flawlessly. It appears
>> > that
>> > only tran log backup will occur forever unless we intervene. I do want
>> > a
>> > full
>> > backup to happen, you know, eventually...
>> >
>> > What is best way to automate this? Ideally, a full backup nightly would
>> > be
>> > great. How to do in script, or is there anything in gui?
>> >
>> > tia,
>> > chris
>>|||Also, taking DIFFERENTIAL BACKUP would NOT break the log sequence.
However taking TRANSACTION LOG backup (other than the automated jobs of Log
Shipping itself) would break the chain.
--
Ekrem Ã?nsoy
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:D69D6BFF-3674-4894-92DF-35EB8261E9DA@.microsoft.com...
> I can't "just do backup database..." this will break log shipping.
> Correct?
> I'm concerned w/ primary - to start log shipping you do a full backup to
> init, then tran log backups thereafter w/ each log shipped to secondary. I
> DO
> NOT want to do tran log backups forever... I eventually would like to do a
> full backup.
> Am I missing somehting...?
> cb
> "Kevin3NF" wrote:
>> You want a full backup of the primary? Just do Backup database...
>> You cannot backup the secondary as far as I know.
>> If you want to re-init log shipping and start clean on a system that LS
>> is
>> working flawlessly on, you aer simply wasting bandwidth and cpu. :)
>> --
>> 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.
>>
>> "Chris" <Chris@.discussions.microsoft.com> wrote in message
>> news:2E07F579-4A8A-47B6-B457-D7B543F00086@.microsoft.com...
>> >
>> > We have setup Log Shipping in SQL 2005. Working flawlessly. It appears
>> > that
>> > only tran log backup will occur forever unless we intervene. I do want
>> > a
>> > full
>> > backup to happen, you know, eventually...
>> >
>> > What is best way to automate this? Ideally, a full backup nightly would
>> > be
>> > great. How to do in script, or is there anything in gui?
>> >
>> > tia,
>> > chris
>>
Showing posts with label occur. Show all posts
Showing posts with label occur. Show all posts
Wednesday, March 21, 2012
Monday, March 12, 2012
Logn error
I'm having a bizarre error occur with one specific user. For starters, I hav
e
an SQL back-end with an Access data project front end. All of my users are
members of a SQLUSERS group, with the correct permissions.
When one specific user, Zack, logs into the db, he does so under the
SQLUSERS group. Everything runs smoothly until Zack tries to perform a
particular action that imports data from a fixed-width text file on CD. When
he does this, the system adds Zack as a separate user, even though he's
already part of the SQLUSERS group. The new Zack user inherits the
permissions from SQLUSERS, and during the data import process the system
creates new tables for Zack. Some fields don't have the correct data types,
which causes an error. Zack becomes the owner of these new import tables.
When any other member of SQLUSERS performs the same action, the system
deletes the data from, and reuses the existing tables.
Has anyone encountered anything similar to this?Hi
SQL Server will not create new users on it's own, therefore you have some
code that will be doing this. If your code is creating new (staging) tables
then zack will own them if he is not the dbo or a sysadmin. If the tables do
not already exist I would expect the same behaviour for other users that hav
e
the same privileges for Zack unless your code is conditional on who is
running it. If permissions are granted to the SQLUsers group other users may
be able to access and truncate the tables. For these users the code must kno
w
that Zack is the owner and referencing them using it.
You should review the code and/or use profiler to see what statements are
being sent to the database.
John
"mike" wrote:
> I'm having a bizarre error occur with one specific user. For starters, I h
ave
> an SQL back-end with an Access data project front end. All of my users are
> members of a SQLUSERS group, with the correct permissions.
> When one specific user, Zack, logs into the db, he does so under the
> SQLUSERS group. Everything runs smoothly until Zack tries to perform a
> particular action that imports data from a fixed-width text file on CD. Wh
en
> he does this, the system adds Zack as a separate user, even though he's
> already part of the SQLUSERS group. The new Zack user inherits the
> permissions from SQLUSERS, and during the data import process the system
> creates new tables for Zack. Some fields don't have the correct data types
,
> which causes an error. Zack becomes the owner of these new import tables.
> When any other member of SQLUSERS performs the same action, the system
> deletes the data from, and reuses the existing tables.
> Has anyone encountered anything similar to this?
e
an SQL back-end with an Access data project front end. All of my users are
members of a SQLUSERS group, with the correct permissions.
When one specific user, Zack, logs into the db, he does so under the
SQLUSERS group. Everything runs smoothly until Zack tries to perform a
particular action that imports data from a fixed-width text file on CD. When
he does this, the system adds Zack as a separate user, even though he's
already part of the SQLUSERS group. The new Zack user inherits the
permissions from SQLUSERS, and during the data import process the system
creates new tables for Zack. Some fields don't have the correct data types,
which causes an error. Zack becomes the owner of these new import tables.
When any other member of SQLUSERS performs the same action, the system
deletes the data from, and reuses the existing tables.
Has anyone encountered anything similar to this?Hi
SQL Server will not create new users on it's own, therefore you have some
code that will be doing this. If your code is creating new (staging) tables
then zack will own them if he is not the dbo or a sysadmin. If the tables do
not already exist I would expect the same behaviour for other users that hav
e
the same privileges for Zack unless your code is conditional on who is
running it. If permissions are granted to the SQLUsers group other users may
be able to access and truncate the tables. For these users the code must kno
w
that Zack is the owner and referencing them using it.
You should review the code and/or use profiler to see what statements are
being sent to the database.
John
"mike" wrote:
> I'm having a bizarre error occur with one specific user. For starters, I h
ave
> an SQL back-end with an Access data project front end. All of my users are
> members of a SQLUSERS group, with the correct permissions.
> When one specific user, Zack, logs into the db, he does so under the
> SQLUSERS group. Everything runs smoothly until Zack tries to perform a
> particular action that imports data from a fixed-width text file on CD. Wh
en
> he does this, the system adds Zack as a separate user, even though he's
> already part of the SQLUSERS group. The new Zack user inherits the
> permissions from SQLUSERS, and during the data import process the system
> creates new tables for Zack. Some fields don't have the correct data types
,
> which causes an error. Zack becomes the owner of these new import tables.
> When any other member of SQLUSERS performs the same action, the system
> deletes the data from, and reuses the existing tables.
> Has anyone encountered anything similar to this?
Subscribe to:
Posts (Atom)