Typically small companies or small projects which use SQL Server / IIS / File Shares / .NET solutions deploy these apps on a single server many times using just one IP address and the NETBIOS name of the server for both IIS / SQL. Many times there is no use of DNS and even when there is everything is mapped to the server/netbios name.
As environments grow and there is a requirement to create an n-tier server setup possible due to new security requirements, extention of the intranet to the internet, or to scale out an application you may need to split IIS / SQL into different servers. The question then becomes how do you do this without affecting existing services and you want to have minimal down time without having to change all connection information within deployed apps until you have time to review the changes carefully.
First let me begin with how to move IIS away from SQL and then I'll discuss the reverse.
The best way I've found to control the move of IIS sites is by assigning each site it's own ip address / dns host record and adding the ip address to the server network card and IIS site. Now each time you need to move 1 or more sites you can simply replicate the site to another server and change the dns ip pointer to the new pointer. If you have existing sites which were not setup in this fashion you can also move them to a new server, create a site with name of the old netbios machine name, and redirect the default web site to this new site.
Now you successfully isolated SQL Server from IIS/.NET apps you can take your time and correct the apps to use the new dns entry in connection strings instead of using the netbios name of the machine. Once you have corrected the app you can turn off any redirection.
Now let's assume you have the opposite scenario where you started off with a small server and your SQL database server now requires a server with more memory / more processors and you want to keep IIS / FileShares were they are and want to move SQL Databases to a new server. As I mentioned above a good way to do this is by setting up each database with it's own dns entry a very effective redirection mechanism. However you are may be inheriting a system which does not employ this mechanism and again uses the default netbios machine name, furthermore this may get more complicated because there may be multiple instances of SQL Server running on different port numbers.
You could use SQL Aliases on the clients to redirect connections to the newly created instances but this would require changing every pc and IIS server and it would be cumbursome to manage. It would have been nice if microsoft provided a way to redirect from the server just like IIS does but they did not. A product which will help you setup a server based redirection of ports 1433/1434 and/or any other ports is called porttunnel by steelbytes.com. Once you've installed the redirecting service on the server all new requests on port the ports selected will be redirected to the new server which I recommend be redirected to their own dns entries and this will buy the applications developer time to change their applications.
I would like to hear any comments or experiences with this that any of you may have had or if anyone has found a better solution. I'm in no way associated with the product / or company mentioned above just found it to be a good solution.
If I use the DTSMigrationWizard.exe, to migrate my existing DTS packages from SQL Server 2000 to SQL Server 2005 will it delete the DTS packages on the 2000 server?
On this one server I have 65 DTS packages and I want to migrate them all at once if possible but still keep the DTS packages on the 2000 server.
Is there any utility to migrate the existing indexes on default filegroup to a new user defined file group? The only way that I know is to delete the index and recreate with new filegroup.
How about for table? Is there any utility for migrating the existing tables to a different filegroup? The only way that I know is to create a clustered index on the new filegroup which will move the table to the new filegroup. If a clustered index exists then drop the clustered index and recreate it with the new filegroup
I am looking for an existing utility which would do the above?
I want to move an existing table from another. Example B.mdf dbo.xx to C.mdf dbo.xx B.mdf dbo.xx has records - I created a script and install the script for C.mdf dbo.xx C.mdf dbo.xx is empty - All I need now is to populate the records from B.mdf dbo.xx to the empty C.mdf dbo.xx I was telling I could do a cut and paste to copy the dbo.xx Thank you in advance. ~ Peaches ~
How to move existing table(include its constraint and index) into a different filegroup using tsql in Sql Server 2000. We have 1000+ tables in our system and we are planning to move around 500 tables to a new file group, which is available on another SAN drive.
I got 2 questions to ask: 1. I choose Windows and SQL authentication during setup. Will this have any impact on my connection string in Dot net? 2. If I want to host my db on my computer, what other protocols do I need to enable? Currently I got shared memory on.
We implemented SSIS packages which read data from an operational system at our customers site. This system is one of the primairy systems used in the organisation and is vital to the organisation. In what situation ever the operational system shouldn't be affected in its operation by the SSIS packages. Unfortunately the following problems occur:
1. Sometimes a SSIS packages waits infinetly. We tried the 'with (nolock)' and 'with (readuncommitted)'' statement in the source query but without succes. The package just keeps on waiting and the SSIS proces won't finish. It seems the package is just sleeping without resuming.
2. On a specific day the operational system got disturbed and end-users couldn't proceed working because the application hang. According to the system administrators our SSIS package caused a lock on a table in the operational system. Which we find is a kind of strange because we use a simple 'select ... from with (nolock)' query.
We prefer not reading directly from the operational system so we adviced to bring in a mirror read-only database where the SSIS packages can read from. Unfortunately the mirror system will not be up and running within three months from now.
Anybody can advise me what to do because I am running out of options.
I went to look at the connection string previously entered for a dataset created in a new report, and am not seeing anything intuitive for bringing up the associated datasource dialog box that was used to enter name, type and connection string. I'm also noticing nothing intuitive for deleting an existing dataset. How do you do these two very simple things in an existing project? I dont see the dataset in solution explorer, I see it only in the text box on the data tab and in a limited kind of way on the dataset view where the columns show and maint is allowed mostly on the columns only. I tried hilighting the dataset here and hitting the delete key to no avail.
I would like to restore database using RESTORE DATABASE ... REPLACE command. If database exists already and has any open connections this command will fail. I would like to close all existing connections to specific database before running RESTORE DATABASE ... REPLACE command. I can do closing from Management Studio using checkbox "Close Existing Connection" when deleting database. Actually I need to do the same but from script.
I have DNN installed on one server and now i need to move whole site to another server. I have moved the FTP files, and changed the conn string in config. How can i move the database? I dont have the database publishing webservice installed so i will need some other way. Does anyone know of a simple way to migrate from one sql server to another?
i have an application that runs on sql server, that is all working fine on the development environment, and nearly ready for deployment in production.
a large part of this application is based on complex dts packages.
is there a straightforward way to migrate all of these packages AND change all the connections to point to the live box rather than the development box, without painstakingly changing all the connection objects (in around 100 packages!!)?
I'll be doing a migration of all my exisitng SQL7 databases to SQL2000. We are planning to buy new servers for the upgrade. What is the best way to move the entire database?
A) Use copy DB wizard? B) Create own DTS package to move everything? C) Script the entire DB and run it on the new server and then move the data? D) Do a backup and restore it onto the new server?
What are the best options? Are there anything that i should be aware of?
Hi I need to move some DTS packages from SQL7 to SQL2K What is the best way to do this? I realise the problem is because a SQL7 master database cannot be restored to a SQL2K master database Is there some way these can be scripted out of 7 and the script run in 2K
I am exploring the feasibility of migrating from DB2 (v7) to MSSQL server 2005. My current applications are using UDB, but the DBA wants to change to MSSQL. I believe the impact is huge. For example, how to create schema in MSSQL, how to migrate the data...
Anyone had the experience before? Could kindly suggest some reference for such a migration? Thanks!
I'm migrating from DB2 to SQL 2005 workstation. I have tried all kinds and type of migration tools. The best way so far is using the import wizard to created an SSIS package. One little problem so far. I cannot get past the "Text was truncated or one or more characters had no match in the target code page" error. I get quite a few rows before it stops. I've looked for any "invalid characters" in the source data. The row it seems to stop on doesn't make sense. Is there a way to modify the SISS package file to not stop on truncation errors? Or, can I determine the proper code page to use? I've adjusted column data types and lengths but can't find a combination that works.
- Copying to [tsi].[TSI].[CNOTES1] (Error) Messages Error 0xc020901c: Data Flow Task: There was an error with output column "CNLINE" (20) on output "OLE DB Source Output" (11). The column status returned was: "Text was truncated or one or more characters had no match in the target code page.". (SQL Server Import and Export Wizard)
Error 0xc020902a: Data Flow Task: The "output column "CNLINE" (20)" failed because truncation occurred, and the truncation row disposition on "output column "CNLINE" (20)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component. (SQL Server Import and Export Wizard)
Error 0xc0047038: Data Flow Task: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Source - CNOTES1" (1) returned error code 0xC020902A. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. (SQL Server Import and Export Wizard)
Error 0xc0047021: Data Flow Task: SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited. (SQL Server Import and Export Wizard)
Error 0xc0047039: Data Flow Task: SSIS Error Code DTS_E_THREADCANCELLED. Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. There may be error messages posted before this with more information on why the thread was cancelled. (SQL Server Import and Export Wizard)
Error 0xc0047021: Data Flow Task: SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC0047039. There may be error messages posted before this with more information on why the thread has exited. (SQL Server Import and Export Wizard)
Hy all, my english is not so good so i try to explain... I have this environment
2 Servers, one is sql 2000 an the other is sql 2005 (cluster) My server 2000 is very old and we dont want to upgrade(hardaware) them and it have a lot of DTS´s packages (actually only DTS packages). I need to rewrite every package to SSIS, but my priority is take off this server transfering de DTS packages to SQL2005 and use in legacy mode.
How do i do this ?..In this moment i just want to transfer the packages to 2005 and use in legacy mode..there´s a diference between migrate and use in legacy mode ?
Hi, I was able to create an MSSQL database with the ASPNETDB.MDF file. But how do I get the Login Control to point to the MSSQL rather than the App_DataASPNETDB.MDF file?
Hello all, I have an application in which the database is currently in MySQL. The app is being re-written(in .net 3.5) and I would like to move the data to SQL Server 2005. What is the best may to get the data from MySQL to SQL Server. Any good tools out there? Idealy, I would be able to manipulate the data during the move, as I have plans for some schema changes, but I suppose I could always make them after migrating. Please suggest any tools or methods, with your thoughts. I will evaluate any suggested tools. Also, SSIS is available for me, is that the best way?
I am trying to migrate the default repository that is created when you install OLAP on a server. I have done this on my local server and several other servers without a problem. When I goes through the steps to migrate the repository it says it completes sucessfully but leave the repository pointing at the mdb file. On the other servers it has updated the pointer to the SQL database. I am running SQL2000 SP2, AS SP2 and W2000. The only difference I can find it that the server where it doesn't work also has two named instances on it. Any help would be appreciated.
I have 100+ SQL servers registered in SQL EM. Is there a way to migrate these servers to a new PC (registry keys?) or do I have to individually register each one in the new PC? Thanks in advance for any response.
Here is the scenario: We have an existing production non clustered SQL 2000 server instance that we need to migrate to a new clustered SQL 2000 server instance. We need to accomplish this without affecting the FQDN that applications use to call this server. I found this article on a solution to rename the server after an xcopy of the entire db structure. Here is the link http://vyaskn.tripod.com/moving_sql_server.htm. The other issue that we are trying to resolve is the time it takes for the snapshots of replication to run (in our case almost a full day). That is why this approach looked like it may be a good solution for us.
Here is the question: Is it possible to move our existing database to a new clustered environment without having to change the FQDN that other applications use to access this database and without having to reinitialize replication?
Is there a tool available (or planned) to migrate SQL Server 2000 database to SQL Server 2005 ? I came across this (http://www.timespring.net/TS_TD_SQL05offer.htm?track=NL-464&ad=524331) but are there any other tools ?
Has Microsoft planned anything of its own for this ?
