Upgrading DB Server To 2005 *after* The Install?
Feb 15, 2007
I had a SQL2000 DB Server with a simple database. I did an "in place" upgrade to SQL2005 expecting the DB Server and databases to upgrade. However, now when I run SQL Server Management Studio and enter the query:-
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
I get the answer:-
8.00.2039 SP4 Enterprise Edition
Why didn't it upgrade? And how do I upgrade it now? I'm very confused!
View 4 Replies
ADVERTISEMENT
Mar 4, 2006
Hello,
Thanks for reviewing my question. I have installed VisualStudio 2005 on a computer and would like to know if I can install SQL 2005 Server and replace the SQL Express version? Will VS recognize it?
Many Thanks to the Experts
Peter
View 2 Replies
View Related
Feb 18, 2008
How do I upgrade Sql Server 2005 Express to SP2 if I also have SQL Server 2005 Enterprise SP2 already on the same box? I installed Sql Server 2005 Enterprise first, then applied SP2, then installed Visual Studio 2008 (which installed SQL Server 2005 Express).
When I try to upgrade Sql Server 2005 Express to SP2 using the special Express edition of SP2, I get an error message that says "None of the selected features can be installed". I end up having to cancel the install of SP2.
I'm left with SQL Server 2005 at level 9.0.3054 and SQL Server 2005 Express at 9.0.3042. How can I bring SQL Server Express 2005 to the same level as SQL Server 2005 Entperprise?
View 2 Replies
View Related
Mar 29, 2007
Hello!! How can I upgrade from SQL Server 2005 Express Edition to SQL Server 2005 Enterprise Edition? I see allot of example of upgrading from SQL Server 2000 to SQL Server 2005, but no example on upgrading from SQL Server 2005 Express to SQL Server 2005 Enterprise or Standard. Is this possible?
View 6 Replies
View Related
Oct 25, 2007
I first tried installing the DVD and of course it told me I must use the command prompt installation method to include the line SKUUPGRADE=1. I found good references to this in the following links:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2208593&SiteID=1
http://msdn2.microsoft.com/en-us/library/ms144259.aspx
Below is the command I issued at the command prompt:
start /wait d:serverssetupsetup.exe ADDLOCAL=ALL INSTANCENAME=URHCS63SQL2005DSS UPGRADE=SQL_Engine SKUUPGRADE=1 /qb
My servername is URHCS63 and my instance is SQL2005DSS.
When I execute this command, a installation dialog box opens briefly and then disappears and nothing else happens. Here are the results of the bootstrap log file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Time : Thu Oct 25 16:17:48 2007
URHCS63 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
SQL Server Setup was interrupted. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Thu Oct 25 16:20:08 2007
Any ideas on why this is not working for me?
View 9 Replies
View Related
Feb 6, 2007
Hello All,
I'm running Windows XP SP2 and I had SQL Server 2005 running on my box. I needed to run the SP1 upgrade but it doesn't seem to work. I ran Windows Update and the list showed I need to install SP1 and it looked like it ran fine but when I checked the version after the upgrade it hadn't upgraded to .2047. I went back to Windows Update and it said I still needed SP1. So I tried downloading SP1 and running it myself still no luck. So then I decided to uninstall SQL Server 2005 completely, reinstall it and try the SP1 again (using Windows Update) and nothing in fact I'm now getting the error...
"Error Code: 0x2BC4"
...which I haven't been able to find anything on. Does ANYONE have any ideas on what might be happening?
Thanks in advance for any help.
Mike
View 3 Replies
View Related
Jun 28, 2007
Hello,
I have a new HP ProLiant ML115 Server with the "Windows Server 2003" operating system. I will be upgrading from SQL Express 2005 to SQL Server 2005 and I wanted to know will the upgrade run smoothly and what are the necessary, if any, measures I may need to take before and/or after I upgrade to ensure that all my databases and files are carried over?
View 1 Replies
View Related
Feb 6, 2007
I am currently running Windows XP Professional Service Pack2. It already has MSDE & SQL Server 2000 installed (although I just uninstalled MSDE in the vain hope that it might present the installer with a more straightforward upgrade).
I have tried installing with the default instance & a new instance (I don't really care - I just need to install the darn thing). I just want the basic database & Books On-line, nothing fancy.
Here is the Summary log, for what it's worth:
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Tue Feb 06 16:45:14 2007
Machine : ANTHONYY1
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_OWC11_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BackwardsCompat_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : MSXML 6.0 Parser (KB927977)
Product Version : 6.00.3890.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_OWC11_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BOL_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BackwardsCompat_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : MSXML 6.0 Parser (KB927977)
Product Version : 6.00.3890.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_MSXML6_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : SQLXML4
Error : Setup is preparing to continue with the installation.
--------------------------------------------------------------------------------
Here is the SQLSetup0011_ANTHONYY1_Core(Local).log
Microsoft SQL Server 2005 Setup beginning at Tue Feb 06 16:45:14 2007
Process ID : 2560
C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/1/6 16:45:14
Complete: LoadResourcesAction at: 2007/1/6 16:45:14, returned true
Running: ParseBootstrapOptionsAction at: 2007/1/6 16:45:14
Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/1/6 16:45:14, returned true
Running: ValidateWinNTAction at: 2007/1/6 16:45:14
Complete: ValidateWinNTAction at: 2007/1/6 16:45:14, returned true
Running: ValidateMinOSAction at: 2007/1/6 16:45:14
Complete: ValidateMinOSAction at: 2007/1/6 16:45:14, returned true
Running: PerformSCCAction at: 2007/1/6 16:45:14
Complete: PerformSCCAction at: 2007/1/6 16:45:14, returned true
Running: ActivateLoggingAction at: 2007/1/6 16:45:14
Complete: ActivateLoggingAction at: 2007/1/6 16:45:14, returned true
Running: DetectPatchedBootstrapAction at: 2007/1/6 16:45:14
Complete: DetectPatchedBootstrapAction at: 2007/1/6 16:45:14, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2560" returned false.
Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions:
Condition "Setup is running locally." returned true.
Running: PerformDotNetCheck2 at: 2007/1/6 16:45:14
Complete: PerformDotNetCheck2 at: 2007/1/6 16:45:14, returned true
Running: InvokeSqlSetupDllAction at: 2007/1/6 16:45:14
Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.1399.0
<Func Name='DwLaunchMsiExec'>
Examining 'sqlspars' globals to initialize 'SetupStateScope'
Opening 'MachineConfigScope' for [ANTHONYY1]
Trying to find Product Code from command line or passed transform
If possible, determine install id and type
Trying to find Instance Name from command line.
No Instance Name provided on the command line
If possible, determine action
Machine = ANTHONYY1, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = XMLDomDocument, Result = 0 (0x0)
Machine = ANTHONYY1, Article = Processor, Result = 0 (0x0)
Machine = ANTHONYY1, Article = PhysicalMemory, Result = 0 (0x0)
Machine = ANTHONYY1, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = ANTHONYY1, Article = OSVersion, Result = 0 (0x0)
Machine = ANTHONYY1, Article = OSServicePack, Result = 0 (0x0)
Machine = ANTHONYY1, Article = OSType, Result = 0 (0x0)
Machine = ANTHONYY1, Article = iisDep, Result = 0 (0x0)
Machine = ANTHONYY1, Article = AdminShare, Result = 0 (0x0)
Machine = ANTHONYY1, Article = PendingReboot, Result = 70011 (0x1117b)
Machine = ANTHONYY1, Article = PerfMon, Result = 0 (0x0)
Machine = ANTHONYY1, Article = IEVersion, Result = 0 (0x0)
Machine = ANTHONYY1, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = ANTHONYY1, Article = COMPlus, Result = 0 (0x0)
Machine = ANTHONYY1, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = ANTHONYY1, Article = MDAC25Version, Result = 0 (0x0)
*******************************************
Setup Consistency Check Report for Machine: ANTHONYY1
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: IIS Feature Requirement, Result: CheckPassed
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
<Func Name='PerformDetections'>
0
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>
<Func Name='DisplaySCCWizard'>
CSetupBootstrapWizard returned 1
<EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'>
Failed to find help file for LCID :2057
Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0
<EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'>
Complete: InvokeSqlSetupDllAction at: 2007/1/6 16:49:35, returned true
Running: SetPackageInstallStateAction at: 2007/1/6 16:49:35
Complete: SetPackageInstallStateAction at: 2007/1/6 16:49:36, returned true
Running: DeterminePackageTransformsAction at: 2007/1/6 16:49:36
Complete: DeterminePackageTransformsAction at: 2007/1/6 16:49:47, returned true
Running: ValidateSetupPropertiesAction at: 2007/1/6 16:49:47
Complete: ValidateSetupPropertiesAction at: 2007/1/6 16:49:47, returned true
Running: OpenPipeAction at: 2007/1/6 16:49:47
Complete: OpenPipeAction at: 2007/1/6 16:49:47, returned false
Error: Action "OpenPipeAction" failed during execution.
Running: CreatePipeAction at: 2007/1/6 16:49:47
Complete: CreatePipeAction at: 2007/1/6 16:49:47, returned false
Error: Action "CreatePipeAction" failed during execution.
Action "RunRemoteSetupAction" will be skipped due to the following restrictions:
Condition "Action: CreatePipeAction has finished and passed." returned false.
Running: PopulateMutatorDbAction at: 2007/1/6 16:49:47
Complete: PopulateMutatorDbAction at: 2007/1/6 16:49:47, returned true
Running: GenerateRequestsAction at: 2007/1/6 16:49:47
SQL_Engine = 3
SQL_Data_Files = 3
SQL_Replication = 3
SQL_FullText = 3
SQL_SharedTools = 3
SQL_BC_DEP = 3
Analysis_Server = -1
AnalysisDataFiles = -1
AnalysisSharedTools = -1
RS_Server = -1
RS_Web_Interface = -1
RS_SharedTools = -1
Notification_Services = -1
NS_Engine = -1
NS_Client = -1
SQL_DTS = -1
Client_Components = 3
Connectivity = 3
SQL_Tools90 = 3
SQL_WarehouseDevWorkbench = 3
SDK = 3
SQLXML = 3
Tools_Legacy = 3
TOOLS_BC_DEP = 3
SQL_Documentation = 3
SQL_BooksOnline = 3
SQL_DatabaseSamples = -1
SQL_AdventureWorksSamples = -1
SQL_AdventureWorksDWSamples = -1
SQL_AdventureWorksASSamples = -1
SQL_Samples = -1
Complete: GenerateRequestsAction at: 2007/1/6 16:49:48, returned true
Running: CreateProgressWindowAction at: 2007/1/6 16:49:48
Complete: CreateProgressWindowAction at: 2007/1/6 16:49:48, returned true
Running: ScheduleActionAction at: 2007/1/6 16:49:48
Complete: ScheduleActionAction at: 2007/1/6 16:49:48, returned true
Skipped: InstallASAction.11
Skipped: Action "InstallASAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.18
Skipped: Action "InstallASAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.22
Skipped: Action "InstallASAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.9
Skipped: Action "InstallASAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result.
Skipped: InstallDTSAction
Skipped: Action "InstallDTSAction" was not run. Information reported during analysis:
No install request found for package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.11
Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.12
Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.18
Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.22
Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.9
Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result.
Skipped: InstallNSAction
Skipped: Action "InstallNSAction" was not run. Information reported during analysis:
No install request found for package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.11
Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.12
Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.18
Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.22
Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.9
Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result.
Skipped: InstallRSAction.11
Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.18
Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.22
Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result.
Running: InstallSqlAction.11 at: 2007/1/6 16:49:48
Installing: sqlsupport on target: ANTHONYY1
Complete: InstallSqlAction.11 at: 2007/1/6 16:49:51, returned true
Running: InstallSqlAction.12 at: 2007/1/6 16:49:51
Installing: sqlncli on target: ANTHONYY1
Complete: InstallSqlAction.12 at: 2007/1/6 16:49:55, returned true
Running: InstallSqlAction.18 at: 2007/1/6 16:49:55
Installing: owc11 on target: ANTHONYY1
Complete: InstallSqlAction.18 at: 2007/1/6 16:49:56, returned true
Running: InstallSqlAction.21 at: 2007/1/6 16:49:56
Installing: sqlwriter on target: ANTHONYY1
Complete: InstallSqlAction.21 at: 2007/1/6 16:49:58, returned true
Running: InstallSqlAction.22 at: 2007/1/6 16:49:58
Installing: bcRedist on target: ANTHONYY1
Complete: InstallSqlAction.22 at: 2007/1/6 16:50:0, returned true
Running: InstallSqlAction.9 at: 2007/1/6 16:50:0
Installing: msxml6 on target: ANTHONYY1
Complete: InstallSqlAction.9 at: 2007/1/6 16:50:2, returned true
Running: InstallToolsAction.11 at: 2007/1/6 16:50:2
Installing: sqlsupport on target: ANTHONYY1
Complete: InstallToolsAction.11 at: 2007/1/6 16:50:5, returned true
Running: InstallToolsAction.12 at: 2007/1/6 16:50:5
Installing: sqlncli on target: ANTHONYY1
Complete: InstallToolsAction.12 at: 2007/1/6 16:50:8, returned true
Skipped: InstallToolsAction.13
Skipped: Action "InstallToolsAction.13" was not run. Information reported during analysis:
No install request found for package: "PPESku", referred by package: "tools", install will be skipped as a result.
Running: InstallToolsAction.18 at: 2007/1/6 16:50:8
Installing: owc11 on target: ANTHONYY1
Complete: InstallToolsAction.18 at: 2007/1/6 16:50:10, returned true
Running: InstallToolsAction.20 at: 2007/1/6 16:50:10
Installing: BOL on target: ANTHONYY1
Complete: InstallToolsAction.20 at: 2007/1/6 16:52:2, returned true
Running: InstallToolsAction.22 at: 2007/1/6 16:52:2
Installing: bcRedist on target: ANTHONYY1
Complete: InstallToolsAction.22 at: 2007/1/6 16:52:4, returned true
Running: InstallToolsAction.9 at: 2007/1/6 16:52:4
Installing: msxml6 on target: ANTHONYY1
Complete: InstallToolsAction.9 at: 2007/1/6 16:52:6, returned true
Skipped: InstallNSAction.10
Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result.
Running: InstallSqlAction at: 2007/1/6 16:52:7
Installing: sql on target: ANTHONYY1
Error: MsiOpenDatabase failed with 110
Failed to install package
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
Error: MsiOpenDatabase failed with 110 for MSI D:ServersSetupSqlRun_SQL.msi
Setting package return code to: 1620
Complete: InstallSqlAction at: 2007/1/6 16:52:27, returned false
Error: Action "InstallSqlAction" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Running: InstallToolsAction.10 at: 2007/1/6 16:52:27
Installing: sqlxml4 on target: ANTHONYY1
Error Code: 0x8007006e (110)
Windows Error Text: The system cannot open the device or file specified.
Source File Name: sqlchainingminorbuildactionbehavior.cpp
Compiler Timestamp: Mon Jun 13 14:30:04 2005
Function Name: sqls::MinorBuildActionBehavior::modifyRequest
Source Line Number: 65
---- Context -----------------------------------------------
sqls::InstallPackageAction::perform
Complete: InstallToolsAction.10 at: 2007/1/6 16:55:59, returned false
Error: Action "InstallToolsAction.10" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Action "InstallToolsAction" will return false due to the following preconditions:
Condition "Action: InstallToolsAction.10 has finished and failed." returned true.
Installation of package: "tools" failed due to a precondition.
Step "InstallToolsAction" was not able to run.
Skipped: InstallASAction
Skipped: Action "InstallASAction" was not run. Information reported during analysis:
No install request found for package: "as", install will be skipped as a result.
Skipped: InstallRSAction
Skipped: Action "InstallRSAction" was not run. Information reported during analysis:
No install request found for package: "rs", install will be skipped as a result.
Skipped: RepairForBackwardsCompatRedistAction
Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis:
Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Running: ReportChainingResults at: 2007/1/6 16:55:59
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 1620
Error Code: 0x80070654 (1620)
Windows Error Text: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
Source File Name: sqlchainingsqlchainingactions.cpp
Compiler Timestamp: Thu Sep 1 22:23:05 2005
Function Name: sqls::ReportChainingResults::perform
Source Line Number: 3097
---- Context -----------------------------------------------
sqls::HostSetupPackageInstallerSynch::postCommit
sqls::HighlyAvailablePackage::preInstall
led due to cancel code received from cancel source: 29539
...and here is the SQLSetup0011_ANTHONYY1_SQL.log:
=== Verbose logging started: 06/02/2007 16:52:14 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (00:54) [16:52:14:284]: Resetting cached policy values
MSI (c) (00:54) [16:52:14:284]: Machine policy value 'Debug' is 0
MSI (c) (00:54) [16:52:14:284]: ******* RunEngine:
******* Product: D:ServersSetupSqlRun_SQL.msi
******* Action:
******* CommandLine: **********
MSI (c) (00:54) [16:52:14:284]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (00:54) [16:52:14:284]: Grabbed execution mutex.
MSI (c) (00:54) [16:52:14:299]: Cloaking enabled.
MSI (c) (00:54) [16:52:14:299]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (00:54) [16:52:14:299]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A4:98) [16:52:14:299]: Grabbed execution mutex.
MSI (s) (A4:00) [16:52:14:299]: Resetting cached policy values
MSI (s) (A4:00) [16:52:14:299]: Machine policy value 'Debug' is 0
MSI (s) (A4:00) [16:52:14:299]: ******* RunEngine:
******* Product: D:ServersSetupSqlRun_SQL.msi
******* Action:
******* CommandLine: **********
MSI (s) (A4:00) [16:52:21:080]: Note: 1: 2203 2: D:ServersSetupSqlRun_SQL.msi 3: -2147024873
MSI (s) (A4:00) [16:52:21:080]: MainEngineThread is returning 1620
MSI (c) (00:54) [16:52:21:080]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (00:54) [16:52:21:080]: MainEngineThread is returning 1620
=== Verbose logging stopped: 06/02/2007 16:52:21 ===
I suppose an error dialog (or log message) that actually told you what is wrong and then what to do is too much to ask for. (Or an installer than just copied all the files into place). :(
View 4 Replies
View Related
Oct 10, 2005
A lot of vs.net 2005 documentation talks about how asp.net 2.0 developers can easily build web apps using SQLX and then easily upgrade to SQL Server 2005 when we go to production.Can someone point me to the details? How exactly do I take an .MDF file from my development environment and ??import/attach/restore?? it too a full blown SQL Server 2005.TIA,g
View 1 Replies
View Related
Oct 11, 2006
Hello, everyone:
Currently our system is .NET workframe 1.1 / Visual.NET 2003 plus SQL Server 2000. The developer will upgrade to .NET workframe 2.2. Should I have to update database to SQL Server 2005? And some reasons please.
Thanks
ZYT
View 1 Replies
View Related
Aug 19, 2007
I have upgraded my server from SQL Server 2000 to SQL Server 2005. After upgrading, I noticed that an important option in a specific application isn't working, giving a generic error message ("Cannot update the database").
Using SQL Profiler, I found that the query that fails includes the expression:
Code Snippet
DateAdd(DateInteval.Day, ..., ...)
And the error message is: "'DateInterval.Day' is not a recognized dateadd option".
This query:
Code Snippet
SELECT DateAdd(DateInterval.Day, 2, getdate())
Works on SQL Server 2000 servers, while failing on SQL Server 2005 servers, with the same error message as above.
However, this query:
Code Snippet
SELECT DateAdd(Day, 2, getdate())
Works on both SQL Server 2000 servers and SQL Server 2005 servers.
I searched for documentation of this problem, and couldn't find any.
The code for the original application is lost, so changing it is impossible.
Any help or guidance would be appreciated.
View 8 Replies
View Related
Nov 29, 2006
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
View 1 Replies
View Related
May 9, 2006
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,
View 1 Replies
View Related
Aug 15, 2007
The error I got is:
Hotfix.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
EventType : sqlsesetup P1 : sysdbupg.sql P2 : 0x7361
P3 : odbcstatement__execute_batch@sysdbupg.sql@3 P4 : 0x7361
P5 : lib_odbc_statement.h@91 P6 : unknown P7 : sql9 P8 : hotfix@
P9 : x86 P10 : 3042
Log Location: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.
I tried to search internet, however, I couldn't get solution.
My SQL server 2005 is standard version, OS Windows server 2003 sp2, I am using Administrator account to install it.
Thanks a lot,
Rex
View 9 Replies
View Related
May 16, 2007
Hi I currently have this edition of SQL server on my laptop:
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
It is running on SQL Server Management Studio 2005.
I wish to upgrdade to Developer Edition (as my laptop won't support Enterprise as it's running on Windows XP).
I have some questions, which I would be grateful if somebody could help answering:
1- will all my database remain as they are?
2- Will I loose any functionality?
3- Will it upgrade or intstall a separate edition?
4- Can anybody recommend where to purchase Developer 2005 edition?
5- I currently have 2gb capped database limit on my version, will I get a no capped limit?
6- Will the 2gb Capped limit increase to uncapped once I install (i.e. can i use my previous 2gb database and add more data to above 2 gb)
The main issues are that I need an uncapped limit for my DB's and that I will keep my existing db's.
Many thanks!!!!!
View 2 Replies
View Related
Nov 14, 2007
What are the pro's and con's of these Sql Server 2005 Editions:
WorkGroupStandard
I am having to choose between the two for upgrade, and would be interested to know what your experience would tell me. Though it would be entertaining to go with the victor of a google fight(http://googlefight.com/index.php?lang=en_GB&word1=sql+server+2005+workgroup&word2=sql+server+2005+standard), I should probably be responsible about this.
Thanks,
Jason Knight
Developer
View 1 Replies
View Related
Dec 23, 2007
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
View 3 Replies
View Related
Oct 15, 2007
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 -----------------------------------------------
View 1 Replies
View Related
Jan 3, 2008
Help please...
We have developed a system for a medium size company in NYC using SQL Server 2000.
We are about to go live and thought it may be a good idea to upgrade first from SQL Server 2000 to 2005.
I believe standard edition would be sufficient but I am not 100% sure... There isn't a whole lot of data but high availability is crucial. I was thinking of a 2-node fail over cluster setup and/or mirroring.
We need only one instance of SQL Server with about 30 client machines accessing the same databases.
Any thoughts/comments as far as:
Standard or Enterprise?
What type of licensing? Support agreement?
What about the best setup for highest availability? (fail over cluster vs. mirroring vs. replication)
Thanks,
Toshu.
View 1 Replies
View Related
Aug 6, 2007
Hello,
at the moment I have the following problem:
We have installed a version of the MSDE 2000 Sp3 with our software since 2005. Now we install SQL Server Express 2005 in order to use the latest version and to be compatible with Vista.
We have never had any problems with the MSDE, so it was no problem that we installed the german version (by mistake) because there never was any output at installation time.
When we now upgrade the existing MSDE installing the new version of our software, there are often problems and there are error messages, unfortunately in german, which cannot be read by most of our international users.
The problem is, that there seems to be no possibility to upgrade the existing (german) MSDE with the english version of SQL Server Express 2005.
My question is, if it is possible to upgrade the german MSDE to the english SQL Server 2005 to enable our international users to read the error messages at installation time in english?
Thanks in advance.
Best regards,
Peter
View 4 Replies
View Related
Nov 7, 2005
has anybody tried to do that yet? any experiences? how-tos?
View 3 Replies
View Related
Sep 6, 2006
I 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.
View 6 Replies
View Related
Sep 13, 2007
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
View 3 Replies
View Related
Apr 26, 2006
Hi - quick question.
I wanted to upgrade pre-release version of SQL Express to the latest version, and wanted to make sure that none of the database information would be lost. The thing that concerns me is that it states to uninstall previous versions of SQL Server 2005 Express before installing the latest version. I threw the database tables into a backup directory, and I think this should be fine, but I want to be sure. Let me know. Thanks!
View 4 Replies
View Related
Mar 6, 2007
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
View 9 Replies
View Related
Feb 15, 2007
I never installed previous beta versions on my computer before. But now I have some serious problem after an incomplete de-install and a re-install of SQL server 2005 express advanced. I hope anybody can help me to solve this. Because the first installation eas not succesfull I had to do an de-install. I have tried to unstall through start/control panel/ add-remove programms and even there not all programs were removed. And that caused the problem. After that I wanted to re-install again but an msi file was missing. So I did a de-install agian. Tried to re-install again but with a lot of errors. After looking at the library I found a program: Windows Install CleanUp. I installed it and that even gives an error for all programs installed with SQL 2005.
After that I ran a program called MsiInv to clean but without any succes because this program reported a run-tim error. I have all reports on my computer but don't know how to attach them. If you think you can help me I could send you all the reports.
Regards,
Jan J
View 2 Replies
View Related
Jun 28, 2007
Hi,
I just upgraded to SQL server 2005 and some of my Openrowset to Oracle doesnt work. I found out that the issue occur with field with structure Numeric.
The issue is not solve even when I try to cast the field to varchar. sometimes it succeeded and sometimes I get error 7320 & 7321.
I'm using Oracle connector from SQL to Oracle.
I've 64 bit SQL Server.
Attach the code, the Numeric field is SCORE.
select *
FROM
OPENROWSET('ORAOLEDB.ORACLE',aaaa;bbbb;cccc,
'SELECT AUDIT_OPRID, AUDIT_STAMP, AUDIT_ACTN,EMPLID, ACCOMPLISHMENT, MAJOR_CODE,
CAST(SCORE AS Varchar(250))
FROM SYSADM.PS_RTA_ACCOMPLISHM WHERE 1=2')
Anyone can advice on resolution?
Thanks,
Assaf
View 6 Replies
View Related
Mar 14, 2007
Hello all.
I upgraded a SQL 2000 installation to SQL 2005 this past weekend. Minimal issues overall, but one that did crop up relates to a linked server to an Oracle database. The linked server worked before the upgrade, and stopped working immediately after.
We're running on Windows 2003 x64, latest service pack. The linked server is set up using the MSDAORA provider. The error I'm getting post-upgrade is:
=====================
OLE DB provider "MSDAORA" for linked server "PROD" returned message "ORA-06413: Connection not open.".
Msg 7303, Level 16, State 1, Procedure RDM_GET_REP_LIST_SP, Line 12
Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "PROD".
=====================
A tnsping from the server works fine. I've also tried recreating the linked server. Any help would be appreciated. Let me know what other information would be useful.
Thanks,
Adam
View 3 Replies
View Related
Jun 6, 2006
Hello, you all,
I did all the stuff necessary for the upgrading (the Upgrade Advisor didn't say anything special), but the Setup says the following:
"
Name: Microsoft SQL Server 7.00.1063
Cause: The update is blocked. You can obtain more informations in the online help "Versions- and editionsupdates".
Editions problem:
The update is blocked because of rules for the editions update.
"
Is it possible that an upgrade is not possible with the evaluation edition? Or can there be another cause?
Thanks in advance
Oliver
View 4 Replies
View Related
May 26, 2006
I have never installed sql server before and I didnt know if I just take the sql server 2005 standard edition media and boot off it and do a fresh install that way or do I have to install Windows server
View 3 Replies
View Related
May 15, 2007
I have attached the SAN, configured the Windows Clustering and I'm ready for SQL. SQL Server 2005 was already on this machine as a stand alone. I removed all of the software and I'm reinstalling SQL. The cluster option is not enabled. Any ideas why?
View 1 Replies
View Related
Aug 8, 2007
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
View 1 Replies
View Related
Oct 4, 2006
If i have been using sql server 2005 express for developing my application and i decide to upgrade to sql server 2005 express with advanced services while still working on the same application, what will happen to my application's database. Can i be able to continue with my work with out any major regrets.
View 1 Replies
View Related
