Viewing 15 posts - 6,376 through 6,390 (of 9,253 total)
You're going to need to supply more information.
Have you checked the windows event logs and the cluster.log
October 15, 2011 at 12:58 am
use a server side trace to capture workloads from key points in the business day and then feed this too DTA.
DTA only recommends and all of these should be tested...
October 14, 2011 at 5:55 pm
you will need shared storage that both nodes can access
October 14, 2011 at 10:43 am
use reporting service scripter to extract all objects and then import to the new instance.
October 14, 2011 at 8:53 am
you can create a windows cluster with just one node, then add nodes later on. Important to fresh build server A after the migrations and introduce it into the new...
October 14, 2011 at 8:34 am
Leave server A as a stand alone machine. Form a cluster on Server B and install your clustered instances. Move databases, logins, jobs, etc to the new instances and re...
October 14, 2011 at 5:29 am
ananda.murugesan (10/14/2011)
after that I have successfully installed cluster failover setup in corporate domain controller.
not sure what you mean by this?
ananda.murugesan (10/14/2011)
also add second node.
so you ran sql server setup...
October 14, 2011 at 5:24 am
bailifei2011 (10/14/2011)
October 14, 2011 at 2:50 am
there's probably a way through Powershell to do this but i just havent had time to explore it yet 🙂
October 14, 2011 at 2:41 am
yes execute in a job step as ActiveX VB script, paste the code straight into the job step dialog
October 13, 2011 at 4:05 pm
i use a simple VBScript to prune files
Option Explicit
'Delete all SQL Server backup files more than x days old
Dim oFS, oSQLBackupFol, oFol, oFil
Set oFS = CreateObject("Scripting.FileSystemObject")
Set oSQLBackupFol = oFS.GetFolder("D:\MSSQL\Backup") ...
October 13, 2011 at 8:59 am
currently the trace file is set to reach 5MB and not rollover, is this your desired action
October 13, 2011 at 8:50 am
have you checked the stack dump files to see whats in there
D:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump03xx.txt
October 13, 2011 at 3:47 am
but you should gather all details immediately as logs will not last for ever as you have found out.
Next time you have an issue take a copy of the cluster.log
Do...
October 13, 2011 at 3:17 am
just out of interest, why are you worrying about an event that happened 2 weeks ago. Why did you not tackle this at that time
October 13, 2011 at 3:09 am
Viewing 15 posts - 6,376 through 6,390 (of 9,253 total)