Viewing 15 posts - 32,821 through 32,835 (of 59,102 total)
I wonder if the new splitter from the "Tally OH!" article would have helped here. I've not done any heavy testing with it against VARCHAR(MAX) but some folks have...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 10:32 pm
Gosh... if it's taking 4 minutes per row to delete because of foreign key updates, there's bound to be some blocking or even deadlocking if people try to access any...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 10:27 pm
I occasionally drop in on other forums but SQLServerCentral.com is my "home". I'd also love to hear about your transition from SQL Server 2000 to 2008 as I'm sure...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 10:10 pm
In that case, lookup the new ranking functions. ROW_NUMBER() has revolutionized the ease with which formally complex queries can now be resolved.n The read up on Common Table...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 9:35 pm
Gosh... I just thought of this... if all these things are properly FK'd (heh... if that doesn't sound like an HR violation, I don't know what does), then what would...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 9:18 pm
fergusoj (8/18/2011)
When I...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 9:08 pm
Ummm... so what do you want done if the following row is add to the rows you posted?
INSERT INTO TestTable(ParentId,ChildId,RecordType) Values('8','20','I')
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 9:05 pm
Are you saying that both the "add" and "delete" tables have exactly the same columns? If so, what in the tables relates "Adds" to "Deletes"?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 8:51 pm
I don't normally recommend it but have you considered changing the FK's to "Cascade on Delete"? It sounds like that would be the easiest and fastest way to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 8:44 pm
Hi Christi,
First, welcome back and congrats on beating your illness.
If you can afford it, I'd buy a copy of the "Developers Edition". I don't know what the latest...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 8:39 pm
As a bit of a side question, why are you trying to do these things from the client instead of within SQL Server itself?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 8:19 pm
If you want a really a good tested answer, the graphic helps a bit but a lot of well meaning folks just won't touch it. Please see the farticle...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 8:15 pm
I absolutely agree with Sean. Please see the following article and pay particular attention to the "Prologue" at the beginning of the article...
http://www.sqlservercentral.com/articles/T-SQL/68378/
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 8:11 pm
I would just pork chop the provider of the spreadsheet and get them to do things right. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 7:59 pm
Just in case you don't know... even though you're doing constant backups on the T-Log file during maintenance, IIRC, the TLog file will still grow to about 1.5 times that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 7:57 pm
Viewing 15 posts - 32,821 through 32,835 (of 59,102 total)