Hi everyone,
I want to upgrade SQL server 2000 to SQL server2005, what are the issues which I have to look at during my upgrading process, what sort of problems might be faced during the upgrading?
Lot of thanx
Ok another "I Don't crap about SQL and should read the book" question:
I am purchasing new servers for a company that currently runs SQL 2000 in a Windows 2k3 environment. Not sure why, but they want to upgrade to SQL 2005. The have 4 SQL 2000 Standard editions. Three with 1 processor licensing and 1 with per device licensing. The new servers will have 2 x Quad core processors. Since I know licensing is per "Physical Processor" I need to purchase an additional license for a second processor on each machine that has two. How do I purchase a second one? Can do this online? Whats the cost? Another question I have is: Do I need to buy SQL 2005 Standard (Full Standard Version) install on the new machine and migrate by databases from SQL 2000 over to the new ones? Or is there like an upgrade kit where I install SQL 2000 on the new ones then buy a update to SQL 2005 disc? Please don't laugh at my questions, I am by no means a SQL GURU. Thanks in advance.
I was with online chat with Microsoft, and the guy said there is no upgrade option between SQL versions like there is from Windows XP home to Pro, or 2000 to XP. Is this true? Has anyone else done this before? I'm wanting to upgrade from SQL 2000 to SQL 2005. I was hoping there was a 32-bit to 64-bit upgrade as well within the versions, but that doesn't seem available either. I will settle for SQL 2005 32-bit if I can upgrade, but if I have to buy a whole other license for it, I might as well get x64. If anyone has done this or has experience in this, any information would be much appreciated!
View 1 Replies View RelatedAny expert in the house willing to show me how to upgrade from SQL2000 to SQL2005?
Thanks!
Please recommend best learning material for quickly upgrading skill sets from SQL 2000 to SQL 2005
Hey all!
I currently am running 8.00.760 which is the Standard Edition of SQL 2000 SP3 (or it might be 3A - no way to tell)
I have downloaded and am preparing to install 9.0.3042.1 SQL 2005 SP2 but when I run the exe file it informs me that "This machine does not have a product that matches this installation package."
Both are 32 bit versions and the precise exe I'm attempting to run is: SQLServer2005SP2-KB921896-x86-ENU.exe
I'm logged on as the server admin.
The server is running Windows Server 2003 Standard Edition SP2.
It has dual Xeon 3.2ghz dual core processors and 4gb of RAM
All of the documentation indicates that this upgrade path is acceptable.
The only thing I have noticed in the Sys Requirements (http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&displaylang=en)
is that the supported OS is Windows 2003 SP1 (and no sign of SP2 in the list!) could that be what the issue is?
Does anyone have any advice on where I should look to tackle this issue? I'd like to explore all free avenues before dropping any money for the paid SQL support services.
Thanks for any help.
Geoff Garcia
March of Dimes
ggarcia@marchofdimes.com
914-997-4275
I restored a 2000 database back up in to my 2005 database and it works fine. THe only problem is that I cannot create diagrams.
I get the following message:
Database diagram support objects cannot be installed because this database does not have a valid owner. To continue, first use the Files page of the Database Properties dialog box or the ALTER AUTHORIZATION statement to set the database owner to a valid login, then add the database diagram support objects.
I have checked the db_owner and that is a valid owner.
I changed a few times to different owners and still could not install the diagrams..
Any ideas?
thanks
I have to upgrade and move SQL Server 2000 databases from a platform using Server 2000 to one running SQL Server 2005. The server nameinstances will need to be the same so that a number of third party applications and front end systems that connect, and are outside of my control, will not need any data source changes. The servers will be on the same network and can't co-exist with the same name so I guess that I have to go "big bang".
Does anyone have any suggestions for a strategy that I can use?
Does anyone know of any issues that I should be aware of?
I have run the SQL Server 2005 Upgrade Advisor and it tells me the databases should upgrade OK with a few minor issues that can be fixed after.
Thanks,
Hi All
I am upgrading an SQL 2004 Sp4 server to SQl 2005 which is incalled on a High Availability NSCS cluster
I am facing the following problem in the process
Summary.log file contents
--------------------------------------------------------------------------------
Machine : <Node B of Cluster>
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : \Node AC$Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_NodeB_SQL.log
Last Action : ValidateUpgrade
Error String : Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Service pack requirement check:
Your upgrade is blocked because of service pack requirements. To proceed, apply the required service pack and then rerun SQL Server Setup. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Error Number : 29543
____________________________________________
Following is the logs in file \Node AC$Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_NodeB_SQL.log
*********************************************************************************************************************************************
Loaded DLL:
C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlboot.dll
Version:
2005.90.1399.0
Action "
languageUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:
Condition "differentLanguage_with_1033_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Condition "allowableBaseVersion_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Loaded DLL:
C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlboot.dll
Version:
2005.90.1399.0
Action "
maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:
Condition "sameVersion_as_9.0.139906_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Loaded DLL:
C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlboot.dll
Version:
2005.90.1399.0
Action "
skuUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:
Condition "NOT_sameSKU_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Condition "allowableBaseVersion_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Loaded DLL:
C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlboot.dll
Version:
2005.90.1399.0
Action "
versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:
Condition "allowableBaseVersion_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Action "
virtualization_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:
Condition "virtualization_NotSupported_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Action "
warningPatchLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:
Condition "diffInstancePatchLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Action "
warningSPLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:
Condition "diffInstanceSPLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Action "
warningUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:
Condition "warningUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Condition "allowableBaseVersion_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.
Running:
FeaturePhaseAction
at:
Info 2008.2008
/
1
/
4
17
:
26
:
17
Complete:
FeaturePhaseAction
at:
Info 2008.2008
/
1
/
4
17
:
26
:
17
, returned
true
Error Code: 0x80077367 (29543)
Windows Error Text: Source File Name: sqlcaupgradeproduct.cpp
Compiler Timestamp: Mon Sep 19 01:07:45 2005
Function Name: sqls::UpgradeProduct::CanUpgrade
Source Line Number: 142
---- Context -----------------------------------------------
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29543
MSI (s) (8C!A8) [17:26:39:194]: Product: Microsoft SQL Server 2005 -- Error 29543. Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Service pack requirement check:
Your upgrade is blocked because of service pack requirements. To proceed, apply the required service pack and then rerun SQL Server Setup. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Error 29543. Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Service pack requirement check:
Your upgrade is blocked because of service pack requirements. To proceed, apply the required service pack and then rerun SQL Server Setup. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Mon Feb 04 17:26:39 2008
<Func Name='ValidateUpgrade'>
Added FTE to SqlUpgrade property
Added REPL to SqlUpgrade property
<Func Name='updateFeatureSellection'>
Error Code: 0x80077367 (29543)
Windows Error Text: Source File Name: sqlcaupgradeproduct.cpp
Compiler Timestamp: Mon Sep 19 01:07:45 2005
Function Name: sqls::UpgradeProduct::CanUpgrade
Source Line Number: 142
---- Context -----------------------------------------------
********************************************************************************************************************************************
I checked the version of teh SQL server on both teh nodes ...using select @@version query it shown as 8.00.2039 which is SP4.
But i do not understand why it is failing with this error.
Kindly suggest
Thanks
Naresh P.
We are in the process of going through all test steps for upgrading one of our servers with SQL 2000 to SQL 2005. Currently Server 2000, which we will be upgrading as well after SQL is upgraded and running properly. We have Reporting Services installed as well. I am using a test server which is an exact mirrored image of the live server but is not added to the domain.
I am going through the steps of selecting the components, selecting the instance, and then selecting the installed components I want to upgrade (SQL Server 8.0.??? and Reporting Services 8.0.???) and click next.
The upgrade analysis begins. Everything is ok through the SQL Server analysis but when I click next to start the upgrade analysis on Reporting Services I get this error message, "SQL Server Setup requires administrator permissions for the upgraded SQL Server instance. To continue, log in with an administrator account." I am logged in as the local admin which should have the required permissions to upgrade Reporting Services, plus the local admin was ok for the SQL Server upgrade anaylis
I have no idea what could be causing this permissions issue. I did run the SQL 2005 Updrade Analyzer utility and performed all the "before" steps. What could be the issue?
I am in the position that my DR environment will be down while the upgrade from 2000 to 2005 is being done. The upgrade instructions say that update statistics and DBCC check database should be done. With the size of my database I estimate that this will take over 2 days to do. Is this step a necessary step for the upgrade. I am looking to reduce my expose. Keep in mind that DR get overwritten each night.
Hello everyone, I am upgrading from SQL Server 2000 to SQL Server 2005. Any caveats? Can I just detach the db's and attach them into 2005. Or is there any conversion I should run or import first?
Thanks,
I have one 32-bit SQL 2000 server that is our enterprise-wide reporting server (we'll call it RS) and another 32-bit SQL 2000 server that serves as a stored proc data source for certain reports on that server (we'll call it DS). I am about to go through an upgrade/migration of DS to 64-bit SQL 2005 and was wondering if:
it is possible to just change the data source location on RS and point the old reports against the new DS server?
there are any necessary steps to take within RS to make the data source (DS reference on RS) compatible with the destination (report on RS)?
it is possible/easy to bulk-migrate all the RDL's for a particular data source from RS to DS?
Does anyone know any of the answers to these questions?
Thanks in advance!
Hello all,
I'm finding the documentation online to upgrading from 2000 to 2005 fairly poor.
What are the upgrading options and which one is the best option for a web server database.
Also what are best practices pre-upgrade, during upgrade and post-upgrade.
Cannot find much online.
Also since this question will be asked often might as well make it a sticky.
Thanks
Hello
I'm trying to upgrade a Microsoft SQL 2000 (8.00.760 SP3) server to SQL 2005.
It€™s a standard install, std version, not very big databases, default instance, plenty of memory etc. OS is a 2003 server recently upgraded from 2000. All patches etc are installed.
Upgrade was going fine and had got approx 90% through, had started the 2005 db service and converted the databases before it got the following error:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Invalid connection string attribute Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
The 'For help' link returned the helpful... €˜We are sorry but we can€™t help€™...
Worked through http://msdn2.microsoft.com/en-us/library/ms143698.aspx but not 100% applicable and didn€™t resolve.
Partially rolled back, rebooted and resumed install but failed in the same place. Ended going back to a backup snapshot so is now back running as SQL 2000.
Excerpt from install log is below...
Thanks in advance for any assistance.
<Finished SQL statement: Wed Oct 10 21:25:21 2007>
<Started SQL statement: Wed Oct 10 21:25:21 2007> BEGIN DECLARE @GroupName AS nvarchar(4000) SET @GroupName = QUOTENAME(N'PROPMAN-DATASQLServer2005MSFTEUser$PROPMAN-DATA$MSSQLSERVER') EXECUTE(N'grant execute on sp_fulltext_getdata to ' + @GroupName) END
<Finished SQL statement: Wed Oct 10 21:25:22 2007>
Service MSSQLSERVER is being stopped at Wed Oct 10 21:25:22 2007
Service MSSQLSERVER with parameters '' is being started at Wed Oct 10 21:25:34 2007
Attempt to start service when it is already running
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Service MSSQLSERVER started at Wed Oct 10 21:25:40 2007
<EndServerDowntime Wed Oct 10 21:25:40 2007>
Loaded DLL:
C:WINNTsystem32Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=01S00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Invalid connection string attribute
Error Code: 0x8007ea62 (60002)
Windows Error Text: Source File Name: libodbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@upgradeconnect
Source Line Number: 148
---- Context -----------------------------------------------
sqls:equenceInstaller::launchAction
Staring action SqlScript
SqlUpgradeScriptHlpr
Connecting to SQL Server
ExecuteUpgradeSqlCommands
sqlConnect
Originial error was 8007ea62 (60002)
Error Code: 60002
MSI (s) (5C!20) [21:26:20:164]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Invalid connection string attribute Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.'.
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Invalid connection string attribute Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Loaded DLL:
C:WINNTsystem32Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=01S00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Invalid connection string attribute
Error Code: 0x8007ea62 (60002)
Windows Error Text: Source File Name: libodbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@upgradeconnect
Source Line Number: 148
---- Context -----------------------------------------------
My question is two fold:
We have a database 65 GB in size and has grown over 12 years.
1) How can I upgrade to 2005 without downtime?
2) Our upgrades on SQL 2000 now can take upwards of 10 hours to add just a column and rebuild index tables?
Any way we can speed this up without detaching the database and going offline?
thanks,
Larry Sitka
Does anyone know of a resource that describes the steps to upgrade an instance of MSDE(2000) to SQL 2005 Standard?
We found something on a MS site that indirectly indicated you could upgrade the MSDE to SQL Express and then upgrade Express to the full version of 2005, but that method created quite a bit of problems(System databases), which we were not able to resolve short of uninstalling MSDE and the apps and installing SQL 2005 and re-installing the apps; but I have to believe there is a better way.
Thanks! Bob McEuen
How do SQL 2000 service packs play a role in upgrading? That is, can SQL 2000 Standard with no Service Packs(SP) be upgraded to SQL 2005 Standard, or does SQL 2000 Standard have to have a certain service pack??
View 1 Replies View RelatedI recently upgraded from SQL Server 2000 to SQL Server 2005. I have Oracle databases I need to share data with. I was using the Heterogeneous Services (hsodbc) from Oracle and connected to SS 2000 fine. Since I've upgraded, I can't use hsodbc to connect to my SS 2005 database. I get the following error:
ORACLE GENERIC GATEWAY Log File Started at 2006-09-06T09:40:07
hoainit (3): ; hoainit Exited with retcode = 0.
hoalgon (7): ; hoalgon Entered. name = edw.
DB_ODBC_INTERFACE (2085): ; [Microsoft][SQL Native Client][SQL Server]Login
failed for user 'edw'. (SQL State: 28000; SQL Code: 18456)
DRV_InitTdp: DB_ODBC_INTERFACE (2085): ; [Microsoft][SQL Native Client][SQL
Server]Login failed for user 'edw'. (SQL State: 28000; SQL Code: 18456)
nvRETURN (F:WorkConnect_4_6_3srcdrvDRV_BIND.C 356): -2220
nvRETURN (F:WorkConnect_4_6_3srcavNAV_BIND.C 293): -2220
hoalgon (7): ; hoalgon Exited with retcode = 28500.
My upgrade of SQL Server 2000 to SQL Server 2005 is being blocked as follows:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding
FTCATALOGPATH
DEPRECATEDSP
FTCATALOGNAMERESTRICTION
FTNONPERSISTEDCOMPCOL
Many thanks
JMX
Hi,
i've used sql 2000 to create reports. Now i have almost 100 reports with lot of history (snapshots). Now i've developed the same reports in 2005 (basically upgraded the reports). If i upload the new reports, the 2000 history will be lost. Is there anyway that i can upgrade to 2005 and save the history ??
Thanks
I just installed SQL 2005 on a new box. I want to move a database from a SQL 2000 server to the new server. Can I detach the database, copy it and attach it in the new server without having problems?
I'm concerned that if the datafile is in SQL2000 format, when I connect it to SQL2005 server, will it still be in old format or will it upgrade?....or is this something you don't worry about....and why?
Thanks,
Craig
Hello!
We have a module in our business-application, that automatically installs merge replication of the business-application's database, both at publisher and subscribers. It's intended for Sql-2000. Now we need it to be applicable also for Sql-2005, so the module requires some changes, because, as we noticed, sql-2005's replication technology differs from Sql-2000's one.
A few questions to experts, familiar with Merge Replication in SQL-2005:
1. Is it possible to create hybrid replication, with publisher running at SQL-2000 (MSDE) and subscribers running at SQL-2005 Express? Merge publication is not supported in SQL 2005 Express, but some users may require option to use the application at free-of-charge database platform.
2. How deep are changes in merge replication implementation at system level? Is it just modified a bit since SQL-2000, or changed entirely? This knowledge is needed, because the module uses some low-level features (executing system sp's, querying replication-specified tables, etc.). For example, when we tried to create subscription of existing publication in SQL 2005 using the module as is, we found out that sp_addmergepullsubscription_agent doesn't use @encrypted_password parameter anymore, and subscription creation process failed.
3. If anybody has experience using merge replication creation/deletion/detection scripts, generated by SQL 2000, in SQL 2005! Please, tell - what more problems may happen?
Thanks!
I am having issues trying to do an in place upgrade of msde 2000 to sql express 2005. When I try to upgrade it bombs when it reaches "Running action to shutdown instance(Run As Normal User)" with the following error:
Service 'computername' could not be stopped. Verify that you have sufficient privileges to stop system services. The error code is (16386).
I've tried an upgrade on a clean test machine, and it goes through without any problems. I am logged into an account with local admin permissions. If any one has any ideas, they would be appreciated.
I'm having problems upgrading to 2005 Trial from 2000 Standard Edition.Despite the ms docs saying this was a valid upgrade path and runningthe upgrade advisor which did not highlight a non-valid upgrade path, Iam getting the following error :-Name: Microsoft SQL Server 2000Reason: Your upgrade is blocked. ......Edition check:Your upgrade is blocked because of edition upgrade rules. ......Any ideas?Richard.
View 1 Replies View RelatedIs it just me, or are features missing in Management Studio? I mean, where is the "Export Objects" option when exporting data? Why is it so difficult to register a remote server? Why do the object views suck? And most important, why is the documentation the worst software documentation I have EVER SEEN?!
Things that were easy in Enterprise Manager with Client Network Utility and Query Analyzer seem impossible, difficult, or maybe just hidden in Management Studio. If it is there, the documentation sure doesnt tell you how to find it.
Please someone tell me that it's just me. Tell me that the features are there but Im not doing something right. I feel like putting my head in between my door opening and banging the door against it.
Hi,
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403)
Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
2)
Command attempted:
{call sp_MSensure_single_instance (N'Merge Agent Name', 4)}
Error messages:
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368)
Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036)
Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @retcode = -1 and thus cannot obtain exclusive lock on resource
EXEC @retcode = sys.sp_getapplock @Resource = 'Merge Agent Name',
@LockMode = 'Exclusive',
@LockOwner = 'Session',
@LockTimeout = 0,
@DbPrincipal = 'MSmerge_PAL_role'
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
can anyone help?
Thanks
I don't have any idea about upgrading databases.I am been given this task.
It would be great if you let me know what are all the things to be considered upgrading the sql server 2000 databases to sql server 2005.
Please let me know
Thanks
Hi,
I would like to find out if there is any way to upgrade SQL Server 2000 (Ent) to 2005 (STD)
The Instance has many logins and jobs etc and I dont want to loose those
A document or some advice on how to go about it would help
Thanks
Has anyone attempted an upgrade from sql7 to 2000? is it a difficult process? what happens to the users. Is there a good site i can go to to get this info ?
Thanks in advance
Anyone know of any issues I should be aware of when upgrading from sql 7.0 to 2000? Is it a problematic proccess?
liz
We are currently still running SQL6.0 on NT4 server, and we want to upgrade to SQL2000. My question: how easy is it to upgrade from SQL6.0 to SQL2000?
View 3 Replies View RelatedCurrently running SQL Server 7, and have databases. I want to upgrade to SQL Server 2000. How can achieve it without delete or losing my databases. This is NOT a production server, BUT I still want to keep my databases. Ideally I would like to uninstall and reinstall so that there are no SQL Server 7 files lying around when I have SQL 2000 running. Thanks.
View 1 Replies View Related