SQLServerCentral / SQL Server 7,2000 / In The Enterprise

Binaries corrupted in one node of Cluster SQL server 2000

haware_amol-811900 — Mon, 29 Apr 2013 05:28:29 GMT

Suppose we have windows server 2003 EE SP1+ SQL server EE SP4 installed in cluster env. Suppose on one node SQL server binaries got corrupted. Then What should happen with cluster [it will failover to other node? or not]? Also how to install SQL server binaries once again on corrupted node. What are the steps to follow? Do we require to install SQL Server on both nodes?

Calling MySQL stored procedures viua a linked server

dJeePe — Wed, 01 Aug 2007 06:47:00 GMT

Does anyone know if it is possible to call MySQL stored procedures via a linked server setup? I've searched around the net and had a play myself but have had no luck so far.

Log shipping a distribution server

Brent McCracken — Thu, 17 Mar 2005 14:35:00 GMT

Hi, I'm trying to get log shipping to work with a distribution server used in transactional replication. Shipping the distribution database is no problem but the issue is in failover getting the distributor to talk to the publisher. The replication monitor won't display anything - distribution or log reader agents. I could only get this all to work by renaming the standby server to that of the primary server, and then restoring both the master and msdb databases. Has anyone done this and know all the steps necessary to get this to work. I can't even find a white paper on the net with the info I want. I'm not sure if it is necessary to do all that I am doing. I also think there could be a problem with a role change - but I haven't tested that yet.Any help appreciated.

This looks like a hard one for many as I've posted many places with no response.cheers,Brent.

Project Plan

Mat Hues — Mon, 07 Feb 2005 13:05:00 GMT

I'm looking for a decent Project Plan (in any format) for moving from SQL Server 2000 to a SQL Server 2000 Clustered environment. I welcome articles that discuss clustering and testing, but I'm really looking for a Project Plan (Tasks, Duration, Resource, etc).

Thanks,

Matthew

SQL 2008 x64 clustering active / active

richard-730095 — Mon, 12 Oct 2009 12:44:31 GMT

Hello all, I've been trying for days now to get my new SQL Server x64 Enterprise cluster online in an active / active configuration.In the end, this is going to an a 5 node cluster with one acting as passive.My question / issue stems from not being able to install a new instance of SQL without it being a named instance. I get the first node online then the second will only install as a named instance..Help?

2005 Cluster unable to add new database

Solon — Mon, 20 Aug 2012 08:54:13 GMT

I have a 2 node windows 2003 cluster with SQL Server 2005 running. The first node is the owner of SQL which has dependencies on the D: (Data), E: (index), F: (Log), H: (TempDB), and T: (Backup) drives. We have one database running with the files distributed across these volumes. We are trying to add another database but when I go to add it it gives me the following error:Cannot use file 'D:\MSSQL.1\MSSQL\Data\test.mdf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.The database that runs on the cluster is located in the same location, so we know that it can see that resource and the SQL cluster group has the drive as a dependency. Any ideas?Image of SQL dependencies: http://imgur.com/s1bf5

SQL is running on only one node in the cluster. Should be running on two nodes in Active\Active configuration.

jyoti.patel — Wed, 09 May 2012 04:35:14 GMT

Hi All,Two sql server 2005 instances are configured by Active\Active cluster configuration and working fine but every day we dont know what happen i saw the email like"SQL is running on only one node in the cluster. Should be running on two nodes in Active\Active configuration."Can any one tell me the resone why both nodes not running on diff nodes or why we have to manually move node to preferred node.

Log Shipping

Eddy!-427737 — Wed, 11 Jul 2007 05:53:00 GMT

Hi,

Does anyone know of a way to recover log shipping with a missing tuf file. long story why the tuf file is missing but it cannot be replaced.

The only way i can see now is by setting up log shipping from scratch again.

thanks in advance

Dave

SQL ADSI Query limitation

Jan-155192 — Mon, 24 Oct 2005 08:14:00 GMT

Hi,

I am trying to query a list of 2500 users out of the AD in SQL Server with the following query:

SELECT employeeId, SAMAccountName, Mail FROM OPENQUERY( ADSI, 'SELECT Mail, SAMAccountName, employeeID FROM 'LDAP://dc=central,dc=mydomain,dc=int''WHERE objectCategory = ''Person''' )

However the result set seems to be limited to 1000 records. I have read that the "Page Size" parameter for AD should be given, but I don't know the exact SQL syntax.

... 'LDAP://dc=central,dc=mydomain,dc=int''WHERE objectCategory = ''Person'';''Page Size''=50' ) doesn't work. Neither does the range parameter.

Somebody suggested that I should partition the query, asking first for all userids starting with A, then B,... but I don't like that suggestion too much and even if I would use it, the Like 'A%' doesn't work.

Does somebody have any experience with this?

Many thanks,

Jan

SQL Server 2008 Clustering Active Passive

D-SQL — Tue, 17 Jan 2012 12:08:29 GMT

We have set up a 2 node cluster running SQl 2008. We need to add another instance to the cluster do we go through the same process as the default instance and just create a new instance for the new DB running SQL 2008 R2?

Windows 2008 Cluster/ SQL Server 2005 Cluster and Active Directory

ganci.mark — Fri, 11 Nov 2011 07:49:50 GMT

Environment:Server 2008 Enterprise x64 SP2SQL SERVER 2005 SP3 Enterprise x64as anyone Windows 2008 and SQL ClusteredSituation:At the end of last summer we completed a DR exercise.The exercise involved physically segregating a portion of our offsite networkand restoring copies of the Infrastructure ie) Active Directory, installing copies of Windows Clusters 2003 and 2008 and SQL Servers 2005 and performing some testing. After testing and while breakiong down this DR environment a task was performed out of step.The network line connecting our live environment and the DR environment was re-established before the DR Active directories were destroyed. Because the DR domain is essentially a copy of our live domain the DR AD controller replicated with our live environment.Trouble ensued. Accounts and objects were over written.Most of the damage was easily reversed in the case of user accounts but Windows 2008 Clustered SQL Servers were a different story.Because the DR servers were copies of the real ones, the physical computer objects, the cluster object and the sql server virtual name objects all were over written with the DR copy.The first eveidence of a problem was that when remoting into the physical node a message stating the node was no longer trusted appeared.Secondly, Upon failing the SQL instance over to the other node(non affected node), the SQL virtual name would not come on line rendering the instance useless. Thirdly upon failure or restart of the cluster service it failed to come online as well rendering all instances even those not in the DR test useless.The problem seemed to be the AD computer objects (SID?) no longer matched what the Machines and clusters were expecting and had no access to them.The Windows 2003 Clusters did not face this problem as they do not seem to use these objects in the same way as Server 2008 clustering. After some time and troubleshooting with Microsoft the only proposed solution was to restore active directory.Our team did not feel comfortable with this option and ended up building a new cluster and clearing out the AD objects where I then reinstalled the 4 SQL instances that were affected.Has any one faced this similar issue before? Is there an easier way to fix this?The AD objects seem like an achilles heal to Windows 2008 Clustering. Windows 2003 did not have this problem.Thanks for any comments.Mark

SQL 2000 SP4 Cluster - Cluster Services overwriting registry parameters

quackhandle1975 — Wed, 02 Sep 2009 03:28:08 GMT

The Setup:Windows Server 2003 Enterprise SP2 7GB RAMSQL Server 2000 SP4 + AWE Hotfix2 Node cluster Active/Passive10 SQL Instances RunningThe Issue:SQL Instance fails to come back on after taking it offline. From event viewer the error states that the ERRORLOG can't be found. When checking in registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\GSQP038A\MSSQLServer\Parameters\SQLArg0 -dR:\Program Files\Microsoft SQL Server\MSSQL$GSQQ009A\data\master.mdfSQLArg1 -eR:\Program Files\Microsoft SQL Server\MSSQL$GSQQ009A\log\ERRORLOGSQLArg2 -lR:\Program Files\Microsoft SQL Server\MSSQL$GSQQ009A\data\mastlog.ldfFrom above the details are obviously incorrec,t the instance name is different (GSQQ009A resides on the same cluster as GSQP038A)and the path is incorrect, drive paths should be O:\ and not R:\When we update the registry with the correct details, the service has to be started by restarting the SQL Service via the services.mmc and not cluster admin.mmc. The SQL Service comes back online however takes longer than it should.Then we bring Service back online via cluster admin and all is fine however the registry parameters have now changed back to incorrect drive/instance so when taken offline again it will not come back online.So the problem lies (we think) with MS Clustering Services overwriting registry keys from another SQL Instance. This occurs on both nodes.Any ideas as to why this is happening?Thanks In AdvanceScott

SQL Server 2005 Cluster upgrade to SP3 with No passive nodes were successfully patched Exit Code Returned: 11009

SirFalcon60 — Fri, 12 Jun 2009 08:04:26 GMT

Attempted to install SP3 on a SQL Server 2005 Cluster, and the attempt failed. Here is my request. I need some help finding offical microsoft documentation on testing that a SQL Cluster is talking back and forth. Can someone point me in the right direction for this type information. Background:I attempted to update a SQL cluster running SQL Server 2005 SP2. I followed all the nice pretty boxes. and when the upgrade attempt was completed the update to SQL Server engine had failed with a error.Exit Code Returned: 11009------- Summary.txtTime: 06/11/2009 17:20:52.558KB Number: KB955706Machine: EGLSQLTEST1OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)Package Language: 1033 (ENU)Package Platform: x86Package SP Level: 3Package Version: 4035Command-line parameters specified:Cluster Installation: YesLog Location on Passive Nodes:(EGLSQLTEST1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix(EARSQLTEST1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix**********************************************************************************Prerequisites Check & StatusSQLSupport: Passed**********************************************************************************Products Detected Language Level Patch Level Platform EditionSetup Support Files ENU 9.3.4035 x86 Database Services (MSSQLSERVER) ENU SP2 2005.090.3077.00 x86 ENTERPRISEIntegration Services ENU SP3 9.00.4035.00 x86 ENTERPRISESQL Server Native Client ENU 9.00.4035.00 x86 Client Components ENU SP3 9.3.4035 x86 ENTERPRISEMSXML 6.0 Parser ENU 6.20.1099.0 x86 SQLXML4 ENU 9.00.4035.00 x86 Backward Compatibility ENU 8.05.2312 x86 Microsoft SQL Server VSS Writer ENU 9.00.4035.00 x86 **********************************************************************************Products Disqualified & ReasonProduct Reason**********************************************************************************Processes Locking FilesProcess Name Feature Type User Name PIDmsftesql Database Services Service 2708resrcmon.exe Database Services Application MTGA\ClusterAdmin 3452**********************************************************************************Product Installation StatusProduct : Setup Support FilesProduct Version (Previous): 4035Product Version (Final) : Status : Not SelectedLog File : Error Description :----------------------------------------------------------------------------------Product : Database Services (MSSQLSERVER)Product Version (Previous): 3077Product Version (Final) : Status : FailureLog File : Error Number : 11009Error Description : No passive nodes were successfully patched----------------------------------------------------------------------------------SummaryNo passive nodes were successfully patchedExit Code Returned: 11009There was no hotfix.log generated..Just need to now how to ensure this does not happen in production at somepoint

Extend Disk Drives for SQL Cluster

soportegdl_mx — Thu, 10 Mar 2011 16:57:04 GMT

I saw some solutions and aswers in your forum and found they very interesting. I was wondering if someone can help me providing another answer. I recently changed my position and I got the responsibility of a Production SQL 2005 Cluster running on Windows 2003. I have two Disk Drives configured on it where bigger DBs reside and they are getting full soon, Those disks are disk resources in the cluster.Since I am not DBA, I am planning to add 2 bigger disks and copy the DBs to these two new disks with the same drive letters and no move SQL settings.I cannot convert those new disks to dynamics neither to GPTs.Since this is production cluster, I got a short nightly maintenance window and I got nervous because I have only 6 hrs to do this and I don't want to loss something. I do not have an environment to test this so I would appreciate any input.This is the plan that I have 1. Stop the App and SQL Services2. Login to the primary node 1 of the cluster3. Take offline the SQL Server, SQL Server Agent and SQL Server Fulltext resources in SQL Group clearing the affect group check box for them. 4. Remove the dependencies from the Resources Disks in SQL Group. 5. Delete Resources Disk 6. On Disk Management Tool change labels and letters for "Old" disks to any7. Initialize new Disks and Create new Partitions 8. Perform Quick Format and assign letters to new disks as the old disks had9. Login to the secondary node 2 of the cluster10. On Disk Management Tool change labels and letters for "Old" disks to any. 11. Login to primary Node 1 of the cluster12. Create Resources Disks and set the dependencies from the Resources in SQL Group 13. Stop antivirus services related14. Copy all content data from old disks to new disks 15. Reenable check box “affect the group” in the SQL resources. 16. Start SQL Engine and services related 17. Take online the resources in SQL Group18. Perform cluster failover and check if it is working properly. Regarding step 10, I don't know if when I delete the resources the "old" disks appears as available in node 2 in order to change the letters and then when I perform the failover node 2 can see the new disks with the new letters as set in node 1.Are those steps fine?Please help me!Thank you.Alex Salazar

Sql Server Logs (no items) showing in Enterprise Manager

jbrewer — Mon, 27 Aug 2007 12:41:00 GMT

When I look in Enterprise Manager under Management, SQL Server Logs, it shows (no items). There is an errorlog, I can read it by running a query, xp_readerrorlog, and it is in startup jobs. Does anyone have any ideas why the logs do not show in EM? I have tried to research this on the internet with no results. I just started monitoring this system so I don't know the history of it. Any Ideas?

Linked Servers

jim.rasmussen — Thu, 29 Jul 2010 14:47:00 GMT

Can anyone please give me more precise information/step-by-step on setting up linked servers and how to configure access between the two. I have been researching and not quite there yet.ThanksJim

Failed job

jim.rasmussen — Thu, 15 Jul 2010 08:18:43 GMT

I am about to lose my mind. I have a job that is failing on this...[SQLSTATE 01000] (Message 18014) ODBC error 208 (42S02) Invalid object name...the table that is referenced is a valid table(yes I doubled checked spelling). What am I missing?TIAJim

Unable to Kill Process :dbcc inputbuffer

lenymendoza — Mon, 14 Jun 2010 21:27:00 GMT

Hi,Trying to kill this process using kill 14 but does notwork. dbcc inputbuffer(14) shows the following.How can I force to kill this process which has run a fewdays ago on NT4 using MSSQL 7.0?I am supposed to restore a database but it prompts me that the database is currently in used. I did check the processes currently running and it show that SPID 14 is runnable. This is the reason why Im trying to Kill the Process.Please advise. Thank you.

SQl2k\2k5 64bit Cluster (A/A) registry issue

adrian.saunders — Mon, 12 Apr 2010 05:28:27 GMT

HiI've got a problem adding new nodes to my established sql2k/2k5 active active cluster.I've added 2 new nodes to the cluster but when I move sql2k to the new node (havent tried 2k5 yet) it fails to start.The event log seems to indicate it can't write to the sql error log and further checking it seems the registry parameters for MSSQL are wrong (using old Arg0-2 settings)As this is a 64 bit system I can't use cluster recovery tool which seems to be designed for this situation.The registry key is Hkey_Local_machine\Software\wow6432node\microsoft\mssqlserver\mssqlserver\parameters\I'm thinking I should copy over the entire registry from a good node, but I'm thinking that the cluster will overwrite the changes?Should I use the CLI checkpoint (SQL Server" /removecheck:) ?Thanks for your thoughts!

My Cluster has removed the sql service pack!

adrian.saunders — Mon, 19 Apr 2010 07:18:28 GMT

Is this possible?I had a cluster SQL2k EE 32bit SP4 on W2k3 64bit. I've moved the sql resources over to a new node and now the sql version is showing as 8.00.194 which is SQL 2000 RTM.WTFrack?

Cluster Res location

adrian.saunders — Tue, 13 Apr 2010 04:16:32 GMT

Hi A bit of a follow up on my previous questionWhen using Cluster.exe with regard to clustering resources what should the registry location when adding and removing checkpoints when I'm clustering SQL2000 32 bit enterprise on Windows2003 64 bit?The standard command;cluster res "SQL Server" /addcheck: "Software\Microsoft\MSSQLServer\MSSQLSERVER"should it becluster res "SQL Server" /addcheck: "Software\WoW6432Node\Microsoft\MSSQLServer\MSSQLSERVER"Does it matter?

SQL Server restarts automatically

karthik -450760 — Tue, 06 Apr 2010 16:18:27 GMT

Hi,One of the servers gets restarted automatically. I found the below error message in error log"The client was unable to reuse a session with SPID XX, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message."I also see lots and lots of login failures after which the server restart. Any idea why this happens? Its a SQL Server 2008 box and has 16 CPU's with 32 GB of RAM. AWE is enabledAny help is appreciated...

C2 Auditing file lcoation

cdfdfireman — Tue, 09 Feb 2010 14:18:46 GMT

Hi all~I have a series of SQL 2000 database that I have had to turn on C2 auditing. Is there a way to define the location of the trace files other than using the default database location?

Is There A Way To List Current Activity, Such As Primary Key?

EdA ROC — Wed, 03 Feb 2010 13:12:13 GMT

There's a bug in our ERP application and until the vendor fixes the code I need to execute some SQL statements and run a utility to fix the data. I periodically throughout the day check and fix.I have written a couple SQL statements which let me know the jobs (job_number) to fix. However, I don't want to 'fix a job' that a user is still active in - they may be editing various parts of a job and therefore be actively making changes and when they finish the data will need fixing. No sense fixing it now and it being corrupted the next moment.I've been looking around Enterprise Manager and can't see anything. The closest I get is looking in the properties of the Lock / Processes. Not time efficient.What I visualize (wish list) is to see what each user is currently accessing by listing the user's ID, Table, Primary Key of the record(s). I can tell by looking at this information what I need to know.For example: If I issued a command in Query Analyzer "SELECT ... FROM orders where customerid = 'xyz';" the listing would show all the orders that were returned:myloginid | ORDERS | 12345myloginid | ORDERS | 21233myloginid | ORDERS | 34322someone else | INVENTORY | 1278312(Hope this makes sense).

DTS deployment

Mahesh Bote — Wed, 03 Feb 2010 07:52:05 GMT

[font="Verdana"]Hi All,I have more than 35 DTS packages which needs to be deploy on one of the new server. Can anybody tell me is there a way, so that I can deploy such packages from source server to destination server in a single run?What I found is, Save As all packages on source server in SQL Server so that I can develop a new package to transfer these packages from source's msdb..sysdtspackages table to destination's msdb..sysdtspackages. I haven't tried it yet, can anybody explain, is this a way to deploye bulk DTS packages from one server to another server in a single run?Thanks in advance,Mahesh[/font]

SQL Server on SAN

Angela But — Mon, 19 Jan 2004 17:53:00 GMT

I have to deploy a database onto our customer's SAN. The customer is having the SAN configured before I get a look at it. My question is, What should I be asking before deploying the database? Anyone with info on SQL Server deployment on SAN's would be most helpful as I haven't done this before and I'm not entirely sure how SAN's function in terms of where I should be placing db files (does it really matter or does the SAN take care of it?). Are there issues with running SQL Server on a SAN?

Thanks,

Angela

Identifying the cause of intermittent network issues

winston Smith — Thu, 07 Jan 2010 14:32:53 GMT

I have an SQL Server that runs an agent job which calls sprocs on another server, and also hits a few file shares.Every so often the job fails due to time out issues.I cannot see anything wrong on either sql servers. I contacted the infrastructure team who say they cannot find any intermittent issue( prob cause its intermitent!).How would i prove this issue exists, and identify the root cause? Has anyone had experience with this?(just noticed, this forum is for sql server 7/2000. im using sql server 2008. Admins, would you mind moving this to a more appropriate forum please? Thank you)

Faulty node in SQL 2000 Clusting?

quackhandle1975 — Tue, 17 Nov 2009 09:18:24 GMT

Here we have numerous (7+) SQL 2000 Enterprise 8.0.2040 instances running on a 2-node cluster (Win2003 Server SP2) that are load balanced when ever possible. This has been working fine, however recently I have found that if a number of SQL instances are running on one of those nodes (say node 2) then I struggle to connect to them (timeout error), via MS in 2000/5/8. Sometimes I do eventually connect however I am not presented with any SQL Server Agent info.I have checked event viewer and not spotted anything untowards, however have spotted this error:[b][sqsrvres] ODBC sqldriverconnect failed[/b][b][sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][ODBC SQL Server Driver]Timeout expired[/b]I have checked the registry settings for all SQL instances in case this is a tcp/ip or named pipes issue but all details are the same. Has anyone experienced this type of issue before? When I move any SQL instance back to say node 1 everything works fine. Very odd.Thanks In Advance,[b][i]qh[/i][/b]:crazy:

Moving SQL Server 2000 instance on new MSCS cluster without uninstalling it ?

paula_ancaI — Thu, 29 Oct 2009 08:59:24 GMT

My boss ask me to move the SQL Server 2000 instance from the server A to a new MSCS cluster (where server A will be one of two nodes) without uninstalling it … I don’t think this is possible but he wants a proof (link/technical articles). Thanks for helping me.Paula (MCTS SQL Srv 2005)

SQL Server resource failing on SQL 2000 cluster

mkoprowski@computerns.com — Mon, 18 May 2009 13:11:10 GMT

My environment: 2 node Active/Active MS Cluster running Windows 2003 Enterprise SP2 and SQL 2000 with SP4I'm currently in a situation where the transaction log on one of my database instances filled up the 20GB log partition and although I see the SQL Server resource is runnning in Cluster Admin I cannnot connect to any database in Enterprise Admin. I tried failing over the node to the second server but no such luck. I also tried manually starting the SQL Server from the command line in single user mode but received an Error: 3449, Severity: 21 State: 1 - An error has occurred that requires SQL Server to shut down so that recovery can be performed on database ID 1.. I was attempting to run SQL Query Analyzer and shrink and truncate the transaction log but again I'm unable to connect to any of the DB's. The database is set to Simple recovery and I have a valid backup I can restore from if necessary.I read that you can drop the db and reattach which will recreate the transaction log with the default size but run out of ideas. I could really use some help on this issue.Below are the events I'm receiving as well as information from the cluster.log and the output when attempting to start the db from command line in single user mode.Events received:Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Query timeout expired.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] OnlineThread: QP is not online..Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: ErrorEvent Source: MSSQL$QDB02Event Category: (3)Event ID: 19019Date: 5/18/2009Time: 1:21:44 PMUser: N/AComputer: CNSLI-SQL-01Description:The description for Event ID ( 19019 ) in Source ( MSSQL$QDB02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure.Data:0000: 4b 4a 00 40 01 00 00 00 KJ.@....0008: 09 00 00 00 56 00 2d 00 ....V.-.0010: 41 00 4d 00 32 00 2d 00 A.M.2.-.0018: 30 00 31 00 00 00 00 00 0.1.....0020: 00 00 .. Event Type: InformationEvent Source: SQLAgent$QDB02Event Category: Service ControlEvent ID: 102Date: 5/18/2009Time: 1:21:47 PMUser: N/AComputer: V-AM2-01Description:SQLServerAgent service successfully stopped.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Cluster.log output:000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB872.tmp, status 0000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] QfsRegSaveKey C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB872.tmp, status 0000008c4.000005c8::2009/05/18-17:29:37.626 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1000008c4.000005c8::2009/05/18-17:29:37.626 INFO [CP] CppWriteCheckpoint checkpointing file C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB872.tmp to file Q:\MSCS\d9fb84ce-53eb-4af8-a79a-7828032d6a55\00000004.CPT000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] QfsCreateDirectory Q:\MSCS\d9fb84ce-53eb-4af8-a79a-7828032d6a55, status 183000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] QfsOpenFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB872.tmp => 3, e2c status 0000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] QfsOpenFile Q:\MSCS\d9fb84ce-53eb-4af8-a79a-7828032d6a55\00000004.CPT => 2, 1384 status 0000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] ReadFile e2c (regf) 32768 12288, (0=>0) 0 status 0000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] WriteFile 1384 (regf) 12288, status 0 (0=>0)000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] ReadFile e2c (regf) 32768 0, (0=>0) 0 status 0000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] QfsFlushBuffers 1384, status 0000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] QfsCloseHandle e2c, status 0000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] QfsCloseHandle 1384, status 0000008c4.000005c8::2009/05/18-17:29:37.626 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB872.tmp, status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [CP] CppRegNotifyThread checkpointing key SOFTWARE\Microsoft\Microsoft SQL Server\QDB05\MSSQLSERVER to id 4 due to timer000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsGetTempFileName C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\, CLS, 47219 => C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB873.tmp, status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB873.tmp, status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsRegSaveKey C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB873.tmp, status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1000008c4.0000037c::2009/05/18-17:29:41.501 INFO [CP] CppWriteCheckpoint checkpointing file C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB873.tmp to file Q:\MSCS\802ca791-4879-446f-b198-9518ea6e5430\00000004.CPT000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsCreateDirectory Q:\MSCS\802ca791-4879-446f-b198-9518ea6e5430, status 183000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsOpenFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB873.tmp => 3, 1384 status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsOpenFile Q:\MSCS\802ca791-4879-446f-b198-9518ea6e5430\00000004.CPT => 2, e2c status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] ReadFile 1384 (regf) 32768 12288, (0=>0) 0 status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] WriteFile e2c (regf) 12288, status 0 (0=>0)000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] ReadFile 1384 (regf) 32768 0, (0=>0) 0 status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsFlushBuffers e2c, status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsCloseHandle 1384, status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsCloseHandle e2c, status 0000008c4.0000037c::2009/05/18-17:29:41.501 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB873.tmp, status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [CP] CppRegNotifyThread checkpointing key Software\Microsoft\Microsoft SQL Server\MSSQL.4\MSSQLSERVER to id 4 due to timer000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsGetTempFileName C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\, CLS, 47220 => C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB874.tmp, status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB874.tmp, status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsRegSaveKey C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB874.tmp, status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1000008c4.000005c8::2009/05/18-17:29:42.517 INFO [CP] CppWriteCheckpoint checkpointing file C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB874.tmp to file Q:\MSCS\18555d04-b14d-4078-9dce-bdda7cbb7dfd\00000004.CPT000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsCreateDirectory Q:\MSCS\18555d04-b14d-4078-9dce-bdda7cbb7dfd, status 183000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsOpenFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB874.tmp => 3, e2c status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsOpenFile Q:\MSCS\18555d04-b14d-4078-9dce-bdda7cbb7dfd\00000004.CPT => 2, 1384 status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] ReadFile e2c (regf) 32768 16384, (0=>0) 0 status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] WriteFile 1384 (regf) 16384, status 0 (0=>0)000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] ReadFile e2c (regf) 32768 0, (0=>0) 0 status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsFlushBuffers 1384, status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsCloseHandle e2c, status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsCloseHandle 1384, status 0000008c4.000005c8::2009/05/18-17:29:42.517 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB874.tmp, status 0000008c4.00002d94::2009/05/18-17:30:05.596 INFO [CP] CppDepositCheckpoint checkpointing data to file Q:\MSCS\f416537d-4a46-43b4-be9f-2e252e99d6ae\00000002.CPT000008c4.00002d94::2009/05/18-17:30:05.596 INFO [Qfs] QfsCreateDirectory Q:\MSCS\f416537d-4a46-43b4-be9f-2e252e99d6ae, status 183000008c4.00002d94::2009/05/18-17:30:05.596 INFO [Qfs] QfsOpenFile Q:\MSCS\f416537d-4a46-43b4-be9f-2e252e99d6ae\00000002.CPT => 2, 1384 status 0000008c4.00002d94::2009/05/18-17:30:05.596 INFO [Qfs] WriteFile 1384 (regf) 3860, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:05.596 INFO [Qfs] WriteFile 1384 (....) 4096, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:05.596 INFO [Qfs] WriteFile 1384 (....) 4096, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:05.596 INFO [Qfs] WriteFile 1384 (....) 236, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:05.596 INFO [Qfs] QfsFlushBuffers 1384, status 0000008c4.00002d94::2009/05/18-17:30:05.596 INFO [Qfs] QfsCloseHandle 1384, status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [CP] CppRegNotifyThread checkpointing key SOFTWARE\Microsoft\Microsoft SQL Server\QDB04\MSSQLSERVER to id 4 due to timer000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsGetTempFileName C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\, CLS, 47221 => C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB875.tmp, status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB875.tmp, status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsRegSaveKey C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB875.tmp, status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1000008c4.0000037c::2009/05/18-17:30:23.253 INFO [CP] CppWriteCheckpoint checkpointing file C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB875.tmp to file Q:\MSCS\dc8246cc-33b4-4654-9aff-22fdc6889bbe\00000004.CPT000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsCreateDirectory Q:\MSCS\dc8246cc-33b4-4654-9aff-22fdc6889bbe, status 183000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsOpenFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB875.tmp => 3, 1384 status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsOpenFile Q:\MSCS\dc8246cc-33b4-4654-9aff-22fdc6889bbe\00000004.CPT => 2, e2c status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] ReadFile 1384 (regf) 32768 12288, (0=>0) 0 status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] WriteFile e2c (regf) 12288, status 0 (0=>0)000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] ReadFile 1384 (regf) 32768 0, (0=>0) 0 status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsFlushBuffers e2c, status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsCloseHandle 1384, status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsCloseHandle e2c, status 0000008c4.0000037c::2009/05/18-17:30:23.253 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB875.tmp, status 0000008c4.00002d94::2009/05/18-17:30:35.675 INFO [CP] CppDepositCheckpoint checkpointing data to file Q:\MSCS\9e4b58d0-8d24-4f6b-a37d-aad9a170fd8c\00000002.CPT000008c4.00002d94::2009/05/18-17:30:35.675 INFO [Qfs] QfsCreateDirectory Q:\MSCS\9e4b58d0-8d24-4f6b-a37d-aad9a170fd8c, status 183000008c4.00002d94::2009/05/18-17:30:35.675 INFO [Qfs] QfsOpenFile Q:\MSCS\9e4b58d0-8d24-4f6b-a37d-aad9a170fd8c\00000002.CPT => 2, e2c status 0000008c4.00002d94::2009/05/18-17:30:35.675 INFO [Qfs] WriteFile e2c (regf) 3860, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:35.675 INFO [Qfs] WriteFile e2c (....) 4096, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:35.675 INFO [Qfs] WriteFile e2c (....) 4096, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:35.675 INFO [Qfs] WriteFile e2c (....) 236, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:35.690 INFO [Qfs] QfsFlushBuffers e2c, status 0000008c4.00002d94::2009/05/18-17:30:35.690 INFO [Qfs] QfsCloseHandle e2c, status 0000008c4.00002d94::2009/05/18-17:30:37.097 INFO [CP] CppDepositCheckpoint checkpointing data to file Q:\MSCS\b74f4b6e-fc94-43b5-a818-a0a106f39a4c\00000002.CPT000008c4.00002d94::2009/05/18-17:30:37.097 INFO [Qfs] QfsCreateDirectory Q:\MSCS\b74f4b6e-fc94-43b5-a818-a0a106f39a4c, status 183000008c4.00002d94::2009/05/18-17:30:37.097 INFO [Qfs] QfsOpenFile Q:\MSCS\b74f4b6e-fc94-43b5-a818-a0a106f39a4c\00000002.CPT => 2, e2c status 0000008c4.00002d94::2009/05/18-17:30:37.097 INFO [Qfs] WriteFile e2c (regf) 3860, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:37.097 INFO [Qfs] WriteFile e2c (....) 4096, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:37.097 INFO [Qfs] WriteFile e2c (....) 4096, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:37.097 INFO [Qfs] WriteFile e2c (vk..) 4096, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:37.097 INFO [Qfs] WriteFile e2c (....) 236, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:30:37.097 INFO [Qfs] QfsFlushBuffers e2c, status 0000008c4.00002d94::2009/05/18-17:30:37.097 INFO [Qfs] QfsCloseHandle e2c, status 0000008c4.000005c8::2009/05/18-17:30:37.628 INFO [CP] CppRegNotifyThread checkpointing key SOFTWARE\Microsoft\Microsoft SQL Server\QDB03\MSSQLSERVER to id 4 due to timer000008c4.000005c8::2009/05/18-17:30:37.628 INFO [Qfs] QfsGetTempFileName C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\, CLS, 47222 => C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB876.tmp, status 0000008c4.000005c8::2009/05/18-17:30:37.628 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB876.tmp, status 0000008c4.000005c8::2009/05/18-17:30:37.628 INFO [Qfs] QfsRegSaveKey C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB876.tmp, status 0000008c4.000005c8::2009/05/18-17:30:37.628 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1000008c4.000005c8::2009/05/18-17:30:37.628 INFO [CP] CppWriteCheckpoint checkpointing file C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB876.tmp to file Q:\MSCS\d9fb84ce-53eb-4af8-a79a-7828032d6a55\00000004.CPT000008c4.000005c8::2009/05/18-17:30:37.628 INFO [Qfs] QfsCreateDirectory Q:\MSCS\d9fb84ce-53eb-4af8-a79a-7828032d6a55, status 183000008c4.000005c8::2009/05/18-17:30:37.628 INFO [Qfs] QfsOpenFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB876.tmp => 3, e2c status 0000008c4.000005c8::2009/05/18-17:30:37.628 INFO [Qfs] QfsOpenFile Q:\MSCS\d9fb84ce-53eb-4af8-a79a-7828032d6a55\00000004.CPT => 2, 1384 status 0000008c4.000005c8::2009/05/18-17:30:37.628 INFO [Qfs] ReadFile e2c (regf) 32768 12288, (0=>0) 0 status 0000008c4.000005c8::2009/05/18-17:30:37.628 INFO [Qfs] WriteFile 1384 (regf) 12288, status 0 (0=>0)000008c4.000005c8::2009/05/18-17:30:37.628 INFO [Qfs] ReadFile e2c (regf) 32768 0, (0=>0) 0 status 0000008c4.000005c8::2009/05/18-17:30:37.644 INFO [Qfs] QfsFlushBuffers 1384, status 0000008c4.000005c8::2009/05/18-17:30:37.644 INFO [Qfs] QfsCloseHandle e2c, status 0000008c4.000005c8::2009/05/18-17:30:37.644 INFO [Qfs] QfsCloseHandle 1384, status 0000008c4.000005c8::2009/05/18-17:30:37.644 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB876.tmp, status 0000008c4.0000037c::2009/05/18-17:30:41.503 INFO [CP] CppRegNotifyThread checkpointing key SOFTWARE\Microsoft\Microsoft SQL Server\QDB05\MSSQLSERVER to id 4 due to timer000008c4.0000037c::2009/05/18-17:30:41.503 INFO [Qfs] QfsGetTempFileName C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\, CLS, 47223 => C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB877.tmp, status 0000008c4.0000037c::2009/05/18-17:30:41.503 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB877.tmp, status 0000008c4.0000037c::2009/05/18-17:30:41.503 INFO [Qfs] QfsRegSaveKey C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB877.tmp, status 0000008c4.0000037c::2009/05/18-17:30:41.503 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1000008c4.0000037c::2009/05/18-17:30:41.503 INFO [CP] CppWriteCheckpoint checkpointing file C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB877.tmp to file Q:\MSCS\802ca791-4879-446f-b198-9518ea6e5430\00000004.CPT000008c4.0000037c::2009/05/18-17:30:41.503 INFO [Qfs] QfsCreateDirectory Q:\MSCS\802ca791-4879-446f-b198-9518ea6e5430, status 183000008c4.0000037c::2009/05/18-17:30:41.503 INFO [Qfs] QfsOpenFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB877.tmp => 3, 1384 status 0000008c4.0000037c::2009/05/18-17:30:41.503 INFO [Qfs] QfsOpenFile Q:\MSCS\802ca791-4879-446f-b198-9518ea6e5430\00000004.CPT => 2, e2c status 0000008c4.0000037c::2009/05/18-17:30:41.503 INFO [Qfs] ReadFile 1384 (regf) 32768 12288, (0=>0) 0 status 0000008c4.0000037c::2009/05/18-17:30:41.503 INFO [Qfs] WriteFile e2c (regf) 12288, status 0 (0=>0)000008c4.0000037c::2009/05/18-17:30:41.503 INFO [Qfs] ReadFile 1384 (regf) 32768 0, (0=>0) 0 status 0000008c4.0000037c::2009/05/18-17:30:41.519 INFO [Qfs] QfsFlushBuffers e2c, status 0000008c4.0000037c::2009/05/18-17:30:41.519 INFO [Qfs] QfsCloseHandle 1384, status 0000008c4.0000037c::2009/05/18-17:30:41.519 INFO [Qfs] QfsCloseHandle e2c, status 0000008c4.0000037c::2009/05/18-17:30:41.519 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB877.tmp, status 0000008c4.000005c8::2009/05/18-17:30:42.519 INFO [CP] CppRegNotifyThread checkpointing key Software\Microsoft\Microsoft SQL Server\MSSQL.4\MSSQLSERVER to id 4 due to timer000008c4.000005c8::2009/05/18-17:30:42.519 INFO [Qfs] QfsGetTempFileName C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\, CLS, 47224 => C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB878.tmp, status 0000008c4.000005c8::2009/05/18-17:30:42.519 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB878.tmp, status 0000008c4.000005c8::2009/05/18-17:30:42.519 INFO [Qfs] QfsRegSaveKey C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB878.tmp, status 0000008c4.000005c8::2009/05/18-17:30:42.519 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1000008c4.000005c8::2009/05/18-17:30:42.519 INFO [CP] CppWriteCheckpoint checkpointing file C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB878.tmp to file Q:\MSCS\18555d04-b14d-4078-9dce-bdda7cbb7dfd\00000004.CPT000008c4.000005c8::2009/05/18-17:30:42.519 INFO [Qfs] QfsCreateDirectory Q:\MSCS\18555d04-b14d-4078-9dce-bdda7cbb7dfd, status 183000008c4.000005c8::2009/05/18-17:30:42.519 INFO [Qfs] QfsOpenFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB878.tmp => 3, e2c status 0000008c4.000005c8::2009/05/18-17:30:42.519 INFO [Qfs] QfsOpenFile Q:\MSCS\18555d04-b14d-4078-9dce-bdda7cbb7dfd\00000004.CPT => 2, 1384 status 0000008c4.000005c8::2009/05/18-17:30:42.519 INFO [Qfs] ReadFile e2c (regf) 32768 16384, (0=>0) 0 status 0000008c4.000005c8::2009/05/18-17:30:42.519 INFO [Qfs] WriteFile 1384 (regf) 16384, status 0 (0=>0)000008c4.000005c8::2009/05/18-17:30:42.519 INFO [Qfs] ReadFile e2c (regf) 32768 0, (0=>0) 0 status 0000008c4.000005c8::2009/05/18-17:30:42.534 INFO [Qfs] QfsFlushBuffers 1384, status 0000008c4.000005c8::2009/05/18-17:30:42.534 INFO [Qfs] QfsCloseHandle e2c, status 0000008c4.000005c8::2009/05/18-17:30:42.534 INFO [Qfs] QfsCloseHandle 1384, status 0000008c4.000005c8::2009/05/18-17:30:42.534 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\SVCCLU~1\LOCALS~1\Temp\CLSB878.tmp, status 0000008c4.00002d94::2009/05/18-17:31:05.597 INFO [CP] CppDepositCheckpoint checkpointing data to file Q:\MSCS\f416537d-4a46-43b4-be9f-2e252e99d6ae\00000002.CPT000008c4.00002d94::2009/05/18-17:31:05.597 INFO [Qfs] QfsCreateDirectory Q:\MSCS\f416537d-4a46-43b4-be9f-2e252e99d6ae, status 183000008c4.00002d94::2009/05/18-17:31:05.597 INFO [Qfs] QfsOpenFile Q:\MSCS\f416537d-4a46-43b4-be9f-2e252e99d6ae\00000002.CPT => 2, 1384 status 0000008c4.00002d94::2009/05/18-17:31:05.597 INFO [Qfs] WriteFile 1384 (regf) 3860, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:31:05.597 INFO [Qfs] WriteFile 1384 (....) 4096, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:31:05.597 INFO [Qfs] WriteFile 1384 (....) 4096, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:31:05.597 INFO [Qfs] WriteFile 1384 (....) 236, status 0 (0=>0)000008c4.00002d94::2009/05/18-17:31:05.613 INFO [Qfs] QfsFlushBuffers 1384, status 0000008c4.00002d94::2009/05/18-17:31:05.613 INFO [Qfs] QfsCloseHandle 1384, status 0000008c4.00000ddc::2009/05/18-17:31:09.894 INFO [Qfs] GetDiskFreeSpaceEx Q:\MSCS\, status 0Output when manually starting the SQL Server from command line in single user mode:single user mode output C:\Program Files\Microsoft SQL Server\MSSQL$QDB02\Binn>sqlservr -m -c -s QDB022009-05-18 12:23:55.86 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)2009-05-18 12:23:55.86 server Copyright (C) 1988-2002 Microsoft Corporation.2009-05-18 12:23:55.86 server All rights reserved.2009-05-18 12:23:55.86 server Server Process ID is 11480.2009-05-18 12:23:55.86 server Logging SQL Server messages in file 'u:\data\MSSQL$QDB02\log\ERRORLOG'.2009-05-18 12:23:55.87 server SQL Server is starting at priority class 'normal'(8 CPUs detected).2009-05-18 12:23:55.95 server SQL Server configured for thread mode processing.2009-05-18 12:23:55.97 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.2009-05-18 12:23:56.09 server Attempting to initialize Distributed Transaction Coordinator.2009-05-18 12:23:57.56 spid3 Warning ******************2009-05-18 12:23:57.56 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.2009-05-18 12:23:57.56 spid3 Starting up database 'master'.2009-05-18 12:23:57.67 spid3 0 transactions rolled back in database 'master' (1).2009-05-18 12:23:57.67 spid3 Recovery is checkpointing database 'master' (1)2009-05-18 12:23:57.70 server Using 'SSNETLIB.DLL' version '8.0.2039'.2009-05-18 12:23:57.70 spid5 Starting up database 'model'.2009-05-18 12:23:57.72 spid3 Server name is 'CNSLI-SQL-01\QDB02'.2009-05-18 12:23:57.72 spid7 Starting up database 'msdb'.2009-05-18 12:23:57.72 spid9 Starting up database 'Northwind'.2009-05-18 12:23:57.72 spid8 Starting up database 'pubs'.2009-05-18 12:23:57.72 spid10 Starting up database 'QDB'.2009-05-18 12:23:57.73 server SQL server listening on 192.168.254.157: 2738.2009-05-18 12:23:57.76 spid5 Clearing tempdb database.2009-05-18 12:23:57.76 server SQL server listening on TCP, Shared Memory, Named Pipes.2009-05-18 12:23:57.78 server SQL Server is ready for client connections2009-05-18 12:23:57.89 spid5 Starting up database 'tempdb'.2009-05-18 12:23:57.92 spid5 Analysis of database 'tempdb' (2) is 100% complete (approximately 0 more seconds)2009-05-18 12:23:58.67 spid10 Analysis of database 'QDB' (7) is 2% complete (approximately 17 more seconds)2009-05-18 12:24:01.72 spid10 Analysis of database 'QDB' (7) is 30% complete(approximately 7 more seconds)2009-05-18 12:24:07.56 spid1 Warning: unable to allocate 'min server memory' of 6144MB.2009-05-18 12:24:07.87 spid10 Analysis of database 'QDB' (7) is 74% complete(approximately 3 more seconds)2009-05-18 12:24:11.59 spid10 Analysis of database 'QDB' (7) is 100% complete (approximately 0 more seconds)2009-05-18 12:24:11.78 spid10 Recovery of database 'QDB' (7) is 0% complete (approximately 6537 more seconds) (Phase 2 of 3).2009-05-18 12:24:31.79 spid10 Recovery of database 'QDB' (7) is 0% complete (approximately 5774 more seconds) (Phase 2 of 3).2009-05-18 12:24:59.64 spid10 Recovery of database 'QDB' (7) is 0% complete (approximately 5760 more seconds) (Phase 2 of 3).2009-05-18 12:25:14.77 spid10 Recovery of database 'QDB' (7) is 1% complete (approximately 5745 more seconds) (Phase 2 of 3).2009-05-18 12:25:26.33 spid10 ForwardLogBlockReadAheadAsync: Operating system error 21(The device is not ready.) encountered.2009-05-18 12:25:26.53 spid10 Error: 3313, Severity: 21, State: 22009-05-18 12:25:26.53 spid10 Error while redoing logged operation in database 'QDB'. Error at log record ID (428542:311395:1)..2009-05-18 12:25:26.55 spid2 LogWriter: Operating system error 21(The device is not ready.) encountered.2009-05-18 12:25:26.55 spid2 Write error during log flush. Shutting down server2009-05-18 12:25:26.55 spid10 Error: 3449, Severity: 21, State: 12009-05-18 12:25:26.55 spid10 An error has occurred that requires SQL Serverto shut down so that recovery can be performed on database ID 1..

SQL2000 (32bit) on Win2k3(64bit) Cluster problem

adrian.saunders — Wed, 15 Jul 2009 03:42:26 GMT

HelloI'm trying to install SQL2k (32bit) on a windows 2003 SP2 (x86) 64 bit cluster.I've created the MDAC cluster and I'm using the install account.Cluster is working normally; I can move the groups between 2 nodes okay.Currently I'm trying just to install on a single node, I've copied the SQL cd to a local file directory (and I've tried from a remote share with a drive mapping and without a drive mapping)The problem from the logs seems to be installing MSSEARCH (searchstp.exe) from the SQLSP.log10:24:17 End Action: Locked Connectivity Files Check10:24:17 Setup is installing Microsoft Data Access Components (MDAC) ...10:24:17 C:\software\SQL2000\ee_32bit\x86\Other\sqlredis.exe /q:a10:24:32 ExitCode: 010:24:32 InstallMSSearch instance: MSSQLSERVER10:24:32 Software\Microsoft\Search\Install:Version : 9.107.551210:24:32 MSSearch 2.0 or greater version check returned 110:24:32 Setup is installing the Microsoft Full-Text Search Engine ...10:24:32 "C:\software\SQL2000\ee_32bit\x86\FullText\MSSearch\Search\SearchStp.exe" /s /a:SQLServerThe install then sits at the 'performing operations on the cluster nodes' for 30 mins before failing with a ' couldn't perform operations on the cluster nodes' and checking the logs I find a 'timeout error on remote node'Oh I'm also using RDP with the admin settingAny ideas?

Lotus Notes connectivity using OLEDB

paul_whitehead — Tue, 14 Jul 2009 06:21:34 GMT

I have successfully managed to use the OLEDB feature of Lotus Notes LC LSX to retrieve data from a SQL2000 database. However I now have a requirement to run some stored procedures, some of which have input parameter sets, some no parameters. In each case there is no requirement for records to be retrieved. I did write a script to run the SPs using ODBC, but most of my client PCs don't require ODBC, and there is no plan to install it.After much Googling, I can't seem to find any useful information or example scripts. I located Sybase and DB2 examples and attempted to modify them for SQL to no avail. Does anyone have any experience with this to point me in the right direction?Any help would be very much appreciated.ThanksPaul

enterprisemanager not displaying server and databases in sql server 2000 cluster

mvssrikanth1 — Thu, 02 Jul 2009 08:58:20 GMT

Hi!I have installed sql server 2000 cluster database (sql)on windows 2003 server.The two nodes are server1 and server 2.After the installation enterprise manager was working fine.but recently enterprise manager is not displaying server and databases on both nodes.Query analyser on server 1 is working fine.But the database is working fine.i)The contents of C:\Documents and Settings\Administrator\Application Data\Microsoft\MMC of server1: No files found.ii)The contents of C:\Documents and Settings\Administrator\Application Data\Microsoft\MMC of server2:admgmtcomexpdnsmgmtdomaindsadssitegpmcsecpolsql server enterprise manageriii)components in Add/Remove programs:server 1:network DTC access is not enabled Application server console is not enabled.Server 2:network DTC access is enabled in server 2.Application server console is enabled.iv)SQL Server service is on in your Windows task bar, the light is not green and it is blank on both server 1and server 2.The message is not connected to //sql.I tried to add enterprise manager snap-in through MMC command on server 1 i.e(I made the sqlserver on server 1 offline,renaming the sql server enterprise manager.msc,run MMC at command prompt,added sql server enterprise manager snap-in).But no result.I enabled the open console tree to the last active node in the advanced section (Open enterprise manager,tools->options->advanced).but no result.The error log in E:\Program Files\Microsoft SQL Server\MSSQL\LOG has the following contents.i) Sql server is starting at priority normalii) Attempting to initialise distributed transaction coordinatorii) Failed to obtain transaction dispensor Interfaceiv) starting database 'Master'.........v) using xpstar.dll to execute extended stored procedure SP_MSget versionerror:15457,severity:0,state:1Configuration option'show advanced options changed from 1 to 1Run the reconfigure statement to install using Xplog70.dll version 2000.80.194 to execute stored procedures xp_msversion.How to get Enterprise manager displaying databases with server?Can I uninstall Enterprise manager and install it without affecting the production database.Thanks for the help in advance.Regards,Srikanth MVS

sql server 2005 failover

kenweed06 — Tue, 14 Apr 2009 08:43:26 GMT

Hi guys, I have an issue here which you can probably assist me with.Here's the scenario, I support an application that is written in vb and connects tosql server database. It usually reads from a config file the server name and/or the ip addressof the server where the db is hosted. Based on this the only sql server 2005 failover option thatI have used is sql server clustering and it works perfectly since I have the virtual server IP address/name to specify at the config file coupled with the many other advantages of clustering.However not everyone can afford to buy storage facilities. So i'd like some advice on the otherfailover options as im not well conversant with mirroring and logshipping.Specifically i'd want to know with mirroring and logshippin how redirection takes place from the primary server to the secondary server and in my case how does it happen without having to change the servername specified in the config file of each client connecting to the server.

Possibility to add database on a shared drive which is not dependency of SQL Server resource

b.ozga — Mon, 08 Jun 2009 00:56:13 GMT

Hi guys,Yesterday, I detached one of my relevant databases to perform some disk related task. When I tried to attach it again I got well known message[quote]Cannot use file 'd:\xxxx_data.mdf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used.[/quote]Server has been running for couple of months without stop and nobody has been aware that d: drive is not in SQL Server resource dependency.Do you know a way to attach\create database on a disk which is not SQL Server dependency but it is in a cluster group? Any help appreciated. Cheers,Bartek

Insufficient Buffer Space issues

sandy.chaudhary — Fri, 01 May 2009 08:31:07 GMT

We have a sql server 2000 SP4 install on Windows 2003. There are about 20 databases in this instance and at peak we see about 130 connections from various ERP/Analytics applications.SQl server is installed on box 1 and there are 3 other server boxes from where connections originate to the sql server databases.Of late on the application we have been seeing the following error. Some of the application uses a database driver from INET.com.inet.tds.at: [TDS Driver]java.net.SocketException: recv failed: Insufficient buffer space at com.inet.tds.aq.a(Lcom.inet.tds.k;Ljava.lang.Throwable;)Ljava.sql.SQLException;(Unknown Source) at com.inet.tds.TdsDriver.connect(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(Unknown Source) [/b]at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;Ljava.lang.ClassLoader;)Ljava.sql.Connection;(Unknown Source) We have monitored the incoming connections to the database and found that beyond 120 connections the application throw the above error.also, netstat results show about 4000 packets coming to the database server box.At this point, we made changes as per the following linkhttp://support.microsoft.com/default.aspx?scid=kb;EN-US;196271i.e MaxUserPort was made to max.i verified that the number of connections to sql server instance is 32667..However, with the above changes and the verification, the error still continues...Looking forward for the gurus to respond...thankssandeep

Tempdb on a nonclustered resource in the SAN

Jan-1080019 — Fri, 08 May 2009 02:40:48 GMT

Hi,We are running a database on a stretched cluster with a SAN. The tempdb is on a clustered disk and is replicated to the other site. This seems completely wasted to me, since when after failover the database restarts on the other site and recreates the tempdb.When I search this forum, I find that it wouldn't be possible and that someone had a message like this:Only formatted files on which the cluster resource of the server has a dependency can be used. Server: Msg 5184, Level 16, State 1, Line 2 And of course a dependency is only possible on clustered resources.Is there somebody who has found a solution for this? We are using SQL 2005 on Windows 2008.thanks,Jan

PF Usage Issue

Jus — Thu, 26 Mar 2009 15:12:57 GMT

Hello experts..Though am not sure if this is the right forum for my issue, still posting..I have an issue with my Production SQL server box. I have windows 2003 server on which SQL server 2000 is installed.The box having 8 GB RAM.From past few days, it has been observed that, PF usage is occupying 6.7 GB where as when i checked under processes tab in Task manager, the total amount of Mem usage is not exceeding 2 GB. but in Task manager, under Performance tab, PF usage is showing 6.7 GB used.Where is rest memory gone...?When i checked even viewer, am seeing some errors with event id 17052 Error "Communication link failure" ....does it cause any mem issues?Please help me in fixing this issue.--Raj

SQL Server Cluster, how to add local server account to virtual server?

hrhenja — Thu, 07 May 2009 15:14:42 GMT

I recently set up 2 Clustered Nodes (SQL Server 2005) on 2 Windows 2008 boxes, and the cluster works fine. Prior to me clustering the 2 SQL Servers, the single SQL server that was in place had one local user account which we must keep locally on the server ... As I expected, I created the local user on each node in the cluster and when I try to add it to the Virtual Server logins, I get the error below ... Is there any work around to add a Windows local user to a cluster without using a domain account? TITLE: Microsoft SQL Server Management Studio------------------------------Create failed for Login '********'. (Microsoft.SqlServer.Smo)------------------------------ADDITIONAL INFORMATION:An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)------------------------------Windows NT user or group '********' not found. Check the name again. (Microsoft SQL Server, Error: 15401)

I need objective research benchmarking SQL Server performance on virtualization platforms

*ODB* - Brooklyn Zoo — Mon, 11 May 2009 08:07:38 GMT

Problem: IT management is pointing to vendor whitepapers to justify SQL Server performance on virtual platforms. I am looking for Independent research from reputable IT sources benchmarking SQL Server performance to counter this. SQL Versions: 2k5, 2k8Scenarios: OLTP and DWVirtualization Platforms: VMware, HyperVResearch Providers: Gartner, IDC, Meta or others; Not EMC, VMW, MSFT, etc.I also do not want any report "commissioned" by a hardware provider (Dell or HP). "commissioned" means "bought" to me. Again, Objective third party research is the goal, not sales BS masqueraded as independent research. thank you.