Viewing 15 posts - 1,816 through 1,830 (of 5,103 total)
Just Besides the "Cancel Executing Query" (stop sign) you can find "Display Estimated Execution Plan"
Hope you can find it ![]()
July 23, 2007 at 2:43 pm
A clustered index *is* the data itself so when you specify the fill factor for it you *ARE* specifying the the *table* fill factor.
Fill factor is a completely optional thing,...
July 23, 2007 at 2:39 pm
There is also the "time" constraint. I have been involved in very complex processes that eventhough a rewrite was the *right* thing it was not the fastest to provide the...
July 23, 2007 at 2:21 pm
just look at the Toolbar buttons in SSMS when you open a "new query" window.
July 23, 2007 at 2:11 pm
Ok back to square one.
If your table is a HEAP you CAN'T specify fill factor at table level.
If your table is CLUSTERED you CAN!!
The Fill factor you specify in how...
July 23, 2007 at 2:08 pm
>>>So, since 2005 allows me to disable unique indexes as you state, I see absolutely no difference between a unique index and a unique key. There must be some...
July 23, 2007 at 2:05 pm
Fill factor refers to PAGE level.
An index is a structure (BTREE) made up of PAGES, A heap is a table with no clustered index made up of PAGES and a...
July 23, 2007 at 2:00 pm
- why would I EVER use a unique key rather than a unique index ?
Not sure what you mean by "unique key" if what you are trying to refer to...
July 23, 2007 at 1:54 pm
don't get me wrong Alrets work fairly well. The reason I said "fairly" is that ususallly you would tie a job that records the alert content somewhere and if the...
July 23, 2007 at 1:41 pm
Use triggers on the Subscriber and join the inserted/deleted tables with the Local_*
tables as needed
July 23, 2007 at 1:35 pm
The other posiblility is that you restored a database comming from a different server and the login that owned the DB on the source server does not exists or is...
July 23, 2007 at 1:31 pm
Well I answered like that because this forum is for "2005".
For 2000 the best you can do is use an Alert!
I guess the the Error Numbers were 18453 and...
July 23, 2007 at 1:21 pm
Never clean metadata is only related to the tables:
MSmerge_contents
MSmerge_tombstone
MSmerge_genhistory
MSmerge_current_partition_mappings
MSmerge_past_partition_mappings
MSmerge_generation_partition_mappings
On the other hand,
MSmerge_history
is cleaned up by the Agent History Clean Up in the Distribution database!...
July 23, 2007 at 1:05 pm
Viewing 15 posts - 1,816 through 1,830 (of 5,103 total)