You are absolutely correct.

The application pool uses previously spawned connections to run a job which creates a temporary table. When a node has been bounced after the session has been started, it won't let that session create a temp table.

Do you know the reasoning behind this behavior?

Rob.

Hi, Has anyone seen this before? I am trying to create a temporary table as follows: create LOCAL TEMP table recent_stock_items ON COMMIT PRESERVE ROWS AS select distinct s.public_reference, s.advertiser_id, s.stock_item_last_updated, s.stock_item_id,s.revision_number, s.version_number from stock_it...

Hi,

Does anyone have any tools or scripts that can simulate heavy load across a Vertica database/cluster?

I'm trying to set up a training session but want to show people what heavy load looks like.

Cheers

Rob.

Can any user run the database desginer or can it only be the dba superuser account?

Rob.

Hi, I have successfully performed a backup locally on my live cluster by creating a snapshot and subsequent incrementals and this works fine. I now want to back up the same database to a standby cluster in my secondary data centre so I have created this ini file : -----------------------------------...

Thanks Jim,

That's great.

Is there not a way to grant the select option to a role and then grant that role to the users?

How do you create a read only user??

I would like to create a user that can select from a schema but not update or delete it.

Thanks