I am moving all of our SSIS packages from a stand alone server to a clustered environment. The old server ran Enterprise Edition, the new server runs Enterprise Edition 64 bit.
One package on the new server is giving me the error messaage DTS_PRODUCTLEVELTOLOW when run from a job. The package is stored in MSDB
I went back to the server and ran the following with the following results.
- Connected to SSIS from Management Studio on my desktop and ran the package and got the same error message.
- Did the same as above but was connected to the server through Remote Desktop and it ran fine
- Ran the job, which just runs the package and it ran fine
Hello all: looking for some general advice on proper approach. looking to move databases off of a clustered instance to a new (non-clustered) server. Got several issues i'd like some advice on.
1. This is an OLTP instance that's been around for a while & it's pretty well encrusted with apps & processes that attach to it. Therefore it would be a very good thing if we didn't need to change the connection information in several hundred places after the move. I've tested one approach to this that seems to work: moved the instance to a server which has the same name as the cluster resource associated with the clustered instance and an instance that has the same name as the clustered instance. For example: cluster install is aiproddbproduction, moved it to a box called aiproddb with a named instance called "production". There's a bunch of tedious network stuff that has to be done to make this work (binding an IP address to the MAC address of the new box and some murky DHCP reservation fiddling), but after the network crew got done cursing me it did finally work. Does this seem like a reasonable approach?
2. What's the best way to transfer security info to the new instance? I used the transfer Logins DTS widget but had some problems with it not being able to find some groups in AD.
3. what's the best way to transfer DTS packages?
4. is it necessary for the new instance to be at the same patch level as the old instance? the old clustered instance is still at SP3 and i threw the latest SP4 on the new location. good/bad/indifferent?
5. i was planning on taking a full backup & restoring it to the new machine. Is there a better way? Is the wizard for copying databases a good thing?
Those are these issues i'm aware of and have given some thought to. There are probably things about this i haven't considered and would appreciate some word on.
Our production server is currently running SQL 2005 on a stand alone machine. SQL Server is installed as a default instance.
Can we upgrade to a cluster without having to change the instance name i.e currently applications connect to this server with hostname of the server i.e SERVERA, can we install a cluster such that sql server can still be called SERVERA.
I have a SQL 2008 R2 2 node cluster. For DR testing, I need to restore an instance on a new server (completely isolated). The existing instance runs on what I would call an alias. The actual cluster host name is SQLPROD (cluster nodes are SQL01 and SQL02). The instance runs on server SQLPROD-APPLE. The instance is called APPLE. In production, I use SQL Management Studio and I connect to SQLPROD-APPLEAPPLE.
I've setup a new VM to run SQL. Not a cluster. Host name is SQLREC. The new Vm has all the IP addresses that were on the cluster and the DNS for all the aliases are correct. I've installed instance APPLE. I created an alias called SQLPROD-APPLE. When I try to open SQL Management Studio and connect, I can't connect to SQLPROD-APPLEAPPLE. I can connect to localhostAPPLE, SQLRECAPPLE, 192.168.168.50APPLE.
When I attempt to connect to the alias I get error 18452. Pinging the alias resolves correctly. I haven't gotten to the database restore yet, so that's not a concern. I'm just trying to validate the connection first with the correct server and instance names.
Can anyone let me know how to migrate the sql server jobs to new cluster server from a stand alone box? Is it easy to just restore the msdb on the new server?
I have a 2-node cluster environment & I am planning to replace it with new hardware. Currently I am using MSA1000 Disk arrays. Now I would like to move my storage to SAN.
What are the necessary pre-requisite and actions to do this. Any particular thing, I must take care in planning.
Can SQL Server 7.0 be installed on a laptop as a stand-alone run-time application (using a VB front-end application)? Is it necessary to use MS Access as a gateway, or can SQL Server 7.0 really stand on its own?
Hello everybody . I have 40 GB db running mostly transaction processing. I set up 1. back full backup 2 times a day (takes 30 -40 min) 2. log backup every 15 min 3. custom log shipping 4. We don't won't use Cluster.
Once in while becouse of nethwork, or other problem log shipping fails, so I have to restart log shipping all over starting from restore in stand by mode last full back of my db.IT takes 2-3 hrs just to do this restore !!!
1. So I am asking advice is any way I do restore in less time ? 2. Should diffrential backup be taken ? 3. We will not use Custer
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?
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?
HI!I have a little problem:I have change the administrator password (Windows 2003 Server) which MSSQL 2000 use to login.And now the SQL server can't stand up.What should I do?thx!gicio--Posted via http://dbforums.com
I just start my job as sql server DBA. We have disaster recovery plan. We implement Log shipping . My question after the server failiure, when production server up again ,how to point stand by server to production server?, any help will be appreciated.
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
I am trying to upgrade a SQL Server 6.5(Cluster) to SQL Serevr 7.0 (Cluster)..I already have an intsllation of 7.0(On a Cluster),so this means that 6.5 and sql 7 are on seperate cluster's ,if i try to upgrade from 6.5 Cluster to 7.0 Cluster is asks me to uncluster 6.5 and 7.0 is this correct ,assume i cannot break the cluster then what???.. what is the best way i can achieve this functinality.....
When I try to migrate a database on a SQL Server 2000 server to a SQL Server 2005 server with the Copy Database Wizard of the SQL Server Management Studio, I'm confronted with the following problem;
Performing operation...
- Add log for package (Success) - Add task for transferring database objects (Success) - Create package (Success) - Start SQL Server Agent Job (Success) - Execute SQL Server Agent Job (Error) Messages * The job failed. Check the event log on the destination server for details. (Copy Database Wizard)
When I take a look at 'Event viewer' on the SQL 2005 server, the following error is displayed;
InnerException-->An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I already enabled the MSSQLSERVER network configuration protocols (TCP/IP and Named Pipes ).
I need to be able to run a DTS package from a computer that doesn't have any SQL tools on it. What do I need to copy over to that machine to do so? dtsrun.exe, dll's, etc. Thanks
What Does the "SQL" Stand for? I am just starting to teach myself Visual Studio Programing and some other applications. I can build any computer system that is out there and I have; So I think it is now time for me to study modern programing.
I started waching the Visual LESSONS, provided by Microsoft and I must say "Programing has come a long way since Micosoft (BASICA) and (DOS)"..... I am very enthusiastic about the new wave Software laguages....
Computing has been my hobby as well as a outstanding educational tool, I feel that what makes it so great is that you can spend all you life working or playing with them and NEVER reach and end.... So as a retired Machine and ToolMaker I will lean a new field at my own pace.... And Who Knows????????????
Thank you All......... ToolMan59........ Long Life And Good Health to All.......
I've developed a website and it's hosted by a hosting company. Lately i've registered a new domain with a new virtual hosting account. I've transfered my web files succesfully. But migrating the sql server failed for a couple of times now. My database containes many tables with many products. My hosting provides doesn't give me the opportuniy to restore my backup which i've backuped from my old server. First I tried to use the import and export tool of sql server 2005. This was very easy and it succeeded. But this tool only migrates the tables and the views. All the common stored procedures of asp.net membership are not exported. So I can't login at the moment. I've tried to generate a sql script with all the stored procedures with sql server management studio. But If i want to run this script on my new db, it fails with various errors. I tried to use the aspnet_regsql tool to create all the membership tables and stored procedures. If this succeeds, I can import and export my old db to the new one. But i'm getting a error while trying to use the aspnet_regsql tool. The error number is 290 and the error is: How can I fix this? Er is een fout opgetreden bij het uitvoeren van het SQL-bestand InstallMembership.sql. Het SQL-foutnummer is 290 en het SqlException-bericht is: Invalid EXECUTE statement using object "Relation", method "SetUseVarDecimal".----------------------------------------Details van fout----------------------------------------SQL Server: Database: [samet]Geladen SQL-bestand:InstallMembership.sqlOpdrachten mislukt:/*************************************************************//*************************************************************//*************************************************************/DECLARE @ver intDECLARE @version nchar(100)DECLARE @dot intDECLARE @hyphen intDECLARE @SqlToExec nchar(400)SELECT @ver = 8SELECT @version = @@VersionSELECT @hyphen = CHARINDEX(N' - ', @version)IF (NOT(@hyphen IS NULL) AND @hyphen > 0)BEGIN SELECT @hyphen = @hyphen + 3 SELECT @dot = CHARINDEX(N'.', @version, @hyphen) IF (NOT(@dot IS NULL) AND @dot > @hyphen) BEGIN SELECT @version = SUBSTRING(@version, @hyphen, @dot - @hyphen) SELECT @ver = CONVERT(int, @version) ENDEND/*************************************************************/IF (@ver >= 8) EXEC sp_tableoption N'aspnet_Membership', 'text in row', 3000/*************************************************************//*************************************************************/IF (EXISTS (SELECT name FROM sysobjects WHERE (name = N'aspnet_Membership_CreateUser') AND (type = 'P')))DROP PROCEDURE dbo.aspnet_Membership_CreateUserSQL-uitzondering:System.Data.SqlClient.SqlException: Invalid EXECUTE statement using object "Relation", method "SetUseVarDecimal". bij System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) bij System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) bij System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) bij System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) bij System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) bij System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) bij System.Data.SqlClient.SqlCommand.ExecuteNonQuery() bij System.Web.Management.SqlServices.ExecuteFile(String file, String server, String database, String dbFileName, SqlConnection connection, Boolean sessionState, Boolean isInstall, SessionStateType sessionStatetype)
Hello! We are planning migrating to different server. I know the answers how to migrate all jobs and DTS packages. But the only question I have is "How to migrate logins and passwords?"
What is the best way to transfer logins? Can't you just export syslogins table into text file and then import it into the new server?
HI all, Could any one pls suggest me, how i have to migrate to sql server 7.0 from db2. Pls also recommend some sites where will i get the information regarding this migration. Thank you all.
Does anyone know what aspnet_regsql.exe requires to run stand-alone? I have to apply the .NET 2.0 Management/Role API to a sql2000 database on a machine that does not have the .net 2.0 framework installed.
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?
Can I have warm stand by database on SQL 2000 Server.The source server will be SQL 7.0. In another words can i shipp transaction logs from SQL 7.0 and make Warm stand by on SQL 2000 with SQL 7.0 full and transaction log backups Thanks Mike
I have a sql server db that works fine when I connect via the internet and from the network, but when I try to connect after disconnecting from the network it doesn't find the database (even though the sql server db is on the machine I am using after disconnecting, of course).
Is there something wrong with my connection string? Could it be the Windows/SQL Server/Mixed Authentication mode?
Maybe the best question I could ask is, if I want to run sql server as a web back-end, as a network utility, and as a local db for a windows app, how should I have it set up from a security/authentication standpoint?