Reputation
853
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
7 22
Newest
 Enlightened
Impact
~17k people reached

Apr
22
comment How to aggregate table in vertica for last few days, and save the result?
You may be able to use a view. Otherwise, to materialize the result set, consider writing a script which will output the result set to its own table.
Mar
28
awarded  Enlightened
Mar
21
comment Size, audit and rowcount of a table in Vertica
This doesn't answer your own question
Mar
10
comment Truncate a decimal field without rounding in VERTICA
What version of Vertica are you using?
Mar
7
comment Why would Vertica let me start a transaction if I can't roll it back?
I get it now. I agree you shouldn't be able to create a transaction if AUTOCOMMIT is enabled.
Mar
7
comment Why would Vertica let me start a transaction if I can't roll it back?
Bad implementation? If AUTO COMMIT was disabled, then you would need a COMMIT after any DDL.
Feb
16
awarded  Popular Question
Feb
9
awarded  Popular Question
Jan
22
comment Vertica performance on select from view with union
Well, Vertica doesn't have indexes. The only sensible approach is for us to see the actual (anonymized) query.
Jan
14
answered Is Vertica's COPY atomic?
Nov
21
comment Set Default Maximum Rows for Export
@Audrey In the implementations I've seen, compliance was usually fine with being able to audit the requests table. An audit could have just been checking if there was any query run without a LIMIT, for example.
Nov
20
comment Set Default Maximum Rows for Export
Is this an audit/compliance issue?
Nov
20
comment Set Default Maximum Rows for Export
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.
Nov
20
answered Set Default Maximum Rows for Export
Nov
17
comment Vertica INSERT speed highly depends on server load
@woot I wouldn't use COPY for a single row. We'll have to agree to disagree.
Nov
14
answered Vertica INSERT speed highly depends on server load
Oct
13
comment Vertica 6.1: vsql creashes with large resultset
Look at queuetimeout in resource_pools.
Oct
13
comment Vertica 6.1: vsql creashes with large resultset
You're still not giving any information on the environment. Is there a connection timeout on the pool?
Oct
12
comment Vertica 6.1: vsql creashes with large resultset
It would be helpful to know your environment (nodes, specs, network, etc.)
Oct
11
answered Vertica 6.1: vsql creashes with large resultset