Viewing 15 posts - 586 through 600 (of 1,157 total)
bcdedit.exe /enum ALL lists the BCD information
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 4, 2010 at 10:23 am
To confirm, are you using SQL Server 2000? If yes, the update should not fail.
Please post the error message that you get.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 4, 2010 at 10:02 am
You can try these two options.
1) Find the un-applied transaction log backup on the primary server (the one created after the successful restore) and restore it WITH RECOVERY on the...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 4, 2010 at 4:53 am
You may want to change the Protection Level setting of the package not to include "Userkey" details. More information here
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 4, 2010 at 3:22 am
You can create an "Alert" which will notify the "Operator" when the log file size is >=900 KB. Here is an example.
USE [msdb]
GO
EXEC msdb.dbo.sp_add_alert @name=N'TLogFull',
@enabled=1,
@delay_between_responses=0,
@include_event_description_in=0,
@performance_condition=N'SQLServer:Databases|Log File(s)...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 4, 2010 at 3:13 am
Basically I need to make sure that the LastRun shown in SysServers is really the Expected LastRun, by using the schedule frequency and GetDate(). I was hoping there was a...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 3, 2010 at 11:23 pm
You may find this article useful
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 3, 2010 at 11:02 pm
Setting the "Allow in Process" property of the linked server should fix the issue. Please refer this
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 3, 2010 at 11:00 pm
The first error code indicates that SQL Server is unable to authenticate with the Active Directory. Check if the SPN is created properly. Refer this
Are you able to connect using...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 3, 2010 at 10:53 pm
You may find this script[/url] useful.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 3, 2010 at 10:04 pm
AFAIK, there are no settings in SQL Server to cap the CPU usage
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 3, 2010 at 9:55 pm
Was the SQL Server instance restarted after making these changes?
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 1, 2010 at 1:22 pm
You may find the information in "Solving the Problem" section in this article useful.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 30, 2010 at 11:17 pm
Even with the NULL owner if the application is working fine, then changing it sa should not have any impact
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 30, 2010 at 12:35 pm
To enable PAE mode, you have to add PAE to the boot entry in the BCD file. Open an elevated command prompt. Type BCDEDIT /SET PAE ForceEnable
Refer "More information" section...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 30, 2010 at 9:41 am
Viewing 15 posts - 586 through 600 (of 1,157 total)