Viewing 15 posts - 38,446 through 38,460 (of 59,072 total)
Lowell (5/11/2010)
Jeff Moden (5/11/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 2:41 pm
sohairzaki (5/11/2010)
______________
My input file has the following format
<enterprise>
<person>
<sourcedid>
<source>111111</source>
<id>22222</id>
</sourcedid>
<name>
<fn>xxxxxxx</fn>
<n>
<family>yyyyy</family>
<given>zzzzzz</given>
</n>
</name>
<demographics>
<gender>2</gender>
</demographics>
<email>xxxxxx@fffff.edu</email>
<adr>
<street>cccccc</street>
<locality>ccccc</locality>
<region>cccc</region>
<pcode>ccccccc</pcode>
</adr>
<academics>
<academicmajor>gggggg</academicmajor>
<customrole>hhhhhh</customrole>
<customrole>dddddd</customrole>
<customrole>cccccc</customrole>
</academics>
</person>
<person>
…
</person>
</enterprise>
______________________
out put was in the form of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 2:35 pm
kazim.raza (5/11/2010)
I have joined EntityType with FullyQualifiedName. The script would treat it as another extension to levels. My last select remains intact and I...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 2:26 pm
1.6 million random 8 character codes that no one can guess and they're guaranteed to be unique within the set... takes about 25 seconds on my 8 year old desktop...
WITH
cteFirstGen...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 7:41 am
Atif Sheikh (5/11/2010)
This code gave out only 253 duplicates on 16 Mln records.
I don't know if this is exactly what you're after, but you could give it a go.
SELECT TOP...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 7:19 am
john.moreno (5/10/2010)
How does the idea that you can always replace a cursor with something else, fit in with your Connect suggestion, https://connect.microsoft.com/SQLServer/feedback/details/440375?
Maybe it's just me but it seems obvious... it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:53 am
... and aggregate the older data if it's static.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:30 am
sohairzaki (5/10/2010)
Any solution for that
It depends... where does the data come from and why can't it be split up a bit at the source?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:28 am
You bet... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:25 am
Cory E. (5/11/2010)
Jeff Moden (5/10/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:20 am
kazim.raza (5/10/2010)
Duplicates records need to be there as they'll be going...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 9:22 pm
You bet, MC... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 9:04 pm
First... http://www.sqlservercentral.com/articles/Best+Practices/61537/
Second... http://www.sqlservercentral.com/articles/Crosstab/65048/
I have the patience if you have the data and the willingness to help yourself by learning something new. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 8:57 pm
First, it would probably run a bit faster if you didn't select so many unused columns from #Hie.
Second, since your latest query isn't actually using OrgEntityType, my suggestion would be...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 8:47 pm
irobertson (5/10/2010)
You need to pass the results of your query to a variable, then call this using either exec or preferably sp_executesql.
I'm assuming that you'll have more than one...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 8:37 pm
Viewing 15 posts - 38,446 through 38,460 (of 59,072 total)