Logs Shipping ReInit - how to?

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
>>

login works with SQL but not MSDE

Any idea why the following dmo connection string would not work on MSDE, but
does work on SQL Personal Edition? It appears to connects, but then can't
find the server name. In both cases we are using the latest SQL Personal,
MSDE, and Windows XP.
Thanks for any guidance.
Neil
connection string:
server=myserver;trusted_connection="yes";database= northwind;connection
timeout=10;
exception:
[INFO] 20040517 17:59:34.598 (myControl) Connected successfully to
server=VPC1W2KSQL\VPC1MSDE;Trusted_Connection=yes; database=master;connection
timeout=10;
[EXCEPTION] 20040517 17:59:51.352 (SQLServer) Cannot connect
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
at SQLDMO.SQLServerClass.Connect(Object ServerName, Object Login, Object
Password)
at SQLServer.Connect()
Was MSDE installed with the network protocols enabled? With SP3a they are
turned off by default.
Jim
"Neil W." <neilw@.netlib.com> wrote in message
news:eC6V4XdPEHA.1276@.TK2MSFTNGP11.phx.gbl...
> Any idea why the following dmo connection string would not work on MSDE,
but
> does work on SQL Personal Edition? It appears to connects, but then can't
> find the server name. In both cases we are using the latest SQL Personal,
> MSDE, and Windows XP.
> Thanks for any guidance.
> Neil
> connection string:
> server=myserver;trusted_connection="yes";database= northwind;connection
> timeout=10;
> exception:
> [INFO] 20040517 17:59:34.598 (myControl) Connected successfully to
>
server=VPC1W2KSQL\VPC1MSDE;Trusted_Connection=yes; database=master;connection
> timeout=10;
> [EXCEPTION] 20040517 17:59:51.352 (SQLServer) Cannot connect
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> at SQLDMO.SQLServerClass.Connect(Object ServerName, Object Login,
Object
> Password)
> at SQLServer.Connect()
>
|||This took me a little bit further. I can now actually see the tables in in
my program using the dmo calls. Thanks! owever, when I try to access the
individual columns, I continue to get errors such as:
EXCEPTION] 20040520 08:37:30.955 (sqlserver.myObject) Error retrieving info
from test2: Server user 'mymachine\mylogin' is not a valid user in database
'test2'.
Again, this all works fine using SQL Personal Edition.
Neil
"Jim Young" <thorium48@.hotmail.com> wrote in message
Was MSDE installed with the network protocols enabled? With SP3a they are
turned off by default.
Jim
"Neil W." <neilw@.netlib.com> wrote in message
news:eC6V4XdPEHA.1276@.TK2MSFTNGP11.phx.gbl...
> Any idea why the following dmo connection string would not work on MSDE,
but
> does work on SQL Personal Edition? It appears to connects, but then can't
> find the server name. In both cases we are using the latest SQL Personal,
> MSDE, and Windows XP.
> Thanks for any guidance.
> Neil
> connection string:
> server=myserver;trusted_connection="yes";database= northwind;connection
> timeout=10;
> exception:
> [INFO] 20040517 17:59:34.598 (myControl) Connected successfully to
>
server=VPC1W2KSQL\VPC1MSDE;Trusted_Connection=yes; database=master;connection
> timeout=10;
> [EXCEPTION] 20040517 17:59:51.352 (SQLServer) Cannot connect
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> at SQLDMO.SQLServerClass.Connect(Object ServerName, Object Login,
Object
> Password)
> at SQLServer.Connect()
>
|||Carefully read the error message. You need to make the user you are
connecting with, in this case a Windows login, a user in the database you
are trying to use. Everyone that can connect to a server can see the schema
of any database, but you can't select or change any data until you are given
explicit permissions in a database.
Jim
"Neil W." <neilw@.netlib.com> wrote in message
news:OShgsvmPEHA.2468@.TK2MSFTNGP11.phx.gbl...
> This took me a little bit further. I can now actually see the tables in
in
> my program using the dmo calls. Thanks! owever, when I try to access the
> individual columns, I continue to get errors such as:
> EXCEPTION] 20040520 08:37:30.955 (sqlserver.myObject) Error retrieving
info
> from test2: Server user 'mymachine\mylogin' is not a valid user in
database[vbcol=seagreen]
> 'test2'.
> Again, this all works fine using SQL Personal Edition.
> Neil
>
> "Jim Young" <thorium48@.hotmail.com> wrote in message
> Was MSDE installed with the network protocols enabled? With SP3a they are
> turned off by default.
> Jim
> "Neil W." <neilw@.netlib.com> wrote in message
> news:eC6V4XdPEHA.1276@.TK2MSFTNGP11.phx.gbl...
> but
can't[vbcol=seagreen]
Personal,
>
server=VPC1W2KSQL\VPC1MSDE;Trusted_Connection=yes; database=master;connection[vbcol=seagreen]
or
> Object
>
>

Login problem with Windows Authentication

I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
BillFor Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegroups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>

Login problem with Windows Authentication

I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
Bill
For Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegr oups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>

Login problem with Windows Authentication

I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
BillFor Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegroups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>