I am more of a Vertica database user than admin, so I'm not even sure if what I'm asking is absurd, but here goes nothing...

  1. Could I, as an admin, put default restrictions on the number of rows that can be exported per export query? I would like to make sure most users can only export a certain number of rows at a time, and that they cannot change the setting which prevents a massive export. I realize there are probably be ways around this restriction
  2. Would there also be a way to catch a user pulling small amounts of data incrementally from the same data set?

An answer to question (1) would suffice, but I would appreciate any input on question (2), as well.


You can create views using LIMIT and give those view names to the end users. If you're using a development tool such as DBVisualizer, you can set the number of records to limit.

As always, query labels allow for easy tracking of any requests.

| improve this answer | |
  • I think the views option would not work in my particular situation. The labels idea is intriguing, but I'm not sure that would work. A few questions on that matter. What I would want, if some way to catch ANY attempt at an export query. So, if I could continuously check what appears to be called QUERY_PROFILES, and trigger a script that checks for the presence of a sufficient LIMIT clause as a determination for whether or not to manually kill the query. – Audrey Nov 20 '15 at 18:29
  • Upon further reading, it seems like a trigger might be the key with other databases, but is not an option with Vertica. – Audrey Nov 20 '15 at 18:31
  • Your use case doesn't make much sense to me. Vertica will still have to do the same processing to run the query. Your LIMIT will come at the end. – Kermit Nov 20 '15 at 20:26
  • Is this an audit/compliance issue? – Kermit Nov 20 '15 at 21:56
  • It's a legal compliance issue. We can't allow people to take out more than certain number of rows at a time. In theory, there are many ways around this... like pulling out all the records in a table slowly, over time etc. However, just to be on the safe side, we have to cover the more obvious attempts to take excessive amounts of personal information from the database. – Audrey Nov 21 '15 at 21:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.