Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
admin:features:segments:dropping [2012/03/02 19:40]
doc created
admin:features:segments:dropping [2016/06/28 22:38] (current)
Line 9: Line 9:
 [[admin:​features:​segments:​home|Overview]] | [[admin:​features:​segments:​home|Overview]] |
 [[admin:​features:​segments:​creating|Creating Segments]] | [[admin:​features:​segments:​creating|Creating Segments]] |
-[[admin:​features:​segments:​queries|Querying ​Segments]] | +[[admin:​features:​segments:​querying|Querying Segments]] | 
-[[admin:​features:​segments:​attaching|Attaching ​Segments]] | +**[[admin:​features:​segments:​dropping|Dropping Segments]]**
-**[[admin:​features:​segments:​dropping|Dropping Segments]]** ​+
-[[admin:​features:​segments:​archiving|Archiving Segments]]+
 ---- ----
  
 ==== Dropping Segments ==== ==== Dropping Segments ====
  
-Omnidex Segments can be dropped, resulting in the removal of the object from the connection, and also the removal of the underlying ​file.  Omnidex Segments are dropped using the [[dev:​sql:​statements:​drop_segment:​home|DROP SEGMENT]] statement, as shown in the example below:+Omnidex Segments can be dropped, resulting in the removal of the object from the connection, and also the removal of the underlying ​data.  ​It is not required to drop segments, as they will be automatically dropped when the connection ends.  Dropping segments is required when reusing the same connection name within the same connection. 
 + 
 +Omnidex Segments are dropped using the [[dev:​sql:​statements:​drop_segment:​home|DROP SEGMENT]] statement, as shown in the example below:
  
 <​code>​ <​code>​
-> ; Attach an existing ​segment ​containing the Do Not Call list +drop segment ​                  ​PART_1; 
-> drop segment ​DO_NOT_CALL+Segment PART_1 dropped 
-Segment ​DO_NOT_CALL ​dropped+> drop segment ​                  PART_2; 
 +Segment PART_2 dropped 
 +> drop segment ​                  PART_3
 +Segment ​PART_3 ​dropped
 </​code>​ </​code>​
  
 ====  ==== ====  ====
-**[[admin:​features:​segments:​querying|Prev]]** | +**[[admin:​features:​segments:​querying|Prev]]** ​
-**[[admin:​features:​segments:​dropping|Next]]** +
  
    
 
Back to top
admin/features/segments/dropping.1330717258.txt.gz · Last modified: 2016/06/28 22:38 (external edit)