If you are using the JDBC plugin to connect to SqlServer, which is a community
storage plugin, performance might be sub-optimal.
If you are trying to do a table scan, you also have the possibility that the
data being streamed is very large. Your terminal might be the bottleneck for
having to d
You are doing a scan over a file, and there is no predicate/filter in your
query, which means Drill will have to Scan the entire file.
Also Apache Drill's latest released version is 1.8.0, you may want to try
your query on Apache Drill 1.8.0.
On Thu, Sep 1, 2016 at 11:34 AM, wrote:
> Hello
Hello I am using Drill in Window 10 in embedded mode having latest version
(1.7).I am writing one select Query for Sql Server Database.
Query is:-
SELECT CAST(T1.`ID` AS BIGINT) AS `ID`, CAST(T1.`AttributeID` AS BIGINT) AS
`AttributeID`, T1.`String_Value` AS `String_Value`, CAST(T1.`Numeric_V
Hello Sanjiv,
It is a simple select with no filters or conditions and a few casts going
against a database table. Can’t see how it could be possible to improve the
query. Drill will ask for the whole table.Are you accessing the data directly
in Drill through the cmd-line or using the web-ui or
Hello
I am using Drill in Window 10 in embedded mode having latest version
(1.7).
I am writing one select Query for Sql Server Database.
Query is:-
SELECT CAST(T1.`ID` AS BIGINT) AS `ID`, CAST(T1.`AttributeID` AS BIGINT) AS
`AttributeID`, T1.`String_Value` AS `String_Value`, CAST(T1.`Numeric_V
