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.
I trying to get the moving total (juts as moving average). It always sum up the current record plus previous two records as well and grouped by EmpId.For example, attaching a image of excel calculation.
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.
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
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.
Hello Everyone and thanks for your help in advance. I am setting up a new testing and development machine. My previous machine had VS 2003 and SQL Server 2000 installed on it. The new machine is going to be VS 2005 and SQL Server 2005 Standard. I have approximately 12 databases on the old machine in SQL 2000 that I want to bring over onto the new machine and convert to 2005. What is the best way to go aobut this. I'm sure I'm not the first to do this, but I'm having trouble finding documentation on this topic. Any help would be greatly appreciated. Thanks.
I have a SQL Server 2005 Express database on my local machince called OpenAssess.mdf. The server we host with has a file extension of .mdb. How can I go about getting my database to the server? I tried changing the extension to mdb on the local machine but then it tried opening the database in MS Access and didn't work. I just need to connect to the database in my web pages. Here is my connection string and then the error which is visible at the botton of openassessment.org. *********************************************connection string************************************************* OPEN_Conn = "Provider=SQLOLEDB;Data Source=connectionToHostServer;Network Library=DBMSSOCN;Initial Catalog=OpenAssess.mdb;User ID=myuserid;Password=mypassword" *****************************************************error********************************************************* Microsoft OLE DB Provider for SQL Server error '80004005' Cannot open database requested in login 'OpenAssess.mdb'. Login fails.
ok ok, stop laughing. for real, is there any programatic way of doing this? whom ever created this database i inherited (SQL 2000) created the LDF and DATA files on the same drive and in the same folder for that matter. just trying to do a little disaster magament.
Our current sql server 7 is overloaded and I have been asked to move some data to a new box which is to be acquired. My query is as follows:
1what should be the ideal spec of a sql server to allow for windows 2000 in future. And how do I go about moving data from one to the other. I am new to sql and this is my first assignment.
I'd like to hear the "best practices" for moving databases from one server to another with minimal impact (minimum downtime) to users. The database is about 1GB, but growing at an average rate of 5MB/day.
Only 2 databases on that source server are to be moved. There are other databases on that server that shouldn't be affected as much as possible.
Any good suggestions?
I'm sorry, but I'm a complete newbie to SQL Server although I'm very familiar with Exchange/NT stuff. Got thrown this responsibility lately :(
We are going to be moving over about 29 databases from one server to another (space issues). The new database will then be renamed to the old server name. The database sizes range from 100mb to 29gig. I was planning on doing a dump/restore which will take over 3 hours to dump and 12-15 hours to restore. Our NTAdmin suggested shutting down the SQL Servers and just copying over the data/log files to the new box and then bringing up the new server. Had anyone ever tried this? What are the effects on files over 22gig? Should I also copy over the model/msdb/master database files? What other potential problems should I be aware of? My fear is that I start copying them over, run into a problem half way through and then have to revert back to the dump/restore method.
Any help would be appreciated, we are scheduled to do the move this weekend.
We are about to migrate SQL 7 databases from one SQL7 server to another SQL7 server, but we've run into an issue with transferring users/logins/passwords.
The problem is that one server is case-sensitive, and the other is not case-sensitive. This causes each server to encrypt passwords differently from the other.
Has anyone else experienced this before? Is there a workaround? Microsoft acknowledges this as an issue with SQL 7 (with case-sensitive to case-insensitive transfers), but offers no workaround.
Hi, I have to move my SQL server data from win95 to NT. When it comes to databases I would execute attach option. When it comes to backup devices I think I could simply copy the folder where backup devices are being located? IS it true?? How about moving jobs; DTS and Database Maintenance Plans??? Any Ideas?? Thanks, Andy
how can I easily move my whole SQL Server 7 installation to another different machine as the current one is going down for maintenance during one week? Thanks.
I was hoping to get some input on the best approach for the following situation: I have been tasked with moving several SQL server databases from one SQL server to another to free up the hardware on the first one for another purpose. The SQL server is version 6.5 and has service pack 5 on it.
I have installed SQL server on the server where the data is going to end up with the same code page and sort order as the current server.
For my next step I was going to create devices for the databases on the new server, then add the databases to the devices. I was going to use the "Create database for Load" statement. Then I was going to load a transaction dump from each database on the old server into the new database on the new server. Is there anything else I will need to do? Will I have to do anything with the master database or is it sufficient to do what I have stated above?
Can anyone direct me to a good technet article or white paper on this process? I did find a short page in SQL books on line which helped a bit.
I would like to know what will happen if the domain of a server is changed. Does this effect SQL 7.0? Does this effect any current jobs running on the server?
i got few questions. i need to move a databases from old server to new server. old server has 25 user databases total datafile around 300GB. heres the questions.
1. what is the fastest way to move all the data to new server? and what's the best way to do it? (DTS? MDF copy over/attach? bak copy over/restore? other theres other way?)
2. i got alot of job and user need to transfer over. i know DTS can do the user.. how about the jobs?
3. do i need to move the master and msdb over too?
4. beside all 3 questions above... do i miss anything that need to be move too?
