October 24, 2022 at 1:32 pm
Hi,
does any one whether there is an equivalent function on SQL to the STATA command conindex.
We have a user processing 194 million rows of data via STATA using this command and it would be a whole lot easier if it was at he SQL level.
Any help very welcome..
Thanks,
Eamon
October 25, 2022 at 2:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
October 25, 2022 at 10:23 pm
I've never heard of anything like that in SQL Server.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
October 26, 2022 at 7:03 am
STATA is a different product to SQL Server. From what I can see on the product site, it has its own database manager and stores its data in a proprietary format. It appears to be a statistical analysis product vaguely similar to SQL Analysis Services or SQL Server with R analytics.
The Conindex function provides a particular type of analysis, and appears to produce a variety of industry-recognised outputs depending on the parameters given.
I don't think there is a simple solution to the OP problem. If STATA is taking a long time to do its analysis then the OP needs to get support from STATA.
It may be that STATA has scalability problems and might be slower than alternative products with the amount of data the OP has. SQL Server with R may be an alternative, but other alternatives exist. In any event, benchmarking the performance of alternative products is beyond what this site offers.
If STATA support cannot help the OP and the performance is beyond what the business will tolerate then the OP business managers will have to decide their best way forward.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 27, 2022 at 8:40 am
Hi Ed,
I really appreciate your reply and this somewhat reflects our own experience and knowledge.
The STATA script in question is being amended so that less columns are rows are been import from a csv source file along with a reduced number of rows. We are playing around with these columns and rows in order to find an optimum performance but it's a slow process and I guess will just end up running it in chunks as it's essentially a one-off (hopefully).
My initial post was to put it out there in case anything obvious was available I wasn't aware of.
Thanks,
Eamon
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply