Viewing 15 posts - 1,021 through 1,035 (of 1,157 total)
Seems to be a problem with MMC. Why not connect to the instance using SSMS?
You can download SSMS from here and install in on the same server.
Hope this helps!
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 22, 2010 at 1:59 pm
Using Windows Authentication only controls the access to the instance. Authentication level will not have any impact Ownership. Having SA as the owner even in this case will not have...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 22, 2010 at 1:54 pm
The "unyeilding thread...." on the SQL instance lead to the failover.
Please refer
http://support.microsoft.com/kb/891268
http://support.microsoft.com/kb/810885
The System Event Log, SQL Server Error Log and the Cluster Log (c:\windows\cluster\cluster.log) should lead you to...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 22, 2010 at 1:37 pm
Try adding an output file to the file system by modifying the job step properties. This should give more detailed information.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 22, 2010 at 6:24 am
Please check the open connections/performance of the Server to which the job points to. Most likely the server is busy when the job fails.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 22, 2010 at 6:17 am
SQL Server is running out of memory. Try restarting the SQL Service. This will resolve the issue.
If this issue reoccurs try increasing the memory_to_reserve by using -G switch as mentioned...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 21, 2010 at 10:04 pm
As mentioned earlier, the backup file format is not usable and the file needs to be deleted. After that try taking the backup with INIT or FORMAT options in the...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 21, 2010 at 10:02 pm
Did any of the configurations change?
Try using the command line OSQL.exe to connect and troubleshoot
osql.exe -S SerververName -E
If that does not help try starting the SQL Server from the...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 21, 2010 at 10:00 pm
You may try some of the options mentioned here
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 21, 2010 at 8:56 pm
You may try increasing the RAM/Page file allocation on the host.
Ref: http://seer.entsupport.symantec.com/docs/198240.htm
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
July 19, 2010 at 5:20 am
You can remove the BUILTIN\Administrators and add the required AD Users/Groups to SQL Server and grant them appropriate rights.
Hope this works !!
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
January 6, 2010 at 9:08 am
This query will give you the desired output
xp_servicecontrol 'querystate', 'SQLServerAgent'
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 18, 2009 at 5:45 am
This query will give you the info
SELECT
ex.UserName, ex.Format, ex.TimeStart, cat.Name, ex.Parameters, CONVERT(nvarchar(10), ex.TimeStart, 101) AS rundate
FROM ExecutionLog AS ex INNER JOIN
Catalog AS cat ON ex.ReportID = cat.ItemID
ORDER BY ex.TimeStart DESC
Ref:...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 13, 2009 at 7:29 am
From the error message it looks like you don't have sufficient privileges on the box where you are trying to install SQL Server.
Quote from Microsoft site
Make sure you have...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 13, 2009 at 7:21 am
Hi,
This query gives you the text used in the Stored Procedures.
select * from sys.syscomments
Filter the above query based on the requirements.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 13, 2009 at 7:15 am
Viewing 15 posts - 1,021 through 1,035 (of 1,157 total)