Hot answers tagged vertica
There are several ways to get the size of a database, each suited to a slightly different use case. It's important to note that Vertica uses raw and compressed data in different ways, and that you should be conscious of which size you require. For example, licensing is based on the raw data size. Raw Size The raw size is useful for capacity planning or ...
You have two options really: You can create a delimited file with your data, like the following: row1col1data,row1col2data,row1col3data,row1col4data row2col1data,row2col2data,row2col3data,row2col4data row3col1data,row3col2data,row3col3data,row3col4data You can then load that into Vertica using the COPY command and vsql. If you have database superuser ...
With respect to your question about using Vertica during the ETL, it's very rarely necessary (although not unknown) to use a different type of database for the ETL. I would not do that unless you perceive a specific need to do so. The only times I've ever heard of this being done due to interactions with legacy data sources. Although @Kermit works with ...
Try to export the data into csv format, and recreate the table in Vertica using the DDL from Oracle. Check the types as they differ from Oracle to Vertica. Example: assuming the following table structure on Oracle: CREATE TABLE PEOPLE ( ID NUMBER (10), NAME VARCHAR2 (50), ADDRESS VARCHAR2 (250), PRIMARY KEY (ID) ) Assuming a compatible ...
I'm going to assume that you already have the budget to implement some data warehouse solution. Just briefly talking about Vertica; it is a load and read optimized platform, and certainly not designed for OLTP. The piece on staging and processing data would need some more thought. Vertica isn't really designed to have data staged, cleansed, and moved into ...
The driver in the connection string needs to be Vertica, not Vertica ODBC Driver 4.1. EXEC dbo.sp_addlinkedserver @server = N'VERTICA', @srvproduct=N'', -- SQL Server driver @provider=N'MSDASQL', -- Connection string @provstr=N'Driver=Vertica; Servername=ServerName; Port=5433; ...
You can run an INSERT statements from within vsql.
HP Vertica has their community edition for download at https://my.vertica.com/download-community-edition/. If you don't have one already, you will be prompted to create a MyVertica login. If you have problems creating a login, please email me at firstname.lastname@example.org. If you have further issues loading your data, you can tweet at @VerticaHelp and support will ...
Vertica only runs on Linux, you can have a Windows client to acesso Vertica. But don't get scared Linux is not such a scary dragon kkkkk. Vertica installs as 1,2,3 check this link for a full installation article. Vertica uses SQL ANSI so no need for you to learn other languages, it has it's differences but is easy to work with. No need for you to break ...
I'm pretty sure leaf expression means something like "a?b:c". A discrete value from a conditional. But basically the overall message is saying you need to avoid null values. They can't partition on a null.
From the cross-posted site: Vertica only works on Linux, and only some flavors of Linux are supported officially (can't support everything). Vertica's SQL is based on PostgreSQL. 1 Vertica instance runs over multiple nodes acting in parallel. All of them together constitute the cluster.
The namespace refers to a schema (select * from [schema].[tablename]). If you search the "SQL Reference guide" you will find the term used interchangeably, although, schema is used a lot more since its standard SQL.
Vertica includes an ODBC driver for C. Read "Programmer's > Guide Vertica Client Libraries > Programming ODBC Client Applications" This section details the process for configuring the Vertica ODBC driver. It also explains how to use the ODBC API to connect to Vertica in your own client applications.
Only top voted, non community-wiki answers of a minimum length are eligible