For a SQL/2005 DB Server do I need the /3GB switch or not? I will have IIS running on the server; however, it won't be doing very much as the SQL Database is the main thing:
Windows 2003 R2 Enterprise w/16 GIG RAM 4 CPU (Virtual Machine)
SQL/2005 Enterprise Edition
Hardware: Dell Server 8 CPU w/32 GIG RAM running VM ESX V3
I know I need the /PAE switch to utilize Memory over 4 GB - the question is do I need the /3GB switch along with the /PAE switch?
I have a win2k3 server that i am going to need to upgrade to servicepack 2. It is running sql server 2000(sem reports version 8.0 - ithink that is sql server 2000). It has profiler and query analyzerrunning as well. Are there any caveats i need to be concerned aboutbefore installing win2k3 sp2 on a server with sql server 2000. Thanks
Hey there I am an SQL noob, our bank has no real SQL Admin, we had onw that left but never had a good knowledge transfer. We have 2 SQL servers clustered. IBSQL1 and IBSQL2 they make up cluster IBSQL. We have 2 other servers IBIIS1 ans IBIIS2 and we noticed when installing apps on them that they could not see the database. Yet it can ping IBSQL. The problem is on IBSQL1 and 2 port 1433 is not listening or open. Thus on IBSQL it isn't either of course. I have read of all kinds of people having this issue and most have said you need to manually add a connection string "Provider=sqloledb;Data Source=machineName,1433;Initial Catalog=xx;User ID=xx;Password=xx" Problem is I do not know how to add a connection string.
I need step by step instructions since im new to this. Start/programs/etc..... Apparently it is not enough to open the properties of tcp/ip in the config util and say 1433. You need to reenforce it by adding that string.
As it stands I cannot "telnet ibsql 1433" it tells me to take a hike basically.
So is the connection string the likely cause? or could it be something simpler? Thanks in advance.
Hi all,I have MSDE installed on an HP server as some of the utilities requireda database. I have also subsequently installed SQL 2000 onto thisserver which is a windows 2003 box. I know it complains at the startof the installation but I was under the impression that it would stillwork ok, especially with SP3 applied.I have tried to apply SP3 but it tells me that it is not a SQL2000instance ad setup will exit?Also I have noticed that in the directory structure it has used thedollar sign i.e. mssql$machinename its the same in Enterprise Manager\machinename$InstanceName. Whats that all about? Its not like that onany other server!My plan is to uninstall sql 2k, uninstall HP apps and MSDE andreinstall SQL 2k. Can anyone explain the above though?ThanksGary
We are planning a SQL Server 2005 install on VMware ESX, as thebackend to a Sharepoint Services 3.0 web front end..Do I gain anything at all by installing SS 2005 on Win2k3 ENTERPRISEas the OS instead of Standard??Thank you, Tom
I am attempting to install MS SQL 2000 SP2 on a Windows Server 2003 Enterprise SP1 box. The only installer I can find on the disc is in the MSDE directory and when I run it it immediately gives me this error:
"This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package."
I have tried copying the install files to my local hard drive for install, I have checked the version of my Windows Installer (3.1.4000.1840). I have the SP4 updates ready to go once it's installed, but I just cannot get past that point. I know that the same software version has been installed on other Windows 2003 systems, so why would it have a problem on this one machine?
Hello All and Happy New Year (I believe that is still allowed by the PC police?!)
Has anyone experienced performance problems (i.e. processes taking a lot longer to connect to the database server) after appyling Windows Server 2003 SP2 to a server that was previously running Windows Server 2003 RTM? The version of SQL Server (2000 SP4) has not changed between OS Service Packs.
To set the scene, we upgraded one node of a cluster to Win2K3 SP2 intending to upgrade the other node the following night if no problems were encountered. However, after failing over to the patched node we experienced something akin to a Denial Of Service attack whereby connections were gradually refused until even existing connections were kicked out.
We resolved that issue by disabling the SynAttackProtect Registry key (details http://support.microsoft.com/default.aspx?scid=kb;en-us;899599), but although connections are no longer being refused they are taking a lot longer, e.g. opening a Query Analyzer window now takes several seconds to connect to the database. The actual time taken by the database engine to execute sql queries has not increased, but is perceived by the users as having done so because of the time taken to return results.
I asked our server team to run diagnostics against both nodes and they found no problems and no differences apart from the OS service pack level.
I am about to reopen the case I logged with Microsoft, but thought I'd see if you guys had experienced anything similar.
Microsoft Security Paradigmes are Irritating. I sure they're fine onceyou know what they are, but for the uninitiated it's quitecounterintuitive to work with.I moving an old SQL Server-backend-IIS5/ASP-frontend application toservers with windows 2003 standard edition. One server will run thedatabase the other will run IIS 6.0. Note that i haven't set-up adomain, which i think requires one machine to be domain controllerwhich would decrease performance and stuff. I've simply put them on thesame group.I wan't to restrict access the sql server so only the incommingconnection from the webserver is allowed. I can use either namedpipes(which should be the fastest protocol) or tcpwhich should beslight slower than named pipes) but i seem to have a problem. If I usenamed pipes to connect the IUSR(the user under which IIS is running)must have access-rights to IPC$ share on the sql server. I can't seemto set any access-right directly for IPC$ share, but i can reactivatemy guest user and then it works, everyone can now access the ipc$ shareso it's not really what i'm looking for.I can also connect through TCP( and set up some kind of filter onlyallowing incomming connections on port 1433 from the ip of the webserver.But i don't know how to do this. I've taken a look at the IPSec stuffbut it's all about kerberos authentication and other bull which i don'tthink i need. What i need is simply a ip traffick filter, which doesnothing else but reject incomming connection from all other ip's thanmy webserver.My question is how do I do this? Do i need to have a addtitíon"firewall" service running and if so why, how much extra overhead willthis create for the server. Alternately, is it possible to change theaccess right for the IPC$ share manually?Thanks in advance for any input you might have on this?Regs Jens
I am currently working on with the ASP encryption of my application. I've tried to test the encryption of the connection string using the capicom.dll in my local, and it works successfully. However, I am not quite sure if this will still work after my OS is upgraded to WIN2K3 (my current OS is WINXP). Will this dll component be impacted after the OS Upgrade? or will there be no impact at all?
Any inputs from you guys would be much appreciated.
I am using Windows 2003 Server English Version. I wanna store the big-5data so I install the sql server 2000 as if i install it in the Windows2000 with Server Collation of the Chinese_Taiwan_Stroke_CL_AS.However, the data are stored into the database server in unicodeinstead of big-5 in that of windows 2000 OS.I would like to ask how i can set so that the Sql Server 2000 can storethe big-5 data
Is there any reason why an application running on a 32-bit O/S that works with a SQL Server 2K database would not work with a SQL Server 2K5 64-bit database running on a 64-bit O/S?
It is my understanding that the connection layer (be it ODBC, OLEDB, ADODB, etc) would obfuscate any details regarding the underlying architecture... I wouldn't think the instructions sent would need to be any different, unless there is some deprecated call that is no longer supported.
I have installed in a workstation (windows xp pro) sql 7 server (database engine + client tools). After that I installed sql server 2005 with named instance (hostmyinstance).But I didn't end this installation. I had a message saying me that there are problems on clients tools. moreover when I open a dos window and type "sqlcmd", I have the same message (client problems). I then change my sql7 port to 1434 (which isn't the default port).But even with that my sql 2005 sqlcmd don't work correctly. My question is :
can one install sql 7 (server + client tools) and sql 2005 (server + client tools) in the same machine ( a workstation [windows xp pro] )?
I need tyo move tables from Oracle 9.2 or 10.2 version to SQL server 2005.Can any one give me some good hints, scripts etc.I try to look into the Business Intellegent Studio, but I only see Report,Analaysis or Integration services - NO DTS.Can someone tell me where to find it. It used to be so easy in 2000.Thanks,Nasir
I have a partition view named StudentRequest with underlying tables StudentRequest_T1 and StudentRequest_T2.
Primary Key is on NumericSchoolDBN, SchoolYear, TermId, StudentID, CourseCode
Partition View
Create View dbo.StudentRequestPartView with SchemaBinding as Select NumericSchoolDBN, SchoolYear, TermId, StudentID, CourseCode, AssignedCourseCode, AssignedSectionId, LockAssignedRequest, UpdatedByPID, UpdatedDate, CreatedByPID, CreatedDate, AuditCommentId, DebugTrace from dbo.[StudentRequest_T1]
union all
Select NumericSchoolDBN, SchoolYear, TermId, StudentID, CourseCode, AssignedCourseCode, AssignedSectionId, LockAssignedRequest, UpdatedByPID, UpdatedDate, CreatedByPID, CreatedDate, AuditCommentId, DebugTrace from dbo.[StudentRequest_T2] go
Partition Tables
CREATE TABLE [dbo].[StudentRequest_T1]( [NumericSchoolDBN] [int] NOT NULL, [SchoolYear] [smallint] NOT NULL, [TermId] [tinyint] NOT NULL Check ([TermID] = 1), [StudentID] [int] NOT NULL, [CourseCode] [varchar](10) NOT NULL, : )
CREATE TABLE [dbo].[StudentRequest_T2]( [NumericSchoolDBN] [int] NOT NULL, [SchoolYear] [smallint] NOT NULL, [TermId] [tinyint] NOT NULL Check ([TermID] = 2), [StudentID] [int] NOT NULL, [CourseCode] [varchar](10) NOT NULL, : )
I am able to insert, update and delete records in the StudentRequest view using simple DML SQL statements i.e.
e.g. Insert into Student Request (NumericSchoolDBN, SchoolYear, TermId,€¦) Values(12345, 2006, 1,€¦)
Delete from StudentRequest Where NumericSchoolDBN = 12345 and TermId = 1
But when I use complex SQL statements using self-joins€¦
Insert into Student Request (NumericSchoolDBN, SchoolYear, TermId,€¦) Select NumericSchoolDBN, SchoolYear, TermID,€¦. From Student Request sr1 left outer join Student Request sr2 on Sr1.NumericSchoolDBN = Sr1.NumericSchoolDBN and Sr1.SchoolYear = Sr2.SchoolYear and Sr1.TermId = Sr2.TermId and Sr1.StudentID = Sr2.StudentID and Sr1.CourseCode = Sr2.CourseCode
I get the following error and I can€™t seem to find any documentation that this is a limitation!!!...
Msg 4439, Level 16, State 6, Procedure Course_UpdateCoursePromotion, Line 232 Partitioned view 'STARS.dbo.StudentRequest' is not updatable because the source query contains references to partition table '[STARS].[dbo].[StudentRequest_T1]'.
We recently migrated from a SQL 2K to 2K5. We had an automatic DTS scheduled every night that would transfer data to a MySQL server on one of our client€™s machine. It worked like a charm in SQL 2K.
I am trying to figure out how I can connect to a MySQL data source using SSIS in 2K5 as I don€™t see an ODBC Destination anywhere in the Data Flow Task; and run the same transfer using 2K5.
Do I have to add a reference of some kind or does 2K5 doesn€™t support ODBC destinations?
Having problems installing SQL 2005 Developers Edition on a Terminal Services Server that already has SQL 2000 Developers Edition on it. I keep getting this error, no matter in what order I install packages:
Failed to install and configure assemblies M:Program FilesMicrosoft SQL Server90DTSTasksMicrosoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2147024894 Error message: The system cannot find the file specified. Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
The help link says to set the DTC service up to run as a network service and start it, but it already is and is already running. Restarting the DTC and then clicking on retry yields the same error.
Any ideas? I've been beating my head against this machine for a couple of days now.
I need to get a server built for a client today. He has sent me the proof of purchase for his SQL2005. He is working on getting me the licence / cd key today (if thats even possible?).
I have our SQL 2005 server CD here that I wanted to use however when I get to the company name stage of the install the CD-key/licence code is greyed out. Any ideas on how I can change the embedded cdkey/licence to the clients so I can use our media today but with our clients cdkey?
This needs to be done today, its extremly important but due to a problem with logistics the media from the client was delayed untill mid next week.
I continue to have issues with SP-2 for SQL 2005 suite. It has now gotten so bad, I have multiple installations, including the TOOLS ONLY on my laptop failing, that I am going to stop ALL future installations of SP-2. The COM+ failures have not been resolved that I can determine. I have tried uninstalling, I have tried SP-1 before SP-2, every combination one can find. HELP.
Time: 05/07/2007 13:24:05.631 KB Number: KB921896 Machine: GA029-MDGRAVES OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.00.1399.06 x86 SQL Server Native Client ENU 9.00.3042.00 x86 Client Components ENU RTM 9.00.1399.06 x86 STANDARD MSXML 6.0 Parser ENU 6.00.3883.8 x86 Backward Compatibility ENU 8.05.1054 x86
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID
********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log Error Number : 29549 Error Description : MSP Error: 29549 Failed to install and configure assemblies c:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087 Error message: Unknown error 0x80131501 Error description: MSDTC was unable to read its configuration information. (Exception from HRESULT: 0x8004D027) ---------------------------------------------------------------------------------- Product : MSXML 6.0 Parser Product Version (Previous): 3883 Product Version (Final) : 6.10.1129.0 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_msxml6.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 1054 Product Version (Final) : 2004 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SQLServer2005_BC.msi.log Error Number : 0 Error Description : ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 29549
I installed SP1 for SS 2005 on a quasi-production server, which is why I didn't mind rebooting the server. Unfortunately, it's been 5 hours and the server still hasn't rebooted. (I see a gray screen and a pointer, and that's it... but there's still disk access happening. I'm not really sure what it's doing.)
What's the best way to avoid the 5 hour reboot in the future?
Is it possible to convert a SQL2K datafile to SQL2K5? I have a 2K database that I need to easily convert to 2K5, I apprecaite any insight on this issue.
Hello All: From my previous post it seems that the general consensus is for me to use backup and Restore to upgrade a dB from SQL2K to SQL2K5.
Could anyone refer me to some explicit instructions for doing this?
I have SQL2K5 and SQL2K on separate servers and I cannot back the dB up to SQL2K5. I also can't access the drives for SQL2K from SQL2K5. I'm hoping it's a simple mistake.
I want to copy a SQL2005 database to a SQL2000 environment? I created a backup from the DB in SQL2005 and moved the file to the other server but SQL2000 says the BAK file is invalid since the backup has structure version 611 while the server supports version 539. Any solution?
I've populated reporting DB's in the past using different techniques:
1. Have Transactions in Data Tier Write to OLTP AND Reporting DB Simultaneously
2. Log Shipping
3. Restore BAckups Nightly
4. Replication
5. DTS
My question is what is the BEST Practice in SQL2k5.
I'm all gung ho about using Mirroring but am not certain that this will be the best way to go.
My thoughts are something along the lines of this
1. have OLTP Mirrored to what I'll call a "Staging" DB. This is NOT to be used for Failover just as a means of accessing read only data for the Reporting DB
2. Have 2 DBs on another box that are flattened (Denormalized) for reporting (ReportA and ReportB)
3. Use SSIS to Populate the Report DBs in alternating sequences every XXX minutes (60 minutes let say)
4. Use Logic to let the Reporting Application Figure out which of the Two reporting DB's is "live". The Currently loading DB will be offline while it's being loaded and we'll alternate between the two (Exact method TBD but this wont be rocket science)
Now, I know this will "Work" but is this the best way to go about this ?
I do NOT want to use SSIS to populate the Reporting system directly from our OLTP system due to contention issues etc.
I got following error when try to expand msdb under SSIS in SSMS, the SSIS I connected to is on clustered server. The windows account used is member of local admin on both nodes in the cluster and sysadmin in sql. I tried with host name that SSIS runs on and virtual sql server name for connection, tried connect from remote client machine and server itself, got same error:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
