Viewing 15 posts - 48,856 through 48,870 (of 59,102 total)
yogesh.khaire (8/10/2008)
and there is no error in it.
because it is executed when data inserted through Query analyser.
Create Trigger Test on MSArcLong
For Insert,Update
As
Insert...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 9:43 pm
--===== First Data Scenario
TRUNCATE TABLE #MyHead
INSERT INTO #MyHead
(Row_ID,Promo_ID,[Desc])
SELECT '1','1','desc1' UNION ALL
SELECT '2','1','desc2' UNION ALL
SELECT '3','2','desc3' UNION ALL
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 9:41 pm
Beer, Pool, Beer, work on house, Beer, work on garden, Beer, ride motorcycle, Beer, talk with good friends, Beer, fishing, Beer, answer questions on the forum, Beer, more pool, Beer,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 5:55 pm
If it's been 2 years since the move and everything else is moving smartly, then it could be that the code for the reports just wasn't written is a scalable...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 5:49 pm
I believe the question is how to load the Word file into the VARCHAR(MAX) element.
And, yes, I agree... it's probably better to store the name of the file in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 5:37 pm
bakerbill (8/9/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 5:34 pm
Waseem Jaleel (7/21/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 5:28 pm
A CTE is nothing more than a "derived table" just like a subquery in a FROM clause would be. The big differences between itself and a "derived table" is...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 5:26 pm
Heh... spot on, actually. Sergiy is absolutely correct.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 3:51 pm
So change the update code to insert code and change the join to be a WHERE NOT EXISTS or other exclusionary join.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 2:22 pm
I do this same thing with a lot of mixed record files... they're usually fixed width instead of delimited, though. Anyway, I bring the whole file in as a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 2:13 pm
... and, with SQL Server 2000, we end up with this...
DBCC UPDATEUSAGE (0)
SELECT so.Name AS TableName,
si.Rows AS [Rows]
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 1:48 pm
So... hedging a bet against BOL and changing the code to something a bit more conventional, we end up with this...
DBCC UPDATEUSAGE (0)
SELECT so.Name AS TableName,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 1:43 pm
I've found that most of the books are simply a slightly longer, more expensive regurgitation of Books Online. Most of the books I've read don't explain things like the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 11:40 am
It can't happen unless the trigger has code in it telling it to ignore the inserts from WinCC. Recommend you post the trigger code.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 11:10 am
Viewing 15 posts - 48,856 through 48,870 (of 59,102 total)