Logshipping question

Win 2K Adv Server SQL2K sp3a
I have implemented logshipping from server A to server B monitor
server C following the instructions
Everything works fine, every 15 minutes the Backup, Copy and Restore
jobs run
But the destination database is in Loading io Read Only
What is wrong ?
TIA
Jan Waumans<jw@.jw.com> wrote in message
news:8ef6601rfk0kg6i68vb539q1d6ap43op3v@.
4ax.com...
> Win 2K Adv Server SQL2K sp3a
> I have implemented logshipping from server A to server B monitor
> server C following the instructions
> Everything works fine, every 15 minutes the Backup, Copy and Restore
> jobs run
> But the destination database is in Loading io Read Only
> What is wrong ?
When the logs are restored onto server B they are restored WITH NO RECOVERY.
In other words the logs are not rolled forward to make the database
consistent. It is waiting for the next set of logs. If the database was
not read-only then if people made changes to the Server B database you would
not be able to read the next shipped logs.
If you want to have an updatable copy of your database where changes are
replicated every 15 minutes you might wnat to take a peek at replication.|||Bob,
I use replication since 6.0
The reason I want to go to logshipping is that replication is too
difficult to maintain for recovery sites (no schema changes except
with the unusable additional column in 2K mode, only 1 logreader per
published database, ...)
Since in Win2K you can restore a DB in read-only state allowing
additional log restores, I figure this is what logshipping should do
How the destination db could be usable anyway?
Our setup as disaster recovery does not need an access to the
destination db's in normal circumstances, but we need to be able to
switch over in case of emergency
MS clearly states that logshipping is a better solution for disaster
recovery than replication
I must do something wrong
JW
On Thu, 25 Mar 2004 20:42:59 -0000, "Bob Simms"
<bob_simms@.somewhere.com> wrote:

><jw@.jw.com> wrote in message
> news:8ef6601rfk0kg6i68vb539q1d6ap43op3v@.
4ax.com...
>When the logs are restored onto server B they are restored WITH NO RECOVERY
.
>In other words the logs are not rolled forward to make the database
>consistent. It is waiting for the next set of logs. If the database was
>not read-only then if people made changes to the Server B database you woul
d
>not be able to read the next shipped logs.
>If you want to have an updatable copy of your database where changes are
>replicated every 15 minutes you might wnat to take a peek at replication.
>|||log shipping is better than replication in case you want to have the second
server for stand-by. You can read DBs on stand-by server as long as the log
restore is not running. In your case there is nothing wrong when you see
the DB in single user mode.
<jw@.jw.com> wrote in message
news:2dh660tsgo13lv90e53dquf1c03jcren8m@.
4ax.com...
> Bob,
> I use replication since 6.0
> The reason I want to go to logshipping is that replication is too
> difficult to maintain for recovery sites (no schema changes except
> with the unusable additional column in 2K mode, only 1 logreader per
> published database, ...)
> Since in Win2K you can restore a DB in read-only state allowing
> additional log restores, I figure this is what logshipping should do
> How the destination db could be usable anyway?
> Our setup as disaster recovery does not need an access to the
> destination db's in normal circumstances, but we need to be able to
> switch over in case of emergency
> MS clearly states that logshipping is a better solution for disaster
> recovery than replication
> I must do something wrong
> JW
>
> On Thu, 25 Mar 2004 20:42:59 -0000, "Bob Simms"
> <bob_simms@.somewhere.com> wrote:
>
RECOVERY.
would
>|||Study the docs in books on line referring to Log Shipping... There is a
procedure you must go through to make the log ship databases Primary, in the
case of failure.. There is a DTS job and some exports involved... You'd be
well served to test this and ensure you have a good plan...
But until you run recovery on the secondary ( part of the process) it will
show as loading...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.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
<jw@.jw.com> wrote in message
news:8ef6601rfk0kg6i68vb539q1d6ap43op3v@.
4ax.com...
> Win 2K Adv Server SQL2K sp3a
> I have implemented logshipping from server A to server B monitor
> server C following the instructions
> Everything works fine, every 15 minutes the Backup, Copy and Restore
> jobs run
> But the destination database is in Loading io Read Only
> What is wrong ?
> TIA
> Jan Waumans

logins

I am confused about windows account, win dimain account, sql login
accoun and sql database user account... can you give me a fresh
example to show the exact relationship between them and how they work
together?From the Books Online:

<Excerpt href="http://links.10026.com/?link=architec.chm::/8_ar_cs_79kj.htm">
A login ID only enables you to connect to an instance of SQL Server.
Permissions within specific databases are controlled by user accounts. The
database administrator maps your login account to a user account in any
database you are authorized to access.
</Excerpt
Below is a brief summary. I suggest you peruse the Books Online for a
thorough description.

There are 2 basic types of logins: SQL accounts and Windows accounts. SQL
authenticated logins are managed entirely within SQL Server and it is SQL
Server that checks the login password to validate login identity. You
create a new SQL Login using sp_addlogin or using Enterprise Manager.

In contrast, Windows accounts (both local computer and domain accounts) are
managed by Windows so it is Windows that validates the identity of those
logins. You grant an existing Windows user or group account permissions to
connect to a SQL server instance with sp_grantlogin or using Enterprise
Manager.

A login initially has limited permissions; only those databases with the
guest user enabled (e.g. master and tempdb) can be accessed. You can grant
a login permissions to access other databases with sp_grantdbaccess,
sp_adduser or Enterprise Manager. When database access is granted, a
database user is created that is used as the security context within that
database. You can then grant permissions to the user, or better yet, add
the user to roles so that you can manage permissions via role database
membership.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"David McGeorge" <soalvajavab1@.yahoo.com> wrote in message
news:bc907f76.0411200816.6f9df9b0@.posting.google.c om...
>I am confused about windows account, win dimain account, sql login
> accoun and sql database user account... can you give me a fresh
> example to show the exact relationship between them and how they work
> together?

Login to MSDE on Win 98

Hi all,

I have the the problem with logging to MSDE using SQL-DMO interface. On the
W2K with LoginSecure=TRUE everything is OK (connect is made without any
parameters)

But when LoginSecure=FALSE (on Win 98)

connect( 'instance_name', 'sa', 'sa_password' )

then it returns error message :

Login failed for user 'sa'. Reason : Not associated with a trusted SQL

I install MSDE on Win 98 with parameters :

INSTANCENAME='instance_name'
SECURITYMODE=SQL
SAPWD='sa_password'

Server runs with given instance name.

Who knows why I can not login to MSDE ?

TIA,

Marek Powichrowski"Marek Powichrowski" <marekp@.telbank.pl> wrote in message
news:bv81ss$hnp$1@.korweta.task.gda.pl...
> Hi all,
> I have the the problem with logging to MSDE using SQL-DMO interface. On
the
> W2K with LoginSecure=TRUE everything is OK (connect is made without any
> parameters)
> But when LoginSecure=FALSE (on Win 98)
> connect( 'instance_name', 'sa', 'sa_password' )
> then it returns error message :
> Login failed for user 'sa'. Reason : Not associated with a trusted SQL
> I install MSDE on Win 98 with parameters :
> INSTANCENAME='instance_name'
> SECURITYMODE=SQL
> SAPWD='sa_password'
> Server runs with given instance name.
> Who knows why I can not login to MSDE ?
> TIA,
> Marek Powichrowski

The error is slightly strange, since it suggests MSDE is running in Windows
authentication mode, however that isn't supported on Windows 98. Can you
connect to the MSDE instance locally using osql, for example?

osql -S instance_name -U sa -P sa_password

If you can connect like this, then the issue is probably somewhere in your
SQLDMO code, and perhaps you could post the part which makes the connection.
If this doesn't work, then could you post the error message? And did you
install the latest MSDE version, ie. SP3a?

Simon|||>
> The error is slightly strange, since it suggests MSDE is running in
Windows
> authentication mode, however that isn't supported on Windows 98. Can you
> connect to the MSDE instance locally using osql, for example?
> osql -S instance_name -U sa -P sa_password
> If you can connect like this, then the issue is probably somewhere in your
> SQLDMO code, and perhaps you could post the part which makes the
connection.
> If this doesn't work, then could you post the error message? And did you
> install the latest MSDE version, ie. SP3a?

Cause of error was setting LoginSecure to TRUE for the connection made on
the Win 98. When I change LoginSecure to FALSE then connection ends
succesfully (for proper server name user name and password) . So I can
create database using script generated by Enterprise Manager from my
computer and can atatch existing database to MSDE without Enterprise Manager
in the easy way (few lines of code).

Thanks for your support.

Marek Powichrowski

Login problem when scheduling a dts package

Hi.
(Environment: Win 2000 Server sp. 4. MS SQL 7.0 sp 4)
As me, some of you might use the "Scedule Package" option on dts packages to
let the SQL server generate a job, and then copy the "Operating System
Command" string into another job which bundles together a set of dts
packages in one scheduled job.
My problem now is when I rightclick a DTS package and select "Schedule
Package" I get a [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed
for user ' '. It got no detailed error number as the one you get on the
error: "...not assosiated with a trusted SQL connection..." stuff. It only
gives the general SQLState: 28000 error.
We have done a lot off stuff on our domain lately (converted to AD), but it
worked allright yesterday, but after a reboot this morning I got the above
issue.
Where should I start looking? Where do I set the login account which is used
when generating a job from a DTS Package? The Server Agent runs normaly, and
I'm logged into the server with the same ID which have created and owns the
DTS package
Please give me a resource URL or a hint on the above, if you have any
expiriences...
Regards
Mr. SmithThe problem with Authentication, can you provide for the DTS package, to
Windows authentication mode. so that the package run successfully. i faced
same problem.some R&D i fix that issue. can you proceed with windows
authentication.
still u have problem let me know.
"Mr. Smith" wrote:
> Hi.
> (Environment: Win 2000 Server sp. 4. MS SQL 7.0 sp 4)
> As me, some of you might use the "Scedule Package" option on dts packages to
> let the SQL server generate a job, and then copy the "Operating System
> Command" string into another job which bundles together a set of dts
> packages in one scheduled job.
> My problem now is when I rightclick a DTS package and select "Schedule
> Package" I get a [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed
> for user ' '. It got no detailed error number as the one you get on the
> error: "...not assosiated with a trusted SQL connection..." stuff. It only
> gives the general SQLState: 28000 error.
> We have done a lot off stuff on our domain lately (converted to AD), but it
> worked allright yesterday, but after a reboot this morning I got the above
> issue.
> Where should I start looking? Where do I set the login account which is used
> when generating a job from a DTS Package? The Server Agent runs normaly, and
> I'm logged into the server with the same ID which have created and owns the
> DTS package
> Please give me a resource URL or a hint on the above, if you have any
> expiriences...
> Regards
> Mr. Smith
>
>

Login problem when scheduling a dts package

Hi.
(Environment: Win 2000 Server sp. 4. MS SQL 7.0 sp 4)
As me, some of you might use the "Scedule Package" option on dts packages to
let the SQL server generate a job, and then copy the "Operating System
Command" string into another job which bundles together a set of dts
packages in one scheduled job.
My problem now is when I rightclick a DTS package and select "Schedule
Package" I get a [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed
for user ' '. It got no detailed error number as the one you get on the
error: "...not assosiated with a trusted SQL connection..." stuff. It only
gives the general SQLState: 28000 error.
We have done a lot off stuff on our domain lately (converted to AD), but it
worked allright yesterday, but after a reboot this morning I got the above
issue.
Where should I start looking? Where do I set the login account which is used
when generating a job from a DTS Package? The Server Agent runs normaly, and
I'm logged into the server with the same ID which have created and owns the
DTS package
Please give me a resource URL or a hint on the above, if you have any
expiriences...
Regards
Mr. Smith
The problem with Authentication, can you provide for the DTS package, to
Windows authentication mode. so that the package run successfully. i faced
same problem.some R&D i fix that issue. can you proceed with windows
authentication.
still u have problem let me know.
"Mr. Smith" wrote:

> Hi.
> (Environment: Win 2000 Server sp. 4. MS SQL 7.0 sp 4)
> As me, some of you might use the "Scedule Package" option on dts packages to
> let the SQL server generate a job, and then copy the "Operating System
> Command" string into another job which bundles together a set of dts
> packages in one scheduled job.
> My problem now is when I rightclick a DTS package and select "Schedule
> Package" I get a [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed
> for user ' '. It got no detailed error number as the one you get on the
> error: "...not assosiated with a trusted SQL connection..." stuff. It only
> gives the general SQLState: 28000 error.
> We have done a lot off stuff on our domain lately (converted to AD), but it
> worked allright yesterday, but after a reboot this morning I got the above
> issue.
> Where should I start looking? Where do I set the login account which is used
> when generating a job from a DTS Package? The Server Agent runs normaly, and
> I'm logged into the server with the same ID which have created and owns the
> DTS package
> Please give me a resource URL or a hint on the above, if you have any
> expiriences...
> Regards
> Mr. Smith
>
>

Login problem when scheduling a dts package

Hi.
(Environment: Win 2000 Server sp. 4. MS SQL 7.0 sp 4)
As me, some of you might use the "Scedule Package" option on dts packages to
let the SQL server generate a job, and then copy the "Operating System
Command" string into another job which bundles together a set of dts
packages in one scheduled job.
My problem now is when I rightclick a DTS package and select "Schedule
Package" I get a [Microsoft][ODBC SQL Server Driver][SQL Server]
Login failed
for user ' '. It got no detailed error number as the one you get on the
error: "...not assosiated with a trusted SQL connection..." stuff. It only
gives the general SQLState: 28000 error.
We have done a lot off stuff on our domain lately (converted to AD), but it
worked allright yesterday, but after a reboot this morning I got the above
issue.
Where should I start looking? Where do I set the login account which is used
when generating a job from a DTS Package? The Server Agent runs normaly, and
I'm logged into the server with the same ID which have created and owns the
DTS package
Please give me a resource URL or a hint on the above, if you have any
expiriences...
Regards
Mr. SmithThe problem with Authentication, can you provide for the DTS package, to
Windows authentication mode. so that the package run successfully. i faced
same problem.some R&D i fix that issue. can you proceed with windows
authentication.
still u have problem let me know.
"Mr. Smith" wrote:

> Hi.
> (Environment: Win 2000 Server sp. 4. MS SQL 7.0 sp 4)
> As me, some of you might use the "Scedule Package" option on dts packages
to
> let the SQL server generate a job, and then copy the "Operating System
> Command" string into another job which bundles together a set of dts
> packages in one scheduled job.
> My problem now is when I rightclick a DTS package and select "Schedule
> Package" I get a [Microsoft][ODBC SQL Server Driver][SQL Serve
r]Login failed
> for user ' '. It got no detailed error number as the one you get on the
> error: "...not assosiated with a trusted SQL connection..." stuff. It onl
y
> gives the general SQLState: 28000 error.
> We have done a lot off stuff on our domain lately (converted to AD), but i
t
> worked allright yesterday, but after a reboot this morning I got the above
> issue.
> Where should I start looking? Where do I set the login account which is us
ed
> when generating a job from a DTS Package? The Server Agent runs normaly, a
nd
> I'm logged into the server with the same ID which have created and owns th
e
> DTS package
> Please give me a resource URL or a hint on the above, if you have any
> expiriences...
> Regards
> Mr. Smith
>
>