Viewing 15 posts - 76 through 90 (of 96 total)
Take a look at the log file that contains more details of the failure. To figure out the correct log file start with %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\summary.txt. In this...
March 7, 2006 at 8:42 am
Hi Cory,
You can find the details on Edition "upgrades" here: http://msdn2.microsoft.com/en-us/library/ms143393(SQL.90).aspx
I've included the key part of the table for your convenience.
SQL Server 2005... |
March 1, 2006 at 9:26 am
You can check out the following blog for details on configuring remote connects: https://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
February 24, 2006 at 11:31 am
This is not recommended. The supported and recommended method for running SQL2K and SQL2K5 side-by-side is to install SQL2K first and then install SQL2K5. You can go ahead and try...
February 23, 2006 at 9:24 am
You can find the details for changing collations in SQL Server Books Online:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/25b8a3da-a83b-411f-9bb9-ca684306b4d7.htm
or you can access Books Online from MSDN:
http://msdn2.microsoft.com/en-us/library/ms177439(SQL.90).aspx
Cheers,
Dan
February 20, 2006 at 9:54 am
I assure you the change was not made to discourage feedback. On the contrary, the feedback we receive from customers is incredibly valuable to the product team. All feedback and...
February 20, 2006 at 9:47 am
First, let's make sure that everything you think is installed is actually installed.
1. Go to Control Panel -> Add or Remove Program Files.
2. Scroll down to the entry "Microsoft...
February 9, 2006 at 8:31 am
Can you provide any more details on what you're experiencing. As for minimum requirements, you'll need WinXP SP1, Win2K SP4, or Win2K3 SP1. Also, you need Windows Installer 3.1. You...
February 6, 2006 at 9:35 am
The logic in DMO and SMO is slightly different. It appears that in more cases DMO is more correct than SMO. However, to get the most correct answer try calling...
January 30, 2006 at 2:28 pm
Take a look at the setup log files located under %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\. Most likely you'll need to look inside the *_core(local).log file. This sounds like WMI problem....
January 24, 2006 at 9:03 am
Read the upgrade topic in SQL Server 2005 Books Online. You can access it online at http://msdn2.microsoft.com/en-us/library/ms144245(en-US,SQL.90).aspx
January 20, 2006 at 9:30 am
For all of the details, check out: http://msdn2.microsoft.com/en-us/library/ms143393(en-US,SQL.90).aspx
Upgrade from | Supported Upgrade Paths |
---|
SQL Server 2000 Standard Edition SP3 or later1 | SQL Server... |
January 20, 2006 at 9:29 am
Hmmm. Yes check the logs located at %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\. The other thing that may be going on is you installed something from the Tools.MSI which means now...
January 18, 2006 at 9:08 am
It was removed from SQL Server 2005. In SQL Server 2000 it was FYI only and didn't control any server functionality. What do you want to use it for?
Cheer,
Dan
January 18, 2006 at 9:01 am
Be sure that you install SQL Server 2000 first and then SQL Server 2005. Installing SQL2K after SQL2K5 will present some problems with COM registration and uninstall.
January 13, 2006 at 9:30 am
Viewing 15 posts - 76 through 90 (of 96 total)