Viewing 15 posts - 1 through 15 (of 16 total)
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
September 8, 2017 at 12:15 pm
I must be missing something because I tried to execute this SQL and all I received was error 156 incorrect syntax near the keyword 'if'
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
September 7, 2017 at 4:35 pm
stevefromOZ (7/20/2016)
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
July 20, 2016 at 2:16 pm
Steve that makes a lot of sense.
So my original fact table where the columns were:
factID
BillToCustomer
ShipToCustomer
OrderNumber
LineItem
.
.
.
Would become:
factID
BillTo/ShipTo Combination
OrderNumber
LineItem
Your suggestion to handle the ship-to analysis means that the fact table could...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
July 20, 2016 at 1:02 pm
I suspect this is buried, but...
Do any of the correct answers reflect a change in SQL Server 2012, or did the SELECT...INTO statement work the same way under 2008/earlier editions?...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
March 17, 2014 at 3:25 pm
happycat59 (1/15/2014)
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
January 16, 2014 at 11:01 am
tsandeep, I had a client several months back where we needed some standard error handling logic.
My advice, spend a few hours Googling/Binging/whatevering for error-handling in stored procedures.
There are...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
December 13, 2013 at 11:57 am
Well it's nice to see the query is optimized.
Do you get to maintain this, or are you trying to debug something that happened inside of it?
Who did you pi** off...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
August 28, 2013 at 11:06 pm
Hello Thomas -- a couple of comments on your query:
The move record to history section will write the entire contents of your dbo.Alert table, not just the rows upon which...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
August 28, 2013 at 8:41 pm
One additional link that refers to the Microsoft KB article:
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
August 28, 2013 at 8:29 am
R. Brush, I think I understand how the KB article that Erland is citing applies here.
I do agree with you that this specific query doesn't use an ORDER BY clause...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
August 28, 2013 at 8:06 am
Erland Sommarskog (8/26/2013)
R. Brush (8/26/2013)
SELECT @sql = @sql + ' Truncate table ' + QUOTENAME(TABLE_NAME) + '; ' + CHAR(13)
FROM INFORMATION_SCHEMA.TABLES
WHERE TABLE_NAME LIKE @TableNameStartsWith + '%' ...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
August 27, 2013 at 7:19 am
When I ran your SQL on my machine, it produced the results you expected.
However, the database on which I ran the statement had the collation Latin1_General_CI_AS
When I ran your statement...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
August 21, 2013 at 7:32 am
I had a situation similar to yours with batch processes, tables, and triggers attached to the tables.
1) Batch process updated tables
2) Tables had triggers attached
3) Triggers were...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
August 19, 2013 at 12:08 pm
I applaud the effort, except I have to ask why this function would be preferable to the following code:
Jeff Moden's CSV splitter[/url]
I have searched many resources, and it seems like...
_____________________________
Past performance != future results.
All opinions and suggestions are my own, unless they're really good. Then I most likely read them here...
July 29, 2013 at 2:26 pm
Viewing 15 posts - 1 through 15 (of 16 total)