RasgoQL VS tigertoolbox

I built an open source package to bridge the gap between python and dbt, would love your feedback if you have a chance to check it out: https://github.com/rasgointelligence/RasgoQL

I’ve actually solved a similar problem several times in a variety of settings. I’ve had success with boosted trees and feature engineering on the sensor readings over time. I treat each reading as an observation and set the target to be the value I want to forecast (e.g. one hour ahead, the sum over the next day, the value at the same time the next day). There was a recent paper that compared boosted trees to deep learning techniques and found the boosted trees performed really well. Next, I perform feature engineering to aggregate the data up to the current time. These features will include the current value, lagged values over multiple observations for that sensor, more complicated features from moving statistics over different time scales, etc. I actually wrote a blog about creating these features using the open-source package RasgoQL and have similar types of features shared in the open-source repository here. I have also had success creating these sorts of historical features using the tsfresh package. Finally, when evaluating the forecast, use a time based split so earlier data is used to train the model and later data to evaluate the model.

I created RasgoQL to give anyone a pandas-like syntax that you can use to quickly generate hundreds of lines of SQL that will run directly in your Snowflake or BigQuery data warehouse (with more data warehouse support coming soon). The best part? In one line of code, you can export this SQL to your dbt project so that it can run in production alongside other data pipelines.

You can check it out here: https://github.com/rasgointelligence/RasgoQL

They have a sort of version - check in the Tiger Team toolbox on GitHub ...

Thank you for taking the time to reply! Hmm, I just ran https://github.com/microsoft/tigertoolbox/blob/master/tls1.2/CheckClientUpdates.ps1 script on both servers, and I did get: Microsoft SQL Server 2012 Native Client with version 11.4.7507.2 supports TLS 1.2 Microsoft ODBC Driver 17 for SQL Server with version 17.10.3.1 supports TLS 1.2 So, it does appear that TLS 1.2 should be supported by both servers.

Managing security can easily be done with T-SQL and there are plenty of utility scripts out there to help you out - e.g., https://github.com/microsoft/tigertoolbox/tree/master/Securables