Viewing 15 posts - 1 through 15 (of 46 total)
Yes I knew that when I posted a reply. However in the spirit of community driven content and the fact that I looked at this thread and found it relevant...
February 7, 2018 at 2:59 pm
We have had the same issue (SQL Server 2012, SP3) and we think it's because of this:
The NOT FOR REPLICATION option is specified by default for foreign...
February 7, 2018 at 8:14 am
Thanks for that. I had seen that earlier but not sure if it applies. We're running 64-bit SQL Server on 64-bit OS. The hotfix itself has not been installed on...
June 22, 2016 at 7:20 am
Much appreciated, this worked for me as well. Wasted 30-40mins looking in various log files.
May 18, 2016 at 2:33 am
So to clarify - advise is to disable built-in "sa" account, setup a replacement for it, call it something not so obvious. I take it that this is done by...
December 18, 2015 at 8:23 am
Ed Wagner (12/18/2015)
but very scary how easy it was to hack the password. It didn't take long at all to crack and computing power certainly isn't going down.
Just out...
December 18, 2015 at 8:18 am
OK, I didn't know that. So start in single user mode with: -m"SQLCMD" and using SQLCMD to connect to the instance from the server itself will do the trick?
December 18, 2015 at 4:25 am
GilaMonster (12/17/2015)
December 18, 2015 at 3:35 am
Thanks for your replies. I had never thought of setting up an alternative to "sa". Now that you mention it, it seems very obvious! Will start making that the default...
December 18, 2015 at 3:32 am
OK, have you tried what's suggested here: https://www.mssqltips.com/sqlservertip/2827/troubleshooting-sql-server-resourcesemaphore-waittype-memory-issues/
December 16, 2015 at 3:27 am
Oh yes, also is your tempdb data files configured as per: https://support.microsoft.com/en-us/kb/2154845
December 15, 2015 at 7:47 am
OK, I'm not sure what the advice is for the resource semaphore wait type but for CXPACKET wait types, have you checked if your "Max Degree of Parallelism" is set...
December 15, 2015 at 7:44 am
Hi,
You may have already done this but have you checked if there are any wait types related to memory pressures on the instance? I'd highly recommend using Brent Ozar's wait...
December 15, 2015 at 5:39 am
GilaMonster (12/11/2015)
A copy-only log backup doesn't truncate the log, but it can't magically read portions of the log already truncated by the more frequent normal log backups.
Yes, my mistake. I...
December 11, 2015 at 1:49 pm
Grant Fritchey (12/11/2015)
December 11, 2015 at 7:58 am
Viewing 15 posts - 1 through 15 (of 46 total)