Viewing 15 posts - 136 through 150 (of 245 total)
Good point Grant, I assumed you were on a test system and are simply making a copy of the same db.
June 13, 2016 at 4:28 am
If it is in a yellow warning triangle it is the cause of your problem. Remove by how I previously stated.
June 13, 2016 at 4:20 am
Yes, That's fine. Were you getting the warning
June 13, 2016 at 3:50 am
I have had this issue with SQL 2012. Is there a yellow warning on the top of the page above backing up the tail end of the transaction log.
If...
June 13, 2016 at 3:48 am
Sounds more like a political issue rather than technical. It would seem you don't have the authority to govern the server in question.
You need to play a political...
June 10, 2016 at 3:29 am
Looks like it is down to Large page extension being turned on, but not using the trace flag 834.
How to turn of Large Page Extension and is it ok to...
March 18, 2016 at 6:14 am
large page extensions enabled is mentioned in the error log but the trace flag to actually turn it on is not enabled. Anybody? SQL 2005 x64 is the version.
March 18, 2016 at 5:18 am
You can query the default trace for autogrowth activities.
January 6, 2016 at 5:41 am
In terms of recovery, it depends on how much data they are willing to lose in the event of a disaster or if physical corruption is found. If it is...
January 6, 2016 at 4:48 am
This tool doesn't work very well with T-LOGS and point in time recovery. It did however do some sort of recovery, but not to the specific time I requested. It...
January 6, 2016 at 4:46 am
When the query above is executed it fails due to the \ in the string.
If the query is changed to select * from syslogins where name = 'DOMAIN\USER' it works...
December 21, 2015 at 9:19 am
From my understanding the blocks in the reports DB is just the recording of report executions etc. In my experience long running reports cause this issue. Identify all long running...
November 30, 2015 at 9:09 am
Viewing 15 posts - 136 through 150 (of 245 total)