Minimum Memory Requirments To Run SQL 2005 Workstation On Windows XP
Feb 22, 2006
We have a couple XP machines with only 256Mb of RAM and have Windows 2000 client tools installed. What are the minimum hardware requirements for SQL 2005 (Workstation) on an XP desktop?
My boss thinks since we have been blissfully ignorant and running fine with 256Mb then their is no need to upgrade memory in these machines.
I need a link to backup my argument.
This link wont help
http://www.microsoft.com/sql/editions/standard/sysreqs.mspx
As it doesn't specify workstation requirments to run SQL 2005.
View 2 Replies
ADVERTISEMENT
Apr 26, 2007
I'm trying to use SQL Management Studio to connect from a Vista SQL 2005 client w/ SP2 over to a Windows XP workstation running SQL server developer edition (non-sp2) using windows authentication.
I'm already preauthenticated by network shares to the xp workstation. This worked just fine in windows xp but stop working in vista.
After searching around, i found out that vista handles trusted authentication differently than windows xp due to changes in the SSPI. Logging in as sql authentication works fine. Logging in as windows authentication does not.
UPDATE: I found out that two workstations running vista and sql 2005 sp2 cannot connect to each other using windows trusted authentication!!!
What the heck?
UPDATE: I found out that my IIS 7.0 using ASP.NET and connecting to SQL 2005 (non sp2) on a Windows 2003 server (SP1) WILL connect to the database using trusted authentication... apparently IIS can access the credentials and pass them to the sql 2005 box just fine. My Sql 2K5 SP2 tools cannot. I'm forced to use SQL authentication to the box.
Same thing applies with a Windows XP SP2 box running SQL 2005 (non sp2).
Here is my sql server error log off of the windows xp workstation:
2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2.
2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100]
2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1.
2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]
How can i Fix this issue?
[1] Client side:
What is the connection string in you app or DSN?
N/A
If client fails to connect, what is the client error messages?
Is the client remote or local to the SQL server machine?
Remote
Can you ping your server?
YES
Can you telnet to your SQL Server?
YES
What is your client database provider?
SQL Management Studio
Is your client computer in the same domain as the Server computer?
WorkGroup
What protocol the client enabled?
Shared Memory & TCPIP
Do you have aliases configured that match the server name portion of your connection string?
NO
Do you select force encryption on server and/or client?
NO
[2] Server side:
What is the MS SQL version?
SQL Server 2005
What is the SKU of MS SQL?
Developer
What is the SQL Server Protocol enabled?
Shared Memory & TCPIP
Does the server start successfully?
YES
If SQL Server is a named instance, is the SQL browser enabled?
N/A
What is the account that the SQL Server is running under?
Network Service
Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider?
YES
Do you make firewall exception for SQL Browser UDP port 1434?
N/A
[3] Platform:
What is the OS version?
Client - Windows Vista Final w/ SQL Server 2005 SP2 & Network Client SP2
Server - Windows XP Professional SP2 w/ SQL 2005 Server Developer Edition
Do you have third party antivirus, anti-spareware software installed?
None
[4] Misc:
If you have certificate configuration issue: Please use €ścertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question.
N/A
Tips:
1. Find SQL Server Errorlog: Default to C:Program FilesMicrosoft SQL ServerMSSQL.#MSSQLLOG
2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2.
2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100]
2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1.
2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]
[1] Client side:
What is the connection string in you app or DSN?
N/A
If client fails to connect, what is the client error messages?
Is the client remote or local to the SQL server machine?
Remote
Can you ping your server?
YES
Can you telnet to your SQL Server?
YES
What is your client database provider?
SQL Management Studio
Is your client computer in the same domain as the Server computer?
WorkGroup
What protocol the client enabled?
Shared Memory & TCPIP
Do you have aliases configured that match the server name portion of your connection string?
NO
Do you select force encryption on server and/or client?
NO
[2] Server side:
What is the MS SQL version?
SQL Server 2005
What is the SKU of MS SQL?
Developer
What is the SQL Server Protocol enabled?
Shared Memory & TCPIP
Does the server start successfully?
YES
If SQL Server is a named instance, is the SQL browser enabled?
N/A
What is the account that the SQL Server is running under?
Network Service
Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider?
YES
Do you make firewall exception for SQL Browser UDP port 1434?
N/A
[3] Platform:
What is the OS version?
Client - Windows Vista Final w/ SQL Server 2005 SP2 & Network Client SP2
Server - Windows XP Professional SP2 w/ SQL 2005 Server Developer Edition
Do you have third party antivirus, anti-spareware software installed?
None
[4] Misc:
If you have certificate configuration issue: Please use €ścertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question.
N/A
Tips:
1. Find SQL Server Errorlog: Default to C:Program FilesMicrosoft SQL ServerMSSQL.#MSSQLLOG
2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2.
2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100]
2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1.
2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]
View 48 Replies
View Related
Jul 31, 2007
We just upgraded the memory of our database server from 2GB to 4GB. And its OS is windows 2003 standard and sql is 2005 standard edition. According to microsoft(http://msdn2.microsoft.com/en-us/library/ms143685.aspx and http://msdn2.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits_windows_server_2003), this configuration should allow database use up to 4 GB memory. My question is : Do I need to do anything(such as: adjust the maximum memory in management studio) to let our server be able to consume this extra 2 GB memory?
Does this solution http://support.microsoft.com/kb/274750 apply for SQL server 2005?
View 1 Replies
View Related
May 4, 2007
We have a SQL 2005 installed in Windows 2003 64 bit system, which has 16 CPU and 32GB RAM, but the performance is poor. SQL server is AWE enable and the sql start account with "Lock Pages In Memory". I checked the task manager and it looks that the SQL server used only about 300 MB memory. Here is what I found:
http://blogs.msdn.com/psssql/archive/2006/11/28/sql-server-becomes-sluggish-or-appears-to-stall-on-64-bit-installations.aspx?CommentPosted=true#commentmessage
What I need to do?
Thanks
View 5 Replies
View Related
Aug 3, 2007
Hi,
I am testing SQL 2005 Standard (32 bit) on a Windows 2003 Server 64 bit with 8GB of RAM? Should I enable the AWP Setting or not and should I change the maximum server memory (currently saying 2GB)?
Thanks!
Tom
View 1 Replies
View Related
Apr 1, 2006
The computers here at work run Windows 2000 5.00.2195 SP4. Everything checks out with the minimum requirements at http://msdn.microsoft.com/vstudio/express/support/sqlreadme/#_3462_setup_issues_238p
However, one of the "Reports" from the installation says the machine does not meet the minimum requirements, but provides no details. It installs and I have Admin rights on this machine, but I can't even connect to the Northwind database that I downloaded.
Is this due to our logging process where the "system" is actually in another country? (ie, "CITYNAME/Username"
Any help is appreciated!
Jason
View 4 Replies
View Related
Sep 18, 2006
I'm having some problems debugging SQL Server stored procedures on a SQL Server 2005 server. I have installed Visual Studio 2005 on a workstation running Windows XP, now I'm trying to debug a ASP.Net web application that has some code that executes the stored procedures on a Windows 2003 Server running SQL Server 2005.
I opened VS2005 ... created a connection to the SQL Server 2005 instance ... open the Stored procedure ... right click the stored procedure name and selected Step into Stored Procedure and the following message is displayed:
Unable to start T-SQL debugging.Could not attach to SQL Server process on 'ServerName'.
Any ideas.
Thanks,
View 2 Replies
View Related
Aug 9, 2006
It appears that there is no way to install SQL Server 2005 Workstation Components on an x86 operating system (XP in this case) if you have the x64 install disks (Standard Edition). Can someone verify this?
I am finding it hard to believe that workstation components for a standard Windows client environment are not distributed with the version of SQL Server that matches Windows 2003 x64.
Thanks,
Chris
View 1 Replies
View Related
Aug 10, 2001
Can I run SQL server 7 on a P133 server with 32MB of RAM?
View 3 Replies
View Related
Jun 6, 2007
Off of the MSDN SQL Server 2005 Enterprise Edition, what is the MSI I should use to install SQL Server 2005.
I have to Upload all files to a server, and this is going to be painfully slow. Can anyone tell me what the minimum is to upload and install SQL Server Enterprise (not Express)?
(For 32 and 64 bit non-Itanium machines)
View 7 Replies
View Related
Mar 20, 2006
Hello. I am trying to install only the Workstation Components portion of SQL Server 2005 and I get about halfway through and the installation errors out. The error is:
EventType: sql90setup
P1: installtoolsaction
P2: 0xc0000006
P3: 0x78158a35
P4: 0xc0000006
P5: setup_sqlactionenginelistener.cpp@198
P6: setup.exe@2005.90.1399.0
P7: none
This happens after the second disk of the installation is about halfway through installing and then it throws an error stating that "The wrong volume is in the drive. Please insert volume SQLSRVRS into drive D. Cancel, Try Again, Continue" I replace the disc with the first disc and if I pick "Continue" it will display the error above. If I pick "Try again" the installation finishes, but there are components missing from Visual Studio.
---------------------------------------------------------------------------------
Here is the log file:
=== Verbose logging started: 3/16/2006 14:03:49 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (58:00) [14:03:49:483]: Resetting cached policy values
MSI (c) (58:00) [14:03:49:483]: Machine policy value 'Debug' is 0
MSI (c) (58:00) [14:03:49:483]: ******* RunEngine:
******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapSetupSqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (c) (58:00) [14:03:49:483]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (58:00) [14:03:49:483]: Grabbed execution mutex.
MSI (c) (58:00) [14:03:49:483]: Cloaking enabled.
MSI (c) (58:00) [14:03:49:483]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (58:00) [14:03:49:483]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (D4:80) [14:03:49:499]: Grabbed execution mutex.
MSI (s) (D4:BC) [14:03:49:499]: Resetting cached policy values
MSI (s) (D4:BC) [14:03:49:499]: Machine policy value 'Debug' is 0
MSI (s) (D4:BC) [14:03:49:499]: ******* RunEngine:
******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapSetupSqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (s) (D4:BC) [14:03:49:499]: Note: 1: 2203 2: C:Program FilesMicrosoft SQL Server90Setup BootstrapSetupSqlRun_Tools.msi 3: -2147287037
MSI (s) (D4:BC) [14:03:49:499]: MainEngineThread is returning 3
MSI (c) (58:00) [14:03:49:499]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (58:00) [14:03:49:499]: MainEngineThread is returning 3
=== Verbose logging stopped: 3/16/2006 14:03:49 ===
Thank you very much,
BJ
View 7 Replies
View Related
Aug 7, 2006
I have installed the Workstation components on my local PC, which also contains VS 2005 and SQL Express. I installed the WS components so that I could run the full blown version of SQL Management Studio from my PC, to remove SQL 2005 servers.
I tried to update the Workstation components to SP1, but the SP1 package stops at the Setup Support Files, step and terminates claiming the package does not support SQL Express. I realize the package is not intended for Express, I simply need to update Management studio.
I tried running the Post SP1 Tools hotfix and it complains that it will not update SP0 of the tools.
I have successfully updated Express to SP1 and applied the Post hotfixes as well. Is there any way to patch just Management studio on a system with Express installed?
Thank,
Jim
View 2 Replies
View Related
Feb 15, 2007
Hello.
When I install SQL Server 2005, it all goes well except that it fails to install these two:
- SQLXML 4
- workstation components and tools
When I try to install these two from the CD in the Setup folder of the CD 2 with the files sqlxml4.msi and sqlRun_Tools.msi (if I remember these names correctly), it gives me an error:
'Ce package d'installation n'est pas pris en charge par ce type de processeur'
Sorry. My SQL CDs are in french, but it roughly translates to the message:
This installation package is not taken by this processor.
I thought that my hardware configuration does not meet the requirements. But I have a Pentium 4, 2Gig RAM, over 100Gig free HD space. Also I tried to install on other computers to no avail. This is a fresh install, that is, there is no previous SQL Server 2000 in it, no VS.NET 2005 or before. Nothing. I have just a fresh, new computer.
Can anyone help, please?
Jean
View 10 Replies
View Related
Apr 5, 2007
I'm setting up SQL Server 2005 Replication. I have purchase a processor license for SQL Server 2005. Do I need a Windows CAL for each device that will be accessing the replication via IIS?
Thanks!
Matt
View 1 Replies
View Related
Apr 29, 2008
I am having trouble installing disc number 2 on sql standard 2005( I installed disc one) I get the message my workstation components are already installed etc.It will not allow me to go any further It seem like everything installed Here is my summary.... I unistalled vs 2 express 2005---I never used it......
Here is my list on my vista ultimate computer sql server business intelligence, sql server management studio, analysis services installed configuration tools documentation pefmorance tools Did I need to install disc 2 instead of disc 1?
one I am using vista Please help ? I tried opening business intelligence studio it says it has compability issues
Here is my log:
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Professional (Build 6000)
Time : Tue Apr 29 14:13:59 2008
Machine : BILLPREC690
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_1.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_1.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_2.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_2.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_3.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_3.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_3.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_4.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_4.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_4.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_5.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_3.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_5.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_5.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_6.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_4.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft Visual Studio 2005 Premier Partner Edition - ENU
Product Version : 8.0.50727.42
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_PPESku_1.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_6.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BOL_1.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_6.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Integration Services
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_DTS.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLXML4_1.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQL.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLXML4_2.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Analysis Services
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_AS.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Notification Services
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_NS.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Reporting Services
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_RS.log
--------------------------------------------------------------------------------
Machine : BILLPREC690
Product : Microsoft SQL Server 2005 Tools
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_Tools.log
--------------------------------------------------------------------------------
View 6 Replies
View Related
Apr 20, 2007
My server is a dual AMD x64 2.19 GHz with 8 GB RAM running under Windows Server 2003 Enterprise Edition with service pack 1 installed. We have SQL 2000 32-bit Enterprise installed in the default instance. AWE is enabled using Dynamically configured SQL Server memory with 6215 MB minimum memory and 6656 maximum memory settings.
I have now installed, side-by-side, SQL Server 2005 Enterprise Edition in a separate named instance. Everything is running fine but I believe SQL Server2005 could run faster and need to ensure I am giving it plenty of resources. I realize AWE is not needed with SQL Server 2005 and I have seen suggestions to grant the SQL Server account the 'lock pages in memory' rights. This box only runs the SQL 2000 and SQL 2005 server databases and I would like to ensure, if possible, that each is splitting the available memory equally, at least until we can retire SQL Server 2000 next year. Any suggestions?
View 8 Replies
View Related
Apr 27, 2008
Hello,
I have installed successfully Microsoft SQL server 2005 in MSCS.
However the set up did not install Workstation components (client tools - SSMS etc).
I have successfully installed workstation components in one node of cluster.
However setup is giving following error while installing workstation components on other node. (From this node MS SQL server 2005 was installed).
Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
I did "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, /setup".
It executed but no error, no output.
Any gues, help in isolating issue?
Any more information required.(Media is ok. Setup has been tried after reboot. There is enough disk space.)
Regards.
Mahesh
===========
Setup
1) Microsoft Cluster of two nodes.
2) Hardare - HP Blade servers
3) OS - Windows 2003 EE with SP2
4) SQL Server 2005 Standard Edition with SP2.
=============================
MSI (s) (B0:7C) [17:40:20:390]: Note: 1: 1722 2: SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A 3: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe 4: /setup
MSI (s) (B0:7C) [17:47:23:609]: Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
MSI (s) (B0:7C) [17:47:35:921]: Note: 1: 1729
MSI (s) (B0:7C) [17:47:35:921]: Product: Microsoft SQL Server 2005 Tools -- Configuration failed.
MSI (s) (B0:7C) [17:47:35:953]: Cleaning up uninstalled install packages, if any exist
MSI (s) (B0:7C) [17:47:35:953]: MainEngineThread is returning 1603
MSI (s) (B0:A0) [17:47:36:062]: Destroying RemoteAPI object.
MSI (s) (B0:80) [17:47:36:062]: Custom Action Manager thread ending.
View 1 Replies
View Related
Dec 10, 2006
I have found that orig tested 64 bit on our 64bit windows 2003server...about 1 year ago...and company decided to use sql 32 bit on the64bit osmy question and any information is very welcomeis there any things in need to know about awe withmemory above 4g ...whilst using 32 bit sql on a 64bit osi want to increase the memory on the server buti really don't know what im up against since this ismixed system 32 bit sql and 64 bit osthanksmike
View 4 Replies
View Related
Feb 15, 2008
Hi all,
What are the minimum permissions required by the SQL Server 2005 Upgrade Advisor (UA)? I could not find it in the documentation.
Obviously being a local Administrators Windows group and a member of sysadmin SQL Server role will do the trick.
But will being a member of only the sysadmin SQL Server role be enough? I know that the UA does want to read the registry.
Running it under just sysadmin generates the following type of errors:
Database Server
PreUpgrade
Requested registry access is not allowed.
WINSOCKPROXY
Database Server
PreUpgrade
Requested registry access is not allowed.
FTUNSIGNEDCOMPONENTS
Database Server
PreUpgrade
Requested registry access is not allowed.
NETPROTOCOL
Database Server
PreUpgrade
Requested registry access is not allowed.
FTMULTIPLEINSTANCES
Database Server
PreUpgrade
Requested registry access is not allowed.
INVALIDNAMEDPIPE
Database Server
PreUpgrade
Requested registry access is not allowed.
FTCOMPONENTREG
Database Server
PreUpgrade
Requested registry access is not allowed.
FTACCTPASS
The issue then is whether these are significant or not. If the UA is only reading the registry to determine if SSAS, DTS, etc is installed then that is not important. But if it is affecting the end result because it cannot read critical information from the registry that is another matter.
TIA
View 1 Replies
View Related
Jul 13, 2006
I do get the warning about Minimum Hardware Requirement, but can
find nothing in the detail requirements to exclude my PCs configuration.
I have installed:
IE 6.0 sp1
IIS as a part of Win 2000 Professional Edition SP4
I have also used ..aspnet_regiis -r to register ASP.NET 2.0
.NET Framework 2.0
SQL Server Native Client
SQL Server Setup support files
PC includes:
Pentium III 800 MHz
512 MB memory
HardDrive C: 5.92 GB (1.37 GB free)
HardDrive D: 13.1 GB (9.11 GB free)
I have tried several times to install SQL Server 2005 Developer Edition
(most recently from MSDN Disk 3097.1) I have tried to
complete an uninstall before each attempt.
I am, successfully, running Visual Studio 2005.
Any suggestions will be appreciated.
View 5 Replies
View Related
Mar 10, 2004
Hi all, new to the forum.
I am in the process of building a 3+1 Win2k3 cluster with SQL 2000. Once I got through all the funky install issues, everything is running great. In fact, working with the new cluster services has been such a breath of fresh air compared even to Win2K. The SAN abilities of W2K3 with on the fly drive additions and such are just awesome.
Anyway, the issue I am seeing has to do with memory. The boxes all have 8gb. First thing I noticed was Win2K3 seems to automatically enable the /PAE option. It's not in the boot.ini but the server "knows" it is using AWE support, which is fine. What confuses me is if I give SQL (awe enabled) a fixed 7.5gb of RAM to play with, it seems to actually use it, without the 3gb option or any regard for the OS. I was able to push it to 7.9gb leaving the OS about 50mb and it allowed it, or at least it looks like it allows it. Target and total memory counters for SQL Memory show it using the full 7.9gb, but taskmgr shows SQL using 80mb. I seem to remember reading that this is normal somewhere; taskmgr can't accurate display memory use. The available physical memory in taskmgr does reflect that all physical ram is in use.
Adding the PAE and 3GB options to the boot.ini appears to have made no impact. Almost like they were already there anyway?
Can anyone explain Win2k3 and SQL 2000 memory stuff to me? I feel dumb right now.
Thanks!
View 4 Replies
View Related
Dec 25, 2007
Hi all,
We have SQL Server 2005 Entp 32-bit on Windows Server 2003 Entp.Edtion 64-bit. ( Total memory = 16 Gb)
1) So, in this case , do i need to enable AWE Configuration from SQL Server Side ( 32-bit).
And what settings( AWE, /PAE) i should enable on OS (i.e.) on Windows Server 2003 (64-bit) in boot.ini file.
Because right now, i dont see any switches in boot.ini file.
2) And with 16 GB of RAM, what should be the ideal setting for memory ( Min & Max).
Please give some ideas on this.
Thanks.
View 5 Replies
View Related
Mar 11, 2004
Can anyone confirm that SQL 2000 Standard Edition is still limited to 2GB of memory utilization on Windows 2003 Server?
In addition, anyone have suggestions for deploying SQL 2000 on Windows 2003?
TIA
View 1 Replies
View Related
Oct 26, 2007
Hi all,
Whenever am rebooting the windows ce 4.2 device. It is uninstalling the sql server ce 2.0 installation files.
if i try to run an application next time it will ask me to install sql server ce 2.0 first.
How can i write the sql server ce 2.0 as permanantly in the memorydisk like a non volatile memory..
(or)
Is there any other method to fix this.?
Can any one please help me? Thanks in advance.
Regards,
Kumaran A
View 1 Replies
View Related
Feb 10, 2006
This doesn't make any sense. I am trying to install SQL Server 2005 on SBS 2003 with Service Pack 1. According to Windows Update, there is nothing left for me to install. However, I am getting this error (while installing SQL Server Express and the Developer Edition):
"Your operating system does not meet Service Pack level requirements for this SQL Server release. Install the Service Pack from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server setup again."
When I go to the link, there is nothing there to download (it takes me to the main Microsoft download page). I meet all the requirements that I have found. What gives?
Thanks,
Scott
View 36 Replies
View Related
Oct 4, 2007
I am looking for some recommendations for memory sizing and options for a SQL 2000 Cluster. This is a two node cluster built on Windows 2003 ENT SP1 (x86). Both the nodes have the following hardware:
- 4 x Dual Core AMD Processors
- 16 GB Memory
- EMC Shared Disk
We are running six SQL 2000 instances and don't expect each of these instances to use more than 1.7 GB of memory. All these instances are going to support BizTalk 2004 Databases. I already have /PAE enabled on the nodes. I am looking for the following answers:
- Do I need to enable AWE on all the instances even if the instances ? Currently, we don't have that enabled and we have seen some issues regarding excessive paging even when there is physical memory available. The DBAs think that we don't need to enable AWE. I am bit confused on this one.
- We normally run 3 instances on each node and would like size the cluster in such a way that it can take six instances in case of a node failure
Any input will be highly appreciated.
View 4 Replies
View Related
Mar 26, 2008
Hallo there,
I just upgraded from Windows XP Pro to Windows Vista Bussiness and tried to reinstall SQL Server 2005 Developers Edition. After the installation i downloaded (using microsoft windows update) and installed all the service packs for sql and vista available.
My problem is when i open sql server management studio and try to connect to my default instance using windows authentication and database engine, an 18456 error occurs.
I enabled all the protocols and all the ports
I disabled windows firewall and antivirus (eset nod32)
I installed all service packs available
I have also installed Visual Studio 2005 without installing sqlexpress
But nothing happens!
Please i am very desperate, any information will be gratefully accepted.
This is my installation Information
Code Snippet
Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 6.0.6001.18000 (longhorn_rtm.080118-1840)
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 7.0.6001.18000
Microsoft .NET Framework 2.0.50727.1434
Operating System 6.0.6001
Thank you in advance,
Patonios
View 3 Replies
View Related
Jul 11, 2007
Hello everybody!
I hope that someone could help me.
I have a problem when i start sincronyzing with the emulator of MSVS2005 to SQL2005 in Windows Vista. I have the same program in the emulator, but sincronyzing with windows XP Pro and no problem...
I configure the connection to use the IUSR.
The source code that i use:
repl.InternetUrl = @"http://laptop/SQLMobileIIS/sqlcesa30.dll";
repl.Publisher = @"laptop";
repl.PublisherDatabase = @"database";
repl.PublisherSecurityMode = SecurityType.NTAuthentication;
repl.Publication = @"Pubdatabase";
repl.Subscriber = @"SQLMobile";
repl.SubscriberConnectionString = @"Data Source='" + nomeFicheiroBD + "';Password='3409'";
The error that returns is:
"Failure to connect to SQLServer with provided connection information. SQL Server does not exist, access is denied because the IIS user is not a valid user on the SQL Server, or the password is incorrect"
Does anybody knows what i can do?
HELP I NEED SOMEBODY TO HELP!
Thanks!
View 1 Replies
View Related
Jan 21, 2008
Hi I am using SQL 2005 64 Enterprise edition with 30GB memory.
I have allowed SQL to use min 0 memory and maximum 20GB but sql is only showing it can use 100MB of memory
Anyone know the answer
Ap
View 7 Replies
View Related
Oct 25, 2006
Ran a trace using profiler and found that the CLR is not using the ASPNET windows account to log into SQL 2005, instead using the admin. Some ado.net code does not work properly as a result. Have had to change the connection string to use SQL logins.Spec: Win XP Pro; IIS 5; 2.0.Is this normal? Where security and permissions are concerned, what changes, if any, are there from SQL 2000?
View 5 Replies
View Related
Sep 16, 2007
Here'a a break down of what I've done so far.
* Windows 2003 32bit Enterprise with 10gb RAM
* SQL 2005 32bit Enterprise
* boot.ini - have added /3GB /PAE switches
* Confirmed which account SQL Server is running under and added that account to Local Policies/User Rights Assignment/Lock pages in memory
* Enabled AWE in SQL SERVER
* set minimum and maximum server memory to 9gb
* Rebooted.
Task manager says the following:
sqlservr.exe - 95MB usage * I know this is normal when using AWE right?
The actual physical memory used is 3.13GB and never goes higher. So this leads to believe that SQL is utilizing 3GB because of the /3GB switch, but it's not using the rest like it should be. I tried it without the /3GB switch and it only went up to about 2.1GB usage.
I've turned on performance monitor and SQL server target memory says 8.65 GB while the Total Server Memory says 2.45GB.
I've run:
EXEC sp_configure 'show advanced options'
RECONFIGURE
GO
EXEC sp_configure 'awe enabled'
RECONFIGURE
GO
And it confirms that the running value for both is 1
Please help.
View 20 Replies
View Related
Dec 10, 2007
My organization is currently migrating about 35 databases from SQL 2000 to SQL 2005. Most of the databases are small with the largest being about 6gb. These databases are not very transaction intensive. We are about half way through as we started the project a year ago. We purchased new hardware for this SQL 2005 so it is a side-by-side migration and it has been going well so far. I made one oversight which I think will come back to haunt us down the line. I installed Windows Server 2003 Standard R2 Edition and of course now I am considering putting more RAM in the server. We have 4 GB of RAM in the server and of course Standard Edition will not address more 4GB of physical ram. I have not seen any memory pressure yet but as databases are migrated over the amount of physical RAM drops. My buffer hit cahce ratio and page life expectancy performance counters are fine so far. The server is a brand new HP DL 380 G5 with with tons of disk and processing power, but only 4GB of RAM. I can't migrate to another server with more ram obviously.
1. What would you do in a situation like this?
2. I could do an in-place upgrade to Windows Server 2003 Enterprise R2. Has anyone attempted an in-place upgrade? I have no applications
on this server, just SQL 2005 Standard.
3. Would the /3gb switch be an option? I have heard mixed reviews on this one.
As far as database optimization, %75 of the databases are third party so we have little flexibility in tuning them or redesigning
tables.
Thanks,
Alex
View 2 Replies
View Related
Nov 14, 2007
We have been using SQL 2005 for quite sometime however recently I have been seeing memory issues. SQL will grow to use the maximum available! I have set min 1024MB and max to 15360MB leaving approx 5GB for OS.
Windows 2003 64 / SQL2005 64
Lock pages to memory - enabled
Min and Max - 1024, 15360
AWE not checked
We have recently added link server using OLEDB DB2 provider. Could this be the issue?
View 8 Replies
View Related
