Viewing 15 posts - 48,856 through 48,870 (of 59,093 total)
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
rbarryyoung (8/10/2008)
Gimme time to eat lunch, Jeff! 😛 🙂
Heh... hey! I need to know... does brother Darth have to take off the Chevy look-alike to eat?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 11:07 am
Jeffrey Williams (8/10/2008)
Select object_schema_name(object_id) As...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 10:56 am
Also, have 0x100 as the row identifier for both the teacher and the test page does not seem logical... are you sure about that?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 10:48 am
It would be helpful if you posted the CREATE statements for the tables you're trying to target... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 10:46 am
Aye... that's more like it.
The only thing I'd be worried about is... do you need to update usage (DBCC UPDATEUSAGE) as you do in SQL Server 2000 to get accurate...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 10:32 am
Not sure a recursive CTE is needed for this simple update problem... it appears that the prototype ID is simply being updated for each occurance in the temp table...
Sainath,
Thank you...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 10:25 am
Howdy,
Since you're brand new, please take the time to read and follow the suggestions in the link in my signature... it'll help you get very high quality help much faster....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 10:09 am
toniupstny (8/10/2008)
An alternative without cursor is:sp_msforeachtable 'select ''?'', count(*) Rows from ?'Toni
Ummm.... not quite correct, Toni. If you go and look at the code for sp_MSForEachTable, you'll find a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 9:37 am
CAS - Crappy Application Syndrome - I like it a lot, Paul!
Here's what I would do...
... NOTHING...
At least nothing overt for the time being. You've already informed management...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2008 at 9:25 am
Viewing 15 posts - 48,856 through 48,870 (of 59,093 total)