Soon, I will be migrating SQL cluster volumes from our old SAN to the new one. I have an idea of how to do it, but I just wanted some feedback. Yes, I know the best way would be to set up a new cluster using the new SAN and migrate the DB, but unfortunately I don't have that luxury. Here's my plan...
Add new storage to cluster, ensuring the drives are active cluster resources and dependencies match old resources
Back up DB
Shut down SQL Server
Copy all files & folders from old storage to new storage
Reassign drive letters to make new storage match old configuration
Start SQL Server
In theory, I think this will be fine because as long as SQL sees the correct drive letters, it should function properly. Just concerned about the quorum portion of the cluster.
We have our production SQL 2005 server (64 bit Standard Ed.) attached to an iSCSI Equalogic SAN. We have set up 2 new servers an installed the cluster service. My question is: can I install SQL 2005 in this cluster environment an latter on disconnect the data and log volumes from the production server, attach those volumes to the cluster an reattach the DBs? the reason we need to do it like that is that we don't have enough spare space in the SAN to initially create these 2 volumes in the cluster.
Any ideas/suggestions would be greatly appreciated.
We have our production SQL 2005 server (64 bit Standard Ed.) attached to an iSCSI Equalogic SAN. We have set up 2 new servers and installed the cluster service. My question is: can I install SQL 2005 in this new cluster environment an latter on disconnect the data and log volumes from the production server, attach those volumes to the cluster an reattach the DBs? the reason we need to do it like that is that we don't have enough spare space in the SAN to initially create these 2 volumes in the cluster.
Any ideas/suggestions would be greatly appreciated.
I'm looking at using Cluster Shared Volumes on a new Windows Server 2012/SQL Server 2014 cluster. Each instance is going to be configured to use cluster shared volumes. Is there any reason why Availability Groups couldn't be used in conjunction with Cluster Shared Volumes.
I have two Windows 2000 servers (Advance Edition) to form a Windows Cluster. I also install MS SQL 2000 Enterprise Edition on the cluster to form a MS SQL cluster. Now, I want to upgrade the hardware and OS (but keep on using SQL 2000), so I install Windows 2003 server Enterprise Edition on two new servers to form a new Windows Cluster. I am planing to install MS SQL 2000 Enterprise Edition on the new cluster, so the old SQL cluster and new SQL cluster are side by side. I would like to know how to setup a new SQL cluster (I know it has problem to rename SQL Cluster name, so how to fix this problem)? And how to transfer everything (such as system databases, users database, sql user account, password and maintenance plan jobs etc) from old SQL cluster to new SQL cluster? And how to switch over from old SQL cluster to new SQL cluster?
I have a Windows 2008 R2 Always on Cluster with 3 nodes (two in the primary site and one in the DR site).
Primary Site: -Primary Site Server1 -Primary Site Server2
DR Site 1 (to be decommed): -DR Site Server1
Our company is planning on decommissioning the DR site. But before we do this, we want to add a 4th site to the cluster. Migrate the data...and then decommission the original DR Site.
Is it possible to have this configuration:
Primary Site: -Primary Site Server1 -Primary Site Server2
DR Site 1 (to be decommed): -DR Site Server1
DR Site 2 (NEW DR Site): -DR Site Server1
IF this is possible, do I simply add the new DR site to the existing cluster (same steps as adding the first DR node to the cluster when the cluster was originally configured? or are there special steps?
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2 Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid. Msg 3156, Level 16, State 50, Line 2 File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file. Msg 3119, Level 16, State 1, Line 2 Problems were identified while planning for the RESTORE statement. Previous messages provide details. Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
Dear all,I've been using ASP.NET with SQL 2005 express for several months and everything has been fine. Now a customer asks me to install my application on an already existant instance of SQL Server standard edition.I was not able to use nor my application, neither a HelloWorld example.I created a simple Default.aspx that uses a simple database with a single table "Person" via a standard gridview. When I try to open the page I receive an error wich informs me that NT Network service is not able to access database.I've been searching on google for hours and I've tryed unsuccessfully several different way.Can anyone suggest me a scientific procedure to migrate an ASP .net web site from sql 2005 express to sql 2005 standard ?Thank you very Much Fabrizio
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)
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 ?
i'm migrating my dbase from SQL 2000 to SQL 2005..i've restore the dbase to SQL 2005..but what about the SQL job?..do i need to create them back in SQL 2005?..how to do that?..1 more question..how to migrate DTS from SQL 2000 to SQL 2005?..i've ActiveX script in my DTS...really need help from all of u.. thanks
I have right clicked on my DTS package and selected Migrate... Iassumed this is a good idea for future upgradeability (?) The processworked without error but I have no idea where the resulting migratedpackage can be found. The DTS package itself (apparently) remainsunchanged.If your answer is that an SSIS package has been created, please tell meexactly where I can find it.I've looked at SQL Server Business Intelligence Studio (where do theyget these names from?) and have not been able to find SSIS (or anythingelse useful, actually).
I am planning to migrate sql server 2000 databases to sql server 2005(sql server 2005 in a separate box) .I have few questions regarding the migration:
1. Do I have to run Upgrade wizard on 2000 even though I am not upgrading my sql server?
2.Which other databases do I need to move in addition to the user databases. (i.e. do i have to move any system databases?).
3. What do I need to do to move sql server logins with the password to the new machine?
We have a need to migrate some DB2 servers to SQL Server 2005. Unfortunately, the SSMA for DB2 is still not out. Can anyone please tell me on what are the things to consider with regards to DB2 to SQL 2005 migration? It would help if you can point me to some whitepapers or tools ir maybe even some samples or instructions regarding the migration. Thanks!
Newbie to SQL CE 2005. We have an SDF database file with a whole bunch of tables and data. We have to port the SDF to SQL Server 2005 database. The SQL Server DB is empty has no knowledge of the SDF tables/schema. How do I go about to get the SDF schema/tables migrated to SQL Server DB and then also transfer the data.
I've got the responsibility over a small SQL server with 8 Database and approx. 100GByte data online. Most database are used and need to be available 24*7*366. Also a number of local data transformation packages are defined and used on a regular basis. Furthermore a number of third party applications rely on this database.
My question if it is worth the effort to migrate this to 2005? I know there are all kinds of nice migration wizards but do they really work? What if one of the 3rd party apps don't like 2005?
Love to hear both good and bad experiences migrating -> 2005 .
Hi Everybody, does anyone know how I can migrate SQL 2000 data to SQL 2005 database? I'm trying to create an application that will connect to SQL 2000 database using VS2003 and transfer data to SQL2005 database but it doesn't seem to work. Any suggestion is greatly appriciated. devmetz.
Hello. I have the following problem. I have a database in mysql and i want to migrate in ms sql server 2005. How can i do that? I have downloaded and installed MySQL Connector/ODBC .
In client having existing system is MS Access. So I want to migration MS Access system to SQL server 2005.
Let suppose there MS Access one table having 10 fields.
That table data i need migrate in system (sql server 2005), but the field name are different & sql server few fields are extra suppose 15 fields or vise versa.
So can any one help me out, how to migrate the MS access to sql server system?
Please give me if any one the script or step do this.
Dear All, at present all our servers are running with sql server 2000. we are planned to upgrade to sql server 2005 standard edition. what is the approach i need to follow? can i directly go for installation of sql server 2005, and then use copy database wizard? this is a production environment, and we even not give 5 min of downtime. please help me in this regard
Arnav Even you learn 1%, Learn it with 100% confidence.
I was wondering if anyone might be able to help me here. I'm very new to SQL server and has been asked to convert microsoft access database .MDB to SQL server. In another word, i'd like to migrate access to SQL Server. It's not a huge database. The size of it is roughly 6MB. The reason for migration is simply because our clients don't have microsoft office running on their system. They use SQL Server. This's a new challenge to me as i'm more comfortable with using Access now.
I have been searching and studying it thru the online tutorial about what it's and what it does. I have also downloaded and installed the SQL Server 2005 Express edition because it has GUI Interface and it does have the ability to produce reports like Access does. Now my question is how do i start because when i created the database i didn't think of any client/server application? so if i want to run the Access, i just double click it and start using it. how do i migrate it to SQL Server for a testing sake?
Initially, the articles I read suggested that doing an "in place" upgrade is the simplest path, with the drawback that if something goes wrong, I'll have to re-install 2000. And that migrating is more difficult since I'll have to recreate all the logins , security, replication ....
Then I saw a series of posts saying migration is the best ... backup & restore (or detach, reattach) the DBs to a new instance of SQL 2005. What about the systems DBs, such as MSDB and the DTS packages ?? Also, If I migrate to a new instance of SQL, how will I re-establish the connections from other servers ? They are replicating or DTS-ing to ServerA, but now SQL2005 is on ServerASQL2005 (Same server, different instance.
In the scale of things, we have fairly simple environments, although our Production database is almost 300 Gig.
If I install a new instance of SQL 2005 on my SQL 2000 server, and migrate everything from 2000 to 2005, I now have 2 instances: ServerA and ServerASQL2005. All my other servers are referencing the original instance name of ServerA. How do I resolve that problem so that communication between the other servers will still work ??
I am trying to convert an Access database to SQL Server 2005. I have gotten the tables imported into SS2005 but how can I get all my queries imported in? Or is it not possible? Thanks.
I am trying to migrate from MySQL 4.1 to MS SQL Express 2005 1. do i need to create an empty db under Express 2. can this be done from within Express by pulling from MySQL into Express or do I need to work from command lines 3. what would be the cleanest way to approach this
I have a MySQL dump and did look at the result from within Express, but it was not an import, I would like to find a way to import if possible that data. Table by table would be fine.
I need to move few folders from our DEV SSRS 2005 environment to another server. Folders will be moved to new parent folders. Is there any tool that I can use fot this purpose? I used RSScripter from SQLdbatips.com. Although the tool works great but it can't script multiple folder reports. I have to script one by one and it is a big problem.
Hi all, in my current environment, I have a single server SQL 2000 setup that's being replaced. I'm in the process of installing a new SQL 2005 cluster with the thought of taking advantage of 2005 mirroring and clustering, but have a few questions.
1. My thinking is that I can migrate my 2000 databases to 2005, but leave the databases in 8.0 (2000) mode. Are there any issues with this? I know they won't take advantage of the 2005 performance boost
2. Some of the apps don't support 2005 yet so I need to leave them in 2000 mode until they do. Is SQL 2005 fully backwards compatible with a SQL 2000 database?
3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode?
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
Hello Everyone, I have a SQL 6.5 database that is about to grow beyond the size of its current volume. I have 3 volumes of 20GB each, 2 of which aren't being used. What do I need to do to ensure that I can expand the device across multiple volumes?
