Hi guys
We are closing down our old test server. This server used to run RS. Is
there any documentation on how to move the RS installation to another server
so that Reports, Schedules etc. is intact and ready for use on the new
server?
Thanks.
Regards
JonasJonas,
You may find my post useful
http://prologika.com/blog/archive/2004/08/20/161.aspx
Let me know if you find discrepancies.
--
Hope this helps.
----
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
----
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
news:O9WLxgkjEHA.1136@.tk2msftngp13.phx.gbl...
> Hi guys
> We are closing down our old test server. This server used to run RS. Is
> there any documentation on how to move the RS installation to another
server
> so that Reports, Schedules etc. is intact and ready for use on the new
> server?
> Thanks.
> Regards
> Jonas
>|||Hi Teo
My current version of various sw does not support web farms therefore I had
to:
- Remove the key in the new server: rskeymgmt -r[InstallationID]
(InstallationId is in the RSReportServer.Config file).
- Swap the installation id in the actual RSReportServer.Config file with
the old one.
- Run rskeymgmt -a -f -p
Regards
Jonas
"Teo Lachev" <teo.lachev@.nospam.prologika.com> wrote in message
news:uYUkuAojEHA.3972@.tk2msftngp13.phx.gbl...
> Jonas,
> You may find my post useful
> http://prologika.com/blog/archive/2004/08/20/161.aspx
> Let me know if you find discrepancies.
> --
> Hope this helps.
> ----
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ----
> "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> news:O9WLxgkjEHA.1136@.tk2msftngp13.phx.gbl...
> > Hi guys
> >
> > We are closing down our old test server. This server used to run RS. Is
> > there any documentation on how to move the RS installation to another
> server
> > so that Reports, Schedules etc. is intact and ready for use on the new
> > server?
> >
> > Thanks.
> >
> > Regards
> > Jonas
> >
> >
>
Showing posts with label old. Show all posts
Showing posts with label old. Show all posts
Sunday, March 11, 2012
Wednesday, March 7, 2012
Changing ownership of a SQL server 7 database
We recently changed the network administrator username on
the network where I work but all of our SQL 7 databases
still show the old name as the owner. How can this be
changed? thanks.Hi,
Use the below procedure in Query analyzer to change database owner,
sp_changedbowner 'Login_name'
Thanks
Hari
MCDBA
"Ken" <kklasser@.mindspring.com> wrote in message
news:e86601c3f070$3ad66b80$a601280a@.phx.gbl...
> We recently changed the network administrator username on
> the network where I work but all of our SQL 7 databases
> still show the old name as the owner. How can this be
> changed? thanks.
the network where I work but all of our SQL 7 databases
still show the old name as the owner. How can this be
changed? thanks.Hi,
Use the below procedure in Query analyzer to change database owner,
sp_changedbowner 'Login_name'
Thanks
Hari
MCDBA
"Ken" <kklasser@.mindspring.com> wrote in message
news:e86601c3f070$3ad66b80$a601280a@.phx.gbl...
> We recently changed the network administrator username on
> the network where I work but all of our SQL 7 databases
> still show the old name as the owner. How can this be
> changed? thanks.
Sunday, February 19, 2012
Changing ID globally ...
Hi,
We have a help desk application with MS SQL Server backend which is at least
10 years old. This application mainly has 2 tables -
1. One for storing customer ID (Cust_Profile Table) and the
2. Other one for storing all the call details pertaining to customers.
Apart from these two main tables, there are other tables for storing informa
tion like configuration, history etc related to the customer.
My requirement is - I want to change the customer ID globally across the sys
tem. But I am not too sure as to how to proceed. Any suggestions/ideas welc
ome.
Thanks in advance,
HarishHarish,
Review the following psuedocode use the following as guideline only...do not
do this directly on the production system and please test it on the staging
or dev env.
-- NO IDENTITY PROPERTY
Pause access to the database from the Application
Drop any Foreign Keys between tables binding the Customer Key
Begin transaction
UPDATE table1 ..
Check for Errors...rollback if needed.
UPDATE table2...
Check for Errors...rollback if needed
Commit Transaction
-- YES IDENTITY PROPERTY
Check if the Customer ID is of an Identity property
Pause access to the database from the Application
If it is of Identity property you can not Update you have to write a
migration utility
You may have to Create a shadow table with same schema as Customer Profile
(Without Identity Property on ID column)
Copy Data from Base Table (Original) to Shadow Table
Update the Value (Old ID - New ID) in the Shadow Table
Drop any Foreign Keys between tables binding the Customer Key
Begin transaction
DELETE Base Table (Original) -- Use Delete instead of Truncate for
Rollback purposes
Check for Errors...rollback if needed.
SET IDENTITY_INSERT Base Table ON
INSERT Base Table (Collist) SELECT Collist From Shadow Table
SET IDENTITY_INSERT Base Table OFF
UPDATE table2...
Check for Errors...rollback if needed
Commit Transaction
Resume Access to the database from the Application
HTH
Satish Balusa
"Harish Mohanbabu" <anonymous@.discussions.microsoft.com> wrote in message
news:248AB598-83B4-4611-92E3-BE336DA65170@.microsoft.com...
least 10 years old. This application mainly has 2 tables -
information like configuration, history etc related to the customer.
system. But I am not too sure as to how to proceed. Any suggestions/ideas
welcome.
We have a help desk application with MS SQL Server backend which is at least
10 years old. This application mainly has 2 tables -
1. One for storing customer ID (Cust_Profile Table) and the
2. Other one for storing all the call details pertaining to customers.
Apart from these two main tables, there are other tables for storing informa
tion like configuration, history etc related to the customer.
My requirement is - I want to change the customer ID globally across the sys
tem. But I am not too sure as to how to proceed. Any suggestions/ideas welc
ome.
Thanks in advance,
HarishHarish,
Review the following psuedocode use the following as guideline only...do not
do this directly on the production system and please test it on the staging
or dev env.
-- NO IDENTITY PROPERTY
Pause access to the database from the Application
Drop any Foreign Keys between tables binding the Customer Key
Begin transaction
UPDATE table1 ..
Check for Errors...rollback if needed.
UPDATE table2...
Check for Errors...rollback if needed
Commit Transaction
-- YES IDENTITY PROPERTY
Check if the Customer ID is of an Identity property
Pause access to the database from the Application
If it is of Identity property you can not Update you have to write a
migration utility
You may have to Create a shadow table with same schema as Customer Profile
(Without Identity Property on ID column)
Copy Data from Base Table (Original) to Shadow Table
Update the Value (Old ID - New ID) in the Shadow Table
Drop any Foreign Keys between tables binding the Customer Key
Begin transaction
DELETE Base Table (Original) -- Use Delete instead of Truncate for
Rollback purposes
Check for Errors...rollback if needed.
SET IDENTITY_INSERT Base Table ON
INSERT Base Table (Collist) SELECT Collist From Shadow Table
SET IDENTITY_INSERT Base Table OFF
UPDATE table2...
Check for Errors...rollback if needed
Commit Transaction
Resume Access to the database from the Application
HTH
Satish Balusa
"Harish Mohanbabu" <anonymous@.discussions.microsoft.com> wrote in message
news:248AB598-83B4-4611-92E3-BE336DA65170@.microsoft.com...
quote:
> Hi,
> We have a help desk application with MS SQL Server backend which is at
least 10 years old. This application mainly has 2 tables -
quote:
> 1. One for storing customer ID (Cust_Profile Table) and the
> 2. Other one for storing all the call details pertaining to customers.
> Apart from these two main tables, there are other tables for storing
information like configuration, history etc related to the customer.
quote:
> My requirement is - I want to change the customer ID globally across the
system. But I am not too sure as to how to proceed. Any suggestions/ideas
welcome.
quote:
> Thanks in advance,
> Harish
Changing ID globally ...
Hi
We have a help desk application with MS SQL Server backend which is at least 10 years old. This application mainly has 2 tables -
1. One for storing customer ID (Cust_Profile Table) and th
2. Other one for storing all the call details pertaining to customers.
Apart from these two main tables, there are other tables for storing information like configuration, history etc related to the customer
My requirement is - I want to change the customer ID globally across the system. But I am not too sure as to how to proceed. Any suggestions/ideas welcome
Thanks in advance
HarishHarish,
Review the following psuedocode use the following as guideline only...do not
do this directly on the production system and please test it on the staging
or dev env.
-- NO IDENTITY PROPERTY
Pause access to the database from the Application
Drop any Foreign Keys between tables binding the Customer Key
Begin transaction
UPDATE table1 ..
Check for Errors...rollback if needed.
UPDATE table2...
Check for Errors...rollback if needed
Commit Transaction
-- YES IDENTITY PROPERTY
Check if the Customer ID is of an Identity property
Pause access to the database from the Application
If it is of Identity property you can not Update you have to write a
migration utility
You may have to Create a shadow table with same schema as Customer Profile
(Without Identity Property on ID column)
Copy Data from Base Table (Original) to Shadow Table
Update the Value (Old ID - New ID) in the Shadow Table
Drop any Foreign Keys between tables binding the Customer Key
Begin transaction
DELETE Base Table (Original) -- Use Delete instead of Truncate for
Rollback purposes
Check for Errors...rollback if needed.
SET IDENTITY_INSERT Base Table ON
INSERT Base Table (Collist) SELECT Collist From Shadow Table
SET IDENTITY_INSERT Base Table OFF
UPDATE table2...
Check for Errors...rollback if needed
Commit Transaction
Resume Access to the database from the Application
--
HTH
Satish Balusa
"Harish Mohanbabu" <anonymous@.discussions.microsoft.com> wrote in message
news:248AB598-83B4-4611-92E3-BE336DA65170@.microsoft.com...
> Hi,
> We have a help desk application with MS SQL Server backend which is at
least 10 years old. This application mainly has 2 tables -
> 1. One for storing customer ID (Cust_Profile Table) and the
> 2. Other one for storing all the call details pertaining to customers.
> Apart from these two main tables, there are other tables for storing
information like configuration, history etc related to the customer.
> My requirement is - I want to change the customer ID globally across the
system. But I am not too sure as to how to proceed. Any suggestions/ideas
welcome.
> Thanks in advance,
> Harish
We have a help desk application with MS SQL Server backend which is at least 10 years old. This application mainly has 2 tables -
1. One for storing customer ID (Cust_Profile Table) and th
2. Other one for storing all the call details pertaining to customers.
Apart from these two main tables, there are other tables for storing information like configuration, history etc related to the customer
My requirement is - I want to change the customer ID globally across the system. But I am not too sure as to how to proceed. Any suggestions/ideas welcome
Thanks in advance
HarishHarish,
Review the following psuedocode use the following as guideline only...do not
do this directly on the production system and please test it on the staging
or dev env.
-- NO IDENTITY PROPERTY
Pause access to the database from the Application
Drop any Foreign Keys between tables binding the Customer Key
Begin transaction
UPDATE table1 ..
Check for Errors...rollback if needed.
UPDATE table2...
Check for Errors...rollback if needed
Commit Transaction
-- YES IDENTITY PROPERTY
Check if the Customer ID is of an Identity property
Pause access to the database from the Application
If it is of Identity property you can not Update you have to write a
migration utility
You may have to Create a shadow table with same schema as Customer Profile
(Without Identity Property on ID column)
Copy Data from Base Table (Original) to Shadow Table
Update the Value (Old ID - New ID) in the Shadow Table
Drop any Foreign Keys between tables binding the Customer Key
Begin transaction
DELETE Base Table (Original) -- Use Delete instead of Truncate for
Rollback purposes
Check for Errors...rollback if needed.
SET IDENTITY_INSERT Base Table ON
INSERT Base Table (Collist) SELECT Collist From Shadow Table
SET IDENTITY_INSERT Base Table OFF
UPDATE table2...
Check for Errors...rollback if needed
Commit Transaction
Resume Access to the database from the Application
--
HTH
Satish Balusa
"Harish Mohanbabu" <anonymous@.discussions.microsoft.com> wrote in message
news:248AB598-83B4-4611-92E3-BE336DA65170@.microsoft.com...
> Hi,
> We have a help desk application with MS SQL Server backend which is at
least 10 years old. This application mainly has 2 tables -
> 1. One for storing customer ID (Cust_Profile Table) and the
> 2. Other one for storing all the call details pertaining to customers.
> Apart from these two main tables, there are other tables for storing
information like configuration, history etc related to the customer.
> My requirement is - I want to change the customer ID globally across the
system. But I am not too sure as to how to proceed. Any suggestions/ideas
welcome.
> Thanks in advance,
> Harish
Thursday, February 16, 2012
Changing domains and SQL Server connectivity problem
Hi,
My firm will soon need to join the domain of our global firm. Currently I
have 4 SQL Servers in my old domain with replication setup. I have setup a
test server and I have found that clients within the old domain have no
access to the SQL Server in the new domain, but clients in the new domain
have access in the SQL Server of the old domain.
What do I need to do so that clients within the old domain have access to
the SQL Server in the new domain?
"Chris Themi" <ChrisThemi@.discussions.microsoft.com> wrote in message
news:F607969E-928C-4D58-BB7B-537E95BEF320@.microsoft.com...
> My firm will soon need to join the domain of our global firm. Currently I
> have 4 SQL Servers in my old domain with replication setup. I have setup a
> test server and I have found that clients within the old domain have no
> access to the SQL Server in the new domain, but clients in the new domain
> have access in the SQL Server of the old domain.
> What do I need to do so that clients within the old domain have access to
> the SQL Server in the new domain?
It sounds like you need to set up another domain trust, have your new domain
trust your old domain. Add your client accounts in the old domain into the
appropriate groups in the new domain (that have SQL Server access).
Steve
My firm will soon need to join the domain of our global firm. Currently I
have 4 SQL Servers in my old domain with replication setup. I have setup a
test server and I have found that clients within the old domain have no
access to the SQL Server in the new domain, but clients in the new domain
have access in the SQL Server of the old domain.
What do I need to do so that clients within the old domain have access to
the SQL Server in the new domain?
"Chris Themi" <ChrisThemi@.discussions.microsoft.com> wrote in message
news:F607969E-928C-4D58-BB7B-537E95BEF320@.microsoft.com...
> My firm will soon need to join the domain of our global firm. Currently I
> have 4 SQL Servers in my old domain with replication setup. I have setup a
> test server and I have found that clients within the old domain have no
> access to the SQL Server in the new domain, but clients in the new domain
> have access in the SQL Server of the old domain.
> What do I need to do so that clients within the old domain have access to
> the SQL Server in the new domain?
It sounds like you need to set up another domain trust, have your new domain
trust your old domain. Add your client accounts in the old domain into the
appropriate groups in the new domain (that have SQL Server access).
Steve
Changing domains and SQL Server connectivity problem
Hi,
My firm will soon need to join the domain of our global firm. Currently I
have 4 SQL Servers in my old domain with replication setup. I have setup a
test server and I have found that clients within the old domain have no
access to the SQL Server in the new domain, but clients in the new domain
have access in the SQL Server of the old domain.
What do I need to do so that clients within the old domain have access to
the SQL Server in the new domain?"Chris Themi" <ChrisThemi@.discussions.microsoft.com> wrote in message
news:F607969E-928C-4D58-BB7B-537E95BEF320@.microsoft.com...
> My firm will soon need to join the domain of our global firm. Currently I
> have 4 SQL Servers in my old domain with replication setup. I have setup a
> test server and I have found that clients within the old domain have no
> access to the SQL Server in the new domain, but clients in the new domain
> have access in the SQL Server of the old domain.
> What do I need to do so that clients within the old domain have access to
> the SQL Server in the new domain?
It sounds like you need to set up another domain trust, have your new domain
trust your old domain. Add your client accounts in the old domain into the
appropriate groups in the new domain (that have SQL Server access).
Steve
My firm will soon need to join the domain of our global firm. Currently I
have 4 SQL Servers in my old domain with replication setup. I have setup a
test server and I have found that clients within the old domain have no
access to the SQL Server in the new domain, but clients in the new domain
have access in the SQL Server of the old domain.
What do I need to do so that clients within the old domain have access to
the SQL Server in the new domain?"Chris Themi" <ChrisThemi@.discussions.microsoft.com> wrote in message
news:F607969E-928C-4D58-BB7B-537E95BEF320@.microsoft.com...
> My firm will soon need to join the domain of our global firm. Currently I
> have 4 SQL Servers in my old domain with replication setup. I have setup a
> test server and I have found that clients within the old domain have no
> access to the SQL Server in the new domain, but clients in the new domain
> have access in the SQL Server of the old domain.
> What do I need to do so that clients within the old domain have access to
> the SQL Server in the new domain?
It sounds like you need to set up another domain trust, have your new domain
trust your old domain. Add your client accounts in the old domain into the
appropriate groups in the new domain (that have SQL Server access).
Steve
Subscribe to:
Posts (Atom)