fix logins

How do you create the logins with the same password, when
you backup and restore a database to a seperate server and
those logins do not exist at the server level?
AdamEither specify the SID that the user has in the database in your sp_addlogin
call, or just add the login and
fix the user's sid using sp_change_users_login, or use the KB article to exp
ort the logins from the source
server (search KB for sp_help_revlogin).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Adam" <anonymous@.discussions.microsoft.com> wrote in message news:12ade01c41874$f63ca8e0$a
001280a@.phx.gbl...
> How do you create the logins with the same password, when
> you backup and restore a database to a seperate server and
> those logins do not exist at the server level?
> Adam|||Thanks Tibor,
Does sp_change_users_login work for non-windows accounts?
What about adding the login and fix the user's sid? How
does that work for non-windows, how do I keep the
passwords from the database?

>--Original Message--
>Either specify the SID that the user has in the database
in your sp_addlogin call, or just add the login and
>fix the user's sid using sp_change_users_login, or use
the KB article to export the logins from the source
>server (search KB for sp_help_revlogin).
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"Adam" <anonymous@.discussions.microsoft.com> wrote in
message news:12ade01c41874$f63ca8e0$a001280a@.phx
.gbl...
when
and
>
>.
>|||This will not transfer the passwords. You can add a login
by using sp_addlogin and then map it to the user in the
database but for that you will have to know all the
passwords. sp_help_revlogin will move the passwords for
you.
You can also move the logins by using Login Transfer task
in DTS wizard.
Obaid
>--Original Message--
>Thanks Tibor,
>Does sp_change_users_login work for non-windows accounts?
>What about adding the login and fix the user's sid? How
>does that work for non-windows, how do I keep the
>passwords from the database?
>
>in your sp_addlogin call, or just add the login and
>the KB article to export the logins from the source
>message news:12ade01c41874$f63ca8e0$a001280a@.phx
.gbl...
>when
>and
>.
>|||> Does sp_change_users_login work for non-windows accounts?
Yes, it is used exactly for SQL Server logins.

> What about adding the login and fix the user's sid?
That is another option. See Books Online, sp_addlogin, and you'll find a par
ameter for specifying the SID.
Again, search KB for sp_help_revlogin and you'll find an a article with whic
h you can export all logins from
one server to another.

> How
> does that work for non-windows, how do I keep the
> passwords from the database?
It work just fine for non-windows accounts. I'm not sure I understand the pa
rt about password. There's no
password stored inside a database, only in master.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Adam" <anonymous@.discussions.microsoft.com> wrote in message news:17c1601c418d4$d21fcf90$a
101280a@.phx.gbl...
> Thanks Tibor,
> Does sp_change_users_login work for non-windows accounts?
> What about adding the login and fix the user's sid? How
> does that work for non-windows, how do I keep the
> passwords from the database?
>
> in your sp_addlogin call, or just add the login and
> the KB article to export the logins from the source
> message news:12ade01c41874$f63ca8e0$a001280a@.phx
.gbl...
> when
> and

fix logins

How do you create the logins with the same password, when
you backup and restore a database to a seperate server and
those logins do not exist at the server level?
Adam
Either specify the SID that the user has in the database in your sp_addlogin call, or just add the login and
fix the user's sid using sp_change_users_login, or use the KB article to export the logins from the source
server (search KB for sp_help_revlogin).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Adam" <anonymous@.discussions.microsoft.com> wrote in message news:12ade01c41874$f63ca8e0$a001280a@.phx.gbl...
> How do you create the logins with the same password, when
> you backup and restore a database to a seperate server and
> those logins do not exist at the server level?
> Adam
|||Thanks Tibor,
Does sp_change_users_login work for non-windows accounts?
What about adding the login and fix the user's sid? How
does that work for non-windows, how do I keep the
passwords from the database?

>--Original Message--
>Either specify the SID that the user has in the database
in your sp_addlogin call, or just add the login and
>fix the user's sid using sp_change_users_login, or use
the KB article to export the logins from the source
>server (search KB for sp_help_revlogin).
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"Adam" <anonymous@.discussions.microsoft.com> wrote in
message news:12ade01c41874$f63ca8e0$a001280a@.phx.gbl...
when
and
>
>.
>
|||This will not transfer the passwords. You can add a login
by using sp_addlogin and then map it to the user in the
database but for that you will have to know all the
passwords. sp_help_revlogin will move the passwords for
you.
You can also move the logins by using Login Transfer task
in DTS wizard.
Obaid
>--Original Message--
>Thanks Tibor,
>Does sp_change_users_login work for non-windows accounts?
>What about adding the login and fix the user's sid? How
>does that work for non-windows, how do I keep the
>passwords from the database?
>
>in your sp_addlogin call, or just add the login and
>the KB article to export the logins from the source
>message news:12ade01c41874$f63ca8e0$a001280a@.phx.gbl...
>when
>and
>.
>
|||> Does sp_change_users_login work for non-windows accounts?
Yes, it is used exactly for SQL Server logins.

> What about adding the login and fix the user's sid?
That is another option. See Books Online, sp_addlogin, and you'll find a parameter for specifying the SID.
Again, search KB for sp_help_revlogin and you'll find an a article with which you can export all logins from
one server to another.

> How
> does that work for non-windows, how do I keep the
> passwords from the database?
It work just fine for non-windows accounts. I'm not sure I understand the part about password. There's no
password stored inside a database, only in master.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Adam" <anonymous@.discussions.microsoft.com> wrote in message news:17c1601c418d4$d21fcf90$a101280a@.phx.gbl...
> Thanks Tibor,
> Does sp_change_users_login work for non-windows accounts?
> What about adding the login and fix the user's sid? How
> does that work for non-windows, how do I keep the
> passwords from the database?
>
> in your sp_addlogin call, or just add the login and
> the KB article to export the logins from the source
> message news:12ade01c41874$f63ca8e0$a001280a@.phx.gbl...
> when
> and

Fix Bad Data Error After Restore

Our test server had a hardware failuare and I restored the Report Server db's and app - no problem - so it seemed. I am getting a Bad Data Error when trying to run a report. From a previous post I see the issue relates to a different encryption key being used. The autoher noted to fix by reloading catalog.sql. If I do that, won;t i lose the previous deployed reports settings, descriptions etc. Is there a way to keep that info without having to manually redeploy if a hardware failure occurs'Yes, but you must backup (before the failure) and restore the key
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jen" <Jen@.discussions.microsoft.com> wrote in message
news:46813D69-6259-4A82-BA7F-881C52616518@.microsoft.com...
> Our test server had a hardware failuare and I restored the Report Server
db's and app - no problem - so it seemed. I am getting a Bad Data Error
when trying to run a report. From a previous post I see the issue relates
to a different encryption key being used. The autoher noted to fix by
reloading catalog.sql. If I do that, won;t i lose the previous deployed
reports settings, descriptions etc. Is there a way to keep that info
without having to manually redeploy if a hardware failure occurs'|||Ah - I did back up and was able to restore. What is the mysterious key?
The only painful part of the server restore was redeploying and reconfiguring RSS (reports in the right folders, group permissions, etc). After restoring ReportServer db to the server and getting the bad data error, I then restored the ReportServer db to my local PC and copied and pasted necessary report descriptions and other info from the previous install back into the new install using the web interface. It was not terrible but it would have been much nicer to just have restored the ReportServer db versus the redeploy/reconfigure. Is redeploy/reconfigure the only way to recover from hardware failure? Am I missing something with regards to how to do recover better in the event hardware fails again?
All my jobs, db's, etc were operation from restored backups.
"Jason Carlson [MSFT]" wrote:
> Yes, but you must backup (before the failure) and restore the key
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Jen" <Jen@.discussions.microsoft.com> wrote in message
> news:46813D69-6259-4A82-BA7F-881C52616518@.microsoft.com...
> > Our test server had a hardware failuare and I restored the Report Server
> db's and app - no problem - so it seemed. I am getting a Bad Data Error
> when trying to run a report. From a previous post I see the issue relates
> to a different encryption key being used. The autoher noted to fix by
> reloading catalog.sql. If I do that, won;t i lose the previous deployed
> reports settings, descriptions etc. Is there a way to keep that info
> without having to manually redeploy if a hardware failure occurs'
>
>|||Look for the topic "key management" in Books Online. You use the rskeymgmt
utility to backup and restore the encryption key.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jen" <Jen@.discussions.microsoft.com> wrote in message
news:8463A8BA-A3A9-4AD6-8864-60A537234A19@.microsoft.com...
> Ah - I did back up and was able to restore. What is the mysterious key?
> The only painful part of the server restore was redeploying and
reconfiguring RSS (reports in the right folders, group permissions, etc).
After restoring ReportServer db to the server and getting the bad data
error, I then restored the ReportServer db to my local PC and copied and
pasted necessary report descriptions and other info from the previous
install back into the new install using the web interface. It was not
terrible but it would have been much nicer to just have restored the
ReportServer db versus the redeploy/reconfigure. Is redeploy/reconfigure
the only way to recover from hardware failure? Am I missing something
with regards to how to do recover better in the event hardware fails again?
>
> All my jobs, db's, etc were operation from restored backups.
> "Jason Carlson [MSFT]" wrote:
> > Yes, but you must backup (before the failure) and restore the key
> >
> > --
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Jen" <Jen@.discussions.microsoft.com> wrote in message
> > news:46813D69-6259-4A82-BA7F-881C52616518@.microsoft.com...
> > > Our test server had a hardware failuare and I restored the Report
Server
> > db's and app - no problem - so it seemed. I am getting a Bad Data
Error
> > when trying to run a report. From a previous post I see the issue
relates
> > to a different encryption key being used. The autoher noted to fix by
> > reloading catalog.sql. If I do that, won;t i lose the previous deployed
> > reports settings, descriptions etc. Is there a way to keep that info
> > without having to manually redeploy if a hardware failure occurs'
> >
> >
> >