[SalesForce] Governor limits : Database.getQueryLocator

Use batch Apex as described e.g. Force.com Batch Apex and Large Data Volumes. This allows work over a large number of SObjects (or other objects) to be executed in batches where each execute method has its own set of governor limits.

Added after nvr's first comment:

You can run a sequence of batch Apex jobs - a chain - by starting a new job in the finish method of the current job (and so on). Typically, as well as implementing the Database.Batchable interface, you will also add the Database.Stateful marker interface so you can preserve state and forward it to the next batchable in the chain. This approach allows the jobs to be run one after another and so avoids hitting the concurrent jobs governor limit.

Do note though that batch jobs are queued and the processing delays and processing rate are at salesforce's discretion: progress may be slower than you expect.

The governor limit will be refreshed for each transaction .

Your Trigger needs to ensure that for 200 record set you are not doing below in a single transaction

10K DML rows ,

Fetching more than 50K records ,

Doing more than 150 DML (This is not possible unless you have DML inside loop or there is a dependent object that triggered and you have chain of triggering events ) ,

Doing more than 100 SOQL statements (Again this can happen if you have query inside FOR loop)

Transaction here may include any other trigger or workflow that triggered due to DML of the triggering object