Anith Gopal

This is a temporary post that was not deleted. Please delete this manually. (ad460b87-fd6f-4309-ac69-2cec6b803963 – 3bfe001a-32de-4114-a6b4-4005b770f6d7)

static void getFieldRel(Args _args) {     int i = 1;     DictField dictField;     DictRelation DR = new DictRelation(Tablenum(InventTable));     DictTable Dict = new DictTable(Tablenum(InventTable));     DictTable Formref; ;     while(i <= Dict.fieldCnt())     {         if(DR.loadFieldRelation(dict.fieldCnt2Id(i)))         {         Formref = new DictTable(DR.loadFieldRelation(dict.fieldCnt2Id(i)));         info(“Table Name ” + Formref.name());         }         i +=1;     } pause; }

What Immediate_sync means in Transactional Replication José Moreira Neto Microsoft SQL Server Escalation Services sp_addpublication parameter: [ @immediate_sync=] ‘immediate_synchronization’ Immediate_sync has a default of FALSE.  independent_agent must be true for immediate_synchronization to be true . Immediate_sync feature instructs Replication to maintain Snapshot BCP files and distributed transactions in the Distribution database should a new subscriber be created (or reinit) within the Retention period.  By default, this information is purged as soon as existing subscribers receive the transactions.  By keeping the Snapshot and transactions for hours or days, new subscribers can 1) Use old snapshot files, and 2) apply all pending changes since the snapshot.  New Subscribers (or reinit) would not need to have a “fresh” snapshot generated. IF TRUE If true , the synchronization files are created or re-created each time the Snapshot Agent runs.

If you’re not sure what security only crawl is, please see some of my earlier post on this subject. It’s much easier to troubleshoot security only crawls now that we have included Security Updates category within the crawl log in SharePoint 2010! For example, now I can easily spot the incremental crawl at 11:03 AM was a security only crawl:     Just wanted to point this out and provide a heads-up that some of the advanced troubleshooting techniques from the past can now be avoided.   Thanks Colin for supplying the pic

This blog goes live again. Stay tuned for exiting stuff