Viewing 15 posts - 31 through 45 (of 107 total)
Hi,
Point in time recovery is only supported in Full recovery model. So NO, Bulk logged recovery model does not support point in time recovery.
http://msdn.microsoft.com/en-IN/library/ms189275.aspx
Hope it helps...!!!
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 23, 2014 at 11:49 pm
Dear Pradeep,
Output of DBCC Loginfo shows the number VLF's you have in your Log File (ldf), From what i can see you have WAY TOO MANY...!!
too many VLF's create substantial...
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 23, 2014 at 5:17 am
Hi,
This seems like an environment issue to me. Sql server is able to make connection but it is not able to sustain them.
Have some network guy look at your network.
Sorry...
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 23, 2014 at 5:07 am
Dear Arooj,
Check out this link.
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 23, 2014 at 1:46 am
Hi Pradeep,
Couple of questions...
What is the size of you Database? (mdf , ldf).
Auto Growth settings for your database (mdf and ldf)
Also share the output of the DBCC Loginfo for...
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 22, 2014 at 10:56 pm
Hi,
There could be a number of reason for High memory utilization. Lets start with the obvious:
Update Stats Task: You are using the default values for Update Stats Task i.e. For...
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 22, 2014 at 10:41 pm
OOps-- Duplicate Answer
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 22, 2014 at 4:54 am
OOps-- Duplicate Answer
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 22, 2014 at 4:53 am
Hi,
Tsql to Disable CDC:
USE <Name of the database>
GO
EXEC sys.sp_cdc_disable_db
GO
You dont have to delete the jobs or manually disable the CDC from tables. Running the above statement would automatically remove all...
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 22, 2014 at 4:53 am
Apparently... "Good things come to those who WAIT" 😀
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 22, 2014 at 4:41 am
How did you resolve it?
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 22, 2014 at 3:21 am
Hi,
I have not worked in HAG as well, Just trying to help.
Read this article once, You will have a fair idea.
http://www.mssqltips.com/sqlservertip/2573/monitor-sql-server-alwayson-availability-groups/
Regards
Shafat Husain
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 22, 2014 at 12:10 am
Dear Arooj,
Do you have any scheduled reports running on the server? Scheduled reports takes up a lot of memory, setting up the WorkingSetMaximum,WorkingSetMinimum value in RsReportServer.config file will help setting...
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 21, 2014 at 11:59 pm
Dear Jude,
The message occurs when you include ApplicationIntent=ReadOnly (AlwaysOn Availability Groups properties) in your connection string. And the server does not recognize the property.
To resolve this issue you will...
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 21, 2014 at 11:50 pm
Hi,
Their could be a wide variety of issues it is not possible to share the resolution for all of them.
Let us try to narrow down our issue first.
Go to...
Regards,
Shafat Husain
🙂
And Your Lord Never Forgets...!! (64:19 -- Quran)
December 21, 2014 at 11:39 pm
Viewing 15 posts - 31 through 45 (of 107 total)