• r

    radekm

    1 month ago
    Hi. I have a question how to reliably store records in QuestDB so I don't lose any records. Currently I'm using MS SQL but for performance reasons I would like to migrate to QuestDB. The thing is that MS SQL has transactions so my program can easily know when records were stored (it's after transaction successfully committed). After I store records I remove them from original source and continue with the next batch. But in QuestDB how can I determine that data were persisted and I can continue with the next batch?
    r
    h
    +1
    4 replies
    Copy to Clipboard
  • Pei

    Pei

    1 month ago
    @Paddy D welcome! 👋
  • h

    Holger

    1 month ago
    Has anyone a better idea to pull in the unique dates of the time stamp column: select distinct to_str(timestamp, 'yyyy-MM-dd') value from 'table';
    h
    Bolek Ziobrowski
    +1
    6 replies
    Copy to Clipboard
  • Pei

    Pei

    1 month ago
    Hi @Grant Wittenberg welcome!
    Pei
    1 replies
    Copy to Clipboard
  • Andy

    Andy

    1 month ago
    does qdb support rank() function ? like select RANK() OVER(order by [UserId]) as rank,* from [Order]
    Andy
    Bolek Ziobrowski
    +2
    6 replies
    Copy to Clipboard
  • Raul Perez

    Raul Perez

    1 month ago
    Hi! anyone knows if is it possible to have multiple databases under the same instance? I can't find anything in the documentation...
    Raul Perez
    Nicolas Hourcard
    2 replies
    Copy to Clipboard
  • Pei

    Pei

    1 month ago
    Hi @Bo Nordgren @William Hoang welcome! 👋
  • p

    Paddy D

    1 month ago
    Hello, I currently have an application that is sending metrics to my Questdb instance using the LineTcpSender, and everything is working as expected. When attempting to replace this with a LineUdpSender instead, it does not seem to be working. I see nothing in the quest logs to suggest it is receiving any data. I am using the Helm chart found here for my deployed of Questdb. In the container spec generated from this chart, I noticed the protocol defined for the influxdb port 9009 is specified as TCP, but there is nothing for UDP ( they both use the same port ).
    spec:
    containers:
    - image: questdb/questdb:6.4.2
    imagePullPolicy: IfNotPresent
    name: questdb
    ports:
    - containerPort: 9000
    name: http
    protocol: TCP
    - containerPort: 8812
    name: postgresql
    protocol: TCP
    - containerPort: 9009
    name: influxdb
    protocol: TCP
    I am wondering if this would be the cause of the issue I am seeing, and if anyone else has come across this problem? And if so, is there any way to get around this? The protocol appears to be hard coded in the template
    p
    Nicolas Hourcard
    +1
    11 replies
    Copy to Clipboard