# ISSUE Update Node Property Key on large data

**URL:** <https://community.neo4j.com/t/issue-update-node-property-key-on-large-data/9868>\
**Category:** Cypher\
**Tags:** cypher\
**Created:** [September 4, 2019, 1:27pm UTC](https://community.neo4j.com/t/issue-update-node-property-key-on-large-data/9868 "2019-09-04T13:27:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pratik.sonawane08](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/pratik.sonawane08/32/6250_2.png) [@pratik.sonawane08](https://community.neo4j.com/u/pratik.sonawane08)\
**Post date:** [September 4, 2019, 1:27pm UTC](https://community.neo4j.com/t/issue-update-node-property-key-on-large-data/9868/1 "2019-09-04T13:27:48Z")

</div>

I have 100gb of data in graphdb,iwant to update porperty key of node.  
I used below cypher its taking to much time and failed.

match (ele:Element) SET ele.NEW\_PORP\_KEY=ele.OLD\_PORP\_KEY REMOVE ele.OLD\_PROP\_KEY return ele;

---

<div class="post-metadata">

**Author:** ![david\_allen](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/david_allen/32/13090_2.png) [@david\_allen](https://community.neo4j.com/u/david_allen)\
**Post date:** [September 4, 2019, 2:17pm UTC](https://community.neo4j.com/t/issue-update-node-property-key-on-large-data/9868/2 "2019-09-04T14:17:46Z")

</div>

If you have a very large amount of data, the transaction you're doing to update that much may be blowing up your available heap space.

One possibility would be to give your server a lot more RAM. The other would be to break down your transaction into batches of smaller numbers, so that each smaller transaction fits into your available memory.

To batch your transactions, you can use apoc.periodic.iterate:

[http://neo4j-contrib.github.io/neo4j-apoc-procedures/3.5/cypher-execution/commit-batching/](http://neo4j-contrib.github.io/neo4j-apoc-procedures/3.5/cypher-execution/commit-batching/)