September 18, 2012 at 12:34 pm
SQLRNNR (9/18/2012)
jasona.work (9/18/2012)
Lynn Pettis (9/18/2012)
Sometimes you just want to give a snarky reply, but then you bite your tongue and wait.I know the feeling, some of the people I work with simply stop reading at "error"
Help
And then others get snarky! :w00t:
September 18, 2012 at 12:37 pm
Mr. Celko hasn't posted today and I am biting my tongue from giving snarky replies to others. Just wanted to tell someone to read the readme files.
September 18, 2012 at 12:41 pm
Flat file, 150,000 columns, SQL Server only allows 1,024 columns per table. The flat file needs to be imported into Excel spreadsheets.
I'm not in a postion to help.
September 18, 2012 at 12:53 pm
Lynn Pettis (9/18/2012)
Flat file, 150,000 columns, SQL Server only allows 1,024 columns per table. The flat file needs to be imported into Excel spreadsheets.I'm not in a postion to help.
Maybe they need to hire a consultant.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 18, 2012 at 12:57 pm
SQLRNNR (9/18/2012)
Lynn Pettis (9/18/2012)
Flat file, 150,000 columns, SQL Server only allows 1,024 columns per table. The flat file needs to be imported into Excel spreadsheets.I'm not in a postion to help.
Maybe they need to hire a consultant.
I'm trying to figure out what kind of dataset would have 150,000 columns.
September 18, 2012 at 12:59 pm
Lynn Pettis (9/18/2012)
SQLRNNR (9/18/2012)
Lynn Pettis (9/18/2012)
Flat file, 150,000 columns, SQL Server only allows 1,024 columns per table. The flat file needs to be imported into Excel spreadsheets.I'm not in a postion to help.
Maybe they need to hire a consultant.
I'm trying to figure out what kind of dataset would have 150,000 columns.
probably something with four rows of data, i'd bet. somebody with a unpivot from hell.
Lowell
September 18, 2012 at 1:15 pm
Lowell (9/18/2012)
Lynn Pettis (9/18/2012)
SQLRNNR (9/18/2012)
Lynn Pettis (9/18/2012)
Flat file, 150,000 columns, SQL Server only allows 1,024 columns per table. The flat file needs to be imported into Excel spreadsheets.I'm not in a postion to help.
Maybe they need to hire a consultant.
I'm trying to figure out what kind of dataset would have 150,000 columns.
probably something with four rows of data, i'd bet. somebody with a unpivot from hell.
SETI data, every piece of information gathered at a particular point and moment without separation into separate components/associated constructs.
Okay, probably not true, but I for some reason remember the first build for SETI research being something like that because they had no idea yet what the heck might correllate. I could also have had smoke and sunshine blown in my nether region, it wasn't something I cared a ton about to research on my own.
Does EXCEL handle that many columns? I didn't think it did (well, reasonably anyway) but I've certainly been inaccurate before.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 18, 2012 at 1:18 pm
Lynn Pettis (9/18/2012)
Flat file, 150,000 columns, SQL Server only allows 1,024 columns per table. The flat file needs to be imported into Excel spreadsheets.I'm not in a postion to help.
150,000 columns? WTF?
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
September 18, 2012 at 1:20 pm
Well, at least I did post this on the actual thread!
rhythmk (9/18/2012)
boehnc (9/17/2012)
this is basically the code...this join... left join UserView.vwEncounterDiagnosis d on d.VisitId=a.VisitId...will give me multiple rows per patienti might need help with the diagnosis order/code statements in the where code as well?
select a.EncounterKey,a.DivisionName, a.VisitId,a.MedicalRecordNumber,a.InOutIndicator,a.EDFlag,a.AgeYear,a.PatientGender, a.ChargeTotal,pa.City,pa.State,a.PatientZip
from UserView.vwAccount a
left join UserView.vwPayer p on p.PayerPlanKey = a.PayerPrimaryKey
left join UserView.vwPatient pa on pa.PatientKey=a.PatientKey
left join UserView.vwEncounterDiagnosis d on d.VisitId=a.VisitId
where a.DischargeDate>= '2011-01-01' and a.DischargeDate<='2012-01-01'
and p.PayerClassGroupName in ('blue cross','true blue')
and a.ChargeTotal>0
and ((d.DiagnosisOrder between '1' and '4' and d.DiagnosisCode between '140.0' and '239.99')
or (d.DiagnosisOrder between '1' and '4' and d.DiagnosisCode between 'v10.00' and 'v10.99')
or (d.DiagnosisOrder between '1' and '4' and d.DiagnosisCode between 'v76.0' and 'v76.99')
or (d.DiagnosisOrder between '1' and '4' and d.DiagnosisCode in ('v66.1','v66.2','v67.1','v67.2','v58.42')))
Did you try the pseudo code posted by Kraig ? or try with DISTINCT.
Of course not, we are supposed to perform miracles and provide full answers with nothing from which to work.
(Sorry, but snarky got the best of me!)
September 18, 2012 at 1:21 pm
Evil Kraig F (9/18/2012)
Lowell (9/18/2012)
Lynn Pettis (9/18/2012)
SQLRNNR (9/18/2012)
Lynn Pettis (9/18/2012)
Flat file, 150,000 columns, SQL Server only allows 1,024 columns per table. The flat file needs to be imported into Excel spreadsheets.I'm not in a postion to help.
Maybe they need to hire a consultant.
I'm trying to figure out what kind of dataset would have 150,000 columns.
probably something with four rows of data, i'd bet. somebody with a unpivot from hell.
SETI data, every piece of information gathered at a particular point and moment without separation into separate components/associated constructs.
Okay, probably not true, but I for some reason remember the first build for SETI research being something like that because they had no idea yet what the heck might correllate. I could also have had smoke and sunshine blown in my nether region, it wasn't something I cared a ton about to research on my own.
Does EXCEL handle that many columns? I didn't think it did (well, reasonably anyway) but I've certainly been inaccurate before.
Excel 2007 & up can handle 16,384 columns. An order of magnitude off.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
September 18, 2012 at 1:22 pm
Even if it could handle it, 150,000 columns in an Excel spreadsheet renders it useless for any person trying to look at it.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
September 18, 2012 at 1:24 pm
Lynn Pettis (9/18/2012)
SQLRNNR (9/18/2012)
Lynn Pettis (9/18/2012)
Flat file, 150,000 columns, SQL Server only allows 1,024 columns per table. The flat file needs to be imported into Excel spreadsheets.I'm not in a postion to help.
Maybe they need to hire a consultant.
I'm trying to figure out what kind of dataset would have 150,000 columns.
Or what system would actually be able to open it to read it...That means at a minimum 150,000 characters per line...really????
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
September 18, 2012 at 1:26 pm
Sean Lange (9/18/2012)
Lynn Pettis (9/18/2012)
SQLRNNR (9/18/2012)
Lynn Pettis (9/18/2012)
Flat file, 150,000 columns, SQL Server only allows 1,024 columns per table. The flat file needs to be imported into Excel spreadsheets.I'm not in a postion to help.
Maybe they need to hire a consultant.
I'm trying to figure out what kind of dataset would have 150,000 columns.
Or what system would actually be able to open it to read it...That means at a minimum 150,000 characters per line...really????
XML at its worst. Picture a root - /root structure with no sublevels. Developer Mayhem, Cats and Dogs living in harmony, ARMAGGEDDON!
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 18, 2012 at 1:40 pm
Evil Kraig F (9/18/2012)
Does EXCEL handle that many columns? I didn't think it did (well, reasonably anyway) but I've certainly been inaccurate before.
No, it doesn't. If I understand it correctly EXCEL 2007 and EXCEL 2010 both have a limit of 16,384 columns (but something over a million rows). With EXCEL 2010 you can populate a lot more of those cells in the 64-bit version than in the 32-bit version but that doesn't help if what you want is 150,000 columns.
Tom
September 18, 2012 at 6:15 pm
L' Eomot Inversé (9/18/2012)
Evil Kraig F (9/18/2012)
Does EXCEL handle that many columns? I didn't think it did (well, reasonably anyway) but I've certainly been inaccurate before.No, it doesn't. If I understand it correctly EXCEL 2007 and EXCEL 2010 both have a limit of 16,384 columns (but something over a million rows). With EXCEL 2010 you can populate a lot more of those cells in the 64-bit version than in the 32-bit version but that doesn't help if what you want is 150,000 columns.
You're forgetting that 150,000 columns can be put into 10 worksheets (15K at a time). 😀
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
Viewing 15 posts - 37,891 through 37,905 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply