Viewing 15 posts - 301 through 315 (of 622 total)
that ERD must have taken you hours!
November 6, 2014 at 3:41 am
+1 for Redgate.
I spent a day writing an update script, RGT did a better job in 4 minutes (I had forgotten to refresh a view after the table meta data...
November 6, 2014 at 3:36 am
rather than copy data between tables do one of the following:
either have an additional column in the table with the datestamp to identify the version of the record, OR
Create two...
November 5, 2014 at 7:01 am
With Excel and SSIS it could be a whole host of reasons
Just some of the ones I have come across in the past
Excel 64 bit installed on a 64 bit...
November 5, 2014 at 6:22 am
+1 for Michaels suggestion: Pay to have the list cleaned:-)
SOUNDEX is a good start but is designed to work with Anglo-Saxon pronuciations
You could try pattern matching by removing vowels and...
November 5, 2014 at 6:06 am
and if you drop them both into a sequence container within the For Each Folder loop then you can process them in parallel
November 5, 2014 at 5:36 am
I don't like the join of BOM
you are filtering the join based on properties of RO - these feel to me like they should be in the WHERE clause.
If you...
November 5, 2014 at 5:32 am
Hire a DBA from Freelancer / ODesk (Or ask Gail nicely - she really knows her stuff!)
Front end development, back end development, performance tuning and database security are separate skills...
November 5, 2014 at 5:24 am
Or partition the tables based on date; this gives you the best of both worlds: Performance where queries only need to hit one partition and full dataset (at the expese...
November 5, 2014 at 5:22 am
That solution is fine as long as all the possible status codes are known. If they are not then you would need to use the PIVOT() function along with...
November 5, 2014 at 5:09 am
Rather than use a CASE statement, I would create a new table for the multipliers and then join them to the PackType table. If this is to be used...
November 5, 2014 at 5:01 am
the OP said that the number of <TD>s could be 1..n.
A solution that limits the number of columns could result in sparsely populated columns and/or some of the data elements...
November 5, 2014 at 4:47 am
Please explain how you fixed it so that other users reading this thread havn't wasted their time.
Obiron
November 5, 2014 at 4:35 am
I would take the original query and wrap it in a CTE (common Table Expression) then join the CTE back to the original table. IMHO it makes the code...
November 5, 2014 at 3:38 am
60 seconds in a minute,
3600 seconds in an hour.
You will be looking for the FLOOR() function and the MOD operator
FLOOR(200 / 60) = 3
200 % 60 = 20
200 Seconds...
November 5, 2014 at 3:28 am
Viewing 15 posts - 301 through 315 (of 622 total)
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy