Moving A SQL 7.0 Replication Server To Another Sql 7.0 Server
Jun 13, 2001
I am looking for a way to move replication from an old server to a new server. The story goes like this. We have a old machine running tran replication. THis machine is crashing because of a hd going bad. I need to move this Stuff over to another server with out having to re-setup and reinitalize all the replication stuff. Basicaly i am trying to make a copy of the old sql server on the new one. ANy help would be appricated.
Currently we have a SQL 2008 transactional replication setup in which the Publisher is replicating to 6 different subscribers. We need to move the Publisher SQL instance from VM server A to VM server B, which has a different host name. The actual move is expected to take a few hours.
how to handle the replication piece correctly. Steps needed to properly shut down replication before moving the SQL instance, and then the correct way to start replication back up again.
Because the server name is changing, I am thinking that will we have to create a new publication & subscriptions ? And if so, does this mean we HAVE to apply a new snapshot?
I have 2 databases on a remote server on which Replication and Replication Monitor is enabled. Now I want to move this databases from different remove location.
How do I transfer bboth databases with replication and replication monitor enabled on it with all the user logins.
I have done a bit of searching around and cant find a clear answer to this question.
Current Setup Desktop application (c#) that connects to a SQL Server 2005 express database on the same local network as the application (currently 3 users)
It is only a very small company and has just taken on their first remote worker, but expects to take on another 6-8 over the next few months. They have asked for the database to be moved online.
The application was written in such a way that everything has been done using no stored procs, or views, it is all native SQL.
This will be my first DB hosted online and before I go ahead and do anything I just wanted to make sure what I have to do is correct, sorry if this is a very basic question, although I have been programming for a long time, I have never had the chance to do any online databases before.
Will this work. 1.Find a SQL Server 2005 Hosting company. 2.Move the database to the server. 3.Setup the users permissions. 3.Alter the connection string in the application to point to the new location.
So the only thing that would change would be a new connection string in the application preferences?
Or am I living in a dream world, because nothing is ever that simple.
One thing I am worried about is the security/visiblity of the database and data as it travels from the server to the client and back.
My searches have come up blank, so I'm hoping someone else can point me in the right direction. I'm done some development in SQL Server Express, working on tables and procedures. I've now got to move those tables/procedures into SQL Server and I don't know of an easy way to do this. Are there any tools I can take advantage of that would allow me to get all these objects moved? The only way I can see to do it is to move objects over one-by-one. This would be really time-consuming, and I'd like to avoid it if possible. I'm positive I'm not the first one to try this, but what should I be searching for? Are there tools/procedures I should be looking for? Appreciate any help I can get. Thanks.
We have both a production SQL 7 server, QA, and Development. From time to time, I want to move just the data from the production server to the other 2 servers without modifing the objects that may have been changed such as stored procedures and rights. Is there a way using the SQL tools provided that we can just move the data. Becuase also what happens is that the rights to the objects change which means my developers no longer have access to the tables for selects in QA since the changes where overwritten by production where they do not have the rights.
I have two databases on two different servers (an old hosting solution and a new). I need to get all the data from one server to the other but I have no clue as how to do it with MS SQL Server Management Studio Express.
I can easily make the create table scripts that will allow me to create the tables on the new server but what about all the data. I wondered if there is some way to export and import data from one server to another?
With the old SQL Enterprise Manager I was able to import or export as I saw fit but I can't seem to find anything like this with the express manager.
Anyone has any advise as I would like to avoid coding somekind of export program myself,
We have a new server (SRV63) and I followed the instructions at http://msdn2.microsoft.com/en-us/library/ms156421.aspx to move the report server database from our old server (SRV38). Everything appeared OK, however, when I went to initialize the instance in the Reporting Services Configuration tool, it shows an initialized instance (checkbox is checked) for SRV38 and and uninitialized instance for SRV63 (checkbox is not checked). Please note that I am not trying to create a scale-out deployment. I tried to initialize SRV63 but received the error below.
--------------------
ReportServicesConfigUI.WMIProvider.WMIProviderException: The report server installation is not initialized. (rsReportServerNotActivated) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.InitializeReportServer(String installationId)
------------------
This is the only thing stopping me from shutting down SRV38 and bringing SRV63 into production. Can someone assist me with this issue?
Hi, i was after some advice on moving a SQL Server 2000 database from one server to another.
Usually i would do this by backing up the database on the original server the copying it accross the LAN to the new server and restoring it there. This database is 10Gb in size and copying it accross the LAN will take some time and i would like to minimise downtime if possible. The database is at a customer site where i am not responsible for the network or Hardware.
I built a web application using my VS2005 installation, which includes SQL Server Express. All works nicely. However, when I tried to move this application to a system with SQL Server Developer, I cannot get it to work at all - data access receives several errors, with the most common being this one: Cannot open database "xyz.mdf" requested by the login. The login failed. Login failed for user 'MACHINEASPNET'. Here is my connection string (with specific names changed, obviously): Data source=MACHINE;Initial Catalog=xyz.mdf;Integrated Security=SSPI;User=Me;Password=MyPassword I have given users MACHINEASPNET and MACHINEMe all possible permissions (that I know) within SQL Server. I have spent days on this, with no solution - help would be most appreciated.
I missed the days of 6.5 when I can take a database from one server create a device for LOAD on another sever and use the LOAD database command to put that database on another server that has MS SQL SERVER on it..
So what is the trick with 7.0 if DTS is out of the question??
I have a piece of code that has happily run daily for at least 4 years. I have moved it to a machine that is meant to have an identical set-up, and it fails. I need to work out why it fails, but I am stuck. The code works as follows:
CREATE storedProc1 (Parameter1, etc) DECLARE @TransactionName nvarchar(127), @TransactionActive bit -- Plus Other Variables... BEGIN BEGIN TRY
SET @TransactionName= 'TransactionName1' SET @TransactionActive = 'True' BEGIN TRANSACTION @TransactionName WITH MARK
[Code] .....
When I EXECute StoredProc1, it fails with the Error Message "Cannot roll back . No transaction or savepoint of that name was found." I think that message comes from a ROLLBACK TRANSACTION statement in the CATCH of StoredProc2. I have tried commenting out that ROLLBACK statement, which changes the error message to: "Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 2."
I am using reporting services 2000 with SQL server 2000. The report server is on my machine and report server database is on another sql server. I need to move report server database from server1 to server2.I have tried the method which i found on net i.e 1-Stop the reporting services 2-detach the report server database from server1 and attach it to server2 3-reconfigure reporting services using RSconfig wherein i specified the new server name , database name and authentication. 4-Start the reporting services 5-Restart IIS
After following all these steps when i browse the report server i get the following error :
"The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online Help "
I am actually the MOM administrator and only know enough SQL 2005 to keep mom working....sometimes I noticed on my dev mom box that SQL server agent has a lot of jobs configured to run against the mom onepoint database. The production box does not have these jobs. What would be the simplest way to export these jobs so that i can import them on the production box. Any help would be appreciated.
My existing SQL server is an old box that can no longer cope with the load. I need to replace it with a brand new box.
I am looking for a comprehensive set of steps that I could follow to ensure that the transition to the new server goes well.
I'm looking to transfer all my user databases but I'm not so sure whether I have to backup and restore my system databases to the new server as well.
I want to name the new server the same as the old server since I will be taking the old server out of production but I'm not sure whether I should rename the server AFTER I move over all the database and how that would affect SQL. Or should I first rename the old server, remove it out of the domain, then name my new server with the same name as my old server, and then proceed with the SQL installation and the moving of the databases.
Also, I do have a maintenance plan, DTS packages and some jobs set up on my old server that I would also like to move to the new server.
Is there a web page that explains all the steps in granular detail ?
I keep reading in various places of the replication documentation that records can be _moved_ as opposed to just being copied. How can I do this? I can't seem to find anywhere during setting up the publication, articles or subscription an option that allows me to do that!
I'm very new to using SQL Server and have a very basic question that I was hoping someone could help answer or point me in the right direction.
I’ve been searching for the information and have been unable to find what I’m looking for. I might be using the wrong keywords.
This is what I’m trying to find. I have found some information on building a database in Access and porting it over to SQL Server. The information that I've found discusses on a simple level how to use Enterprise Manager to port over using the following steps: Enterprise Manager: 1)Database level >> Action Menu >> New Database … setup a name 2)Highlight new database name 3)Tools Menu >> Data Transformation Services >> Import Data
Data Source = Microsoft Access
Okay, so that is pretty straightforward. If I created the web page using the Access DB and I am using an OLE-DB connection string then once I port over to SQL Server all I should need to change is the connection string to a SQL Server connection string. Is that correct? Anyone know where I can find some information about this process and specifically how to upload the new SQL Server DB to the remote web server? To upload an Access DB, I just FTP the DB to the site directory. Pretty easy. If I understand right, you don’t do that with a SQL Server DB, but rather replicate the DB to the remote server. I would like to understand how to move the SQL Server DB to a remote web server. I’m trying to learn the steps and how it is done? Thanks in advance for any help. -D-
I have a c# application which connects to my Sql Server database which is stored on my PC. I'd now like to place the sql server on a real server. What general steps are involved in doing so?
Hi I'm very new to this but what I'm looking to do should'nt be too difficult although I've tried to no avail.
I'm looking to deploy a web site that uses SQL2000 to another server. Im trying to find out how to move the database to that server. Ideally I would like to be able to save it to CD for safety but its not like old access where you save the mdb file. I need to save the whole 'DTS' package, is that what its called? stored procedures, triggers the lot.
At my work, we have a SQL Server 2K DB on a server. This server is being replaced and the DB needs to be copied from the old server to the new server and I've been asked to perform this task. What I was planning on doing was:
1. Making a copy of the database on the current server
2. Taking the .BAK file created and coping it to the new server via a mapped drive
3. Restoring the database from the .BAK file on the new server
The only concern is moving the .BAK file across the network due to size.
Is this the best method to do this or is there a more preferred way? By doing this, what potential issues could be encountered?
Our SQL server, Report Server and IIS server are all on 1 physical server but that's going to change. We're moving the IIS/web server to a new box but the database server & report server will be on the old box.
Are there available documentation on how to move the Report Server service and IIS configuration of the Report Server?
I am hoping somebody can tell me in detail what is the quickest and fastest way to move SQL 6.5 to a new server. The server it is on is out of resources and space, and I have a new server to move everything over to. I assume I can just install SQL 6.5, copy the DATA database and MSSQL directories over, and rename the new server to the original name and take the old server offline?
Please give me as much detailed directions if you can.
We are moving our production SQL server(EE) box to new box. Also, we need to change the server name with new name. Currently, we have lots of DTS, Transactional Replication and many jobs running.
What are the precautions / DOs and DONTs to make successful transfer to the new server? Apart from restoring msdb on the new server, is there anything we need to concentrate?
Hi Everbody, I've got a client that set up their own SQL server. It is currently installed on NT4 on the system volume. It needs to be moved to a directory. I was wondering if anybody has ever done anything like this or can offer some good advice on the best place to start.
I'm currently working on a project, with development at my location and production at another. My question is what is the best way to copy database changes, ie adding/removing fields, without having to copy over the existing data. I have been just noting what fields I add and remove, and going to the production server and doing it by hand, but this obviously isnt the fastest way to do it. Essentially when I add a new module to the system on production, I have to manipulate existing database tables. I want to copy the schema of those tables to production, but I dont want to lose any existing data on production. Thanks in advance.
I'm doing a remote deployemnt of an asp.net app using Sql Express from my local dev machine to the ISP. Moving the database to the new machine is one thing, but how do you move the users? Just adding the same username and pwds as logins is still going to throw you out of the db isn't it? I've run the Database Publishing Wizard on the target machine, but the t-sql falls over whenever it encounters an unknown user.
Hi all,I have been given the task of moving an sql database from one serverto another. These servers are not on the same network. I know I candetach the database, copy it to a new location, then FTP it to the newserver and re-attach it.My question is, is this the best way to do this? Or is there anotherway? I have access to both servers through Enterprise Manager.TIA
DBCC OPENTRAN shows "REPLICATION" on a server that is not configured for replication. The transaction log is almost as large as the database (40GB) with a Simple recovery model. I would like to find out how the log can be truncated in such a situation.
