Viewing 15 posts - 691 through 705 (of 1,584 total)
I'd recommend you place your TEMPDB Log file on a different drive...
Seems like nice hardware for the server regarding CPU's but what about RAM and the disk subsystem? I...
March 15, 2013 at 1:03 pm
Under Choose Data Source, use Microsoft Office 12.0 Access Database Engine OLE DB Provider - "Microsoft Access" is for Office versions lower than 2007
March 14, 2013 at 12:12 pm
Have you tried inserting a tracer token to verify where the delay is actually occurring?
You can also create custom alerts (in your SQL Server Agent >> Alerts) via the SSMS,...
March 13, 2013 at 10:07 am
This happened on a couple of our servers before and while I can't remember the exact issue (it is typically related to autogrowth of the database files(s)), I remember this...
March 13, 2013 at 10:02 am
Per BOL (see if any of these are true for your situation) - maybe this table has an FK relationship to another table? Or you have CDC enabled?
If that...
March 11, 2013 at 6:05 pm
"Dropping transactional replication" - exactly what did you drop? Just the publication? Subscription?
March 11, 2013 at 1:08 pm
As far as I know it's not a bug, it's by design - If any table/article is included in any active publication, then it cannot be truncated. From BOL...
March 11, 2013 at 8:29 am
This should help - http://msdn.microsoft.com/en-us/library/ms188279.aspx
March 8, 2013 at 9:25 am
Thanks for the clarification Gail, I missed the != when I was editing it 🙂
Regarding the DISTINCT, yep, always test. As we all know what works great for a...
March 8, 2013 at 9:06 am
Okay. FYI the reason I asked about the data type for that column is because if it were a numeric data type and you placed quotes around it (effectively...
March 8, 2013 at 8:58 am
To answer your questions:
1. Merge Join - OK. For more info, check out this great article[/url] by Gail Shaw
2. The distinct forces SQL to go through all your results,...
March 8, 2013 at 8:32 am
No you cannot do this. Ref BOL here
The view referenced by table_or_view_name must be updatable and reference exactly one base table in the FROM clause of the view
March 8, 2013 at 8:00 am
Create a duplicate maintenance plan for both the full and diff, then script it out, delete the duplicate plan OR you could just script it out yourself? 😉
March 6, 2013 at 8:59 pm
@ Jeff 😀
I believe you meant this - to the OP, this link will help greatly!
March 6, 2013 at 8:48 pm
Bhuvnesh (3/5/2013)
Key/RID lookup means Non-clustered index is not covering all the participated columns in one query for one particular table. so optimizer choose the heap(RID) or clustered index(Key)...
March 6, 2013 at 6:05 am
Viewing 15 posts - 691 through 705 (of 1,584 total)