Viewing 15 posts - 54,211 through 54,225 (of 59,089 total)
Heh... yeah, agreed... I've seen folks destroy production with an UPDATE as well... but it was never with the proper form of update (like Greg's is) which must be "If...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2007 at 8:22 am
Bob Fazio (11/2/2007)
I forgot to add.If you have several queries (which most people do) create an index based upon the more common set of those fields.
What...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2007 at 8:01 am
Thanks for the rowcount and line size... I've got an experiment or two to do... I'll be back...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2007 at 7:37 am
Matt Miller (11/9/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 10:37 pm
I think you're going to find that the problem is a bad date in the Oracle view. Check for any dates there that are outside the range of '17530101'...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 9:23 pm
Not true, Sergiy... and if you look, although it works, UPDATE tablealias isn't even listed in 2k BOL...
Syntax
UPDATE
{
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 5:55 pm
Heh... or, you could just shoot yourself in the head now and save on the anticipation 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 5:23 pm
Heh... no problem there... most people don't even know it exists! 😛
Thanks for the feedback, Bruce.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 5:13 pm
Heh... also notice that the != gets converted to a <> in the query plan output 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 5:07 pm
Matt is correct... even if you're using SSIS, 2000 rows should be processed in the proverbial blink of an eye... even faster if you use Bulk Insert, instead 😉 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 5:03 pm
SQLcommando (11/9/2007)
I'm not using the product "MYSQL" ... I just happened to name my server that. I'm using MSSQL 2000. Sorry for the misleading server name.
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 4:53 pm
Susan S (11/8/2007)
Name of database
Logical file name of .MDF
.Mdf File location drive
Size of the file in MB
Physical file location(full path of .mdf file)
Maxsize
Growth
and...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 4:48 pm
Correct... for more info, lookup "table hints, locking hints" in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 8:25 am
Ummm... rather than struggling with syntax, do you know what Books Online is? Comes free with SQL Server and, although it sometimes takes a bit to find what you're...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 8:22 am
Do you have control over what the custom app does? For example, could you modify the custom app to write to a table in the server?
Otherwise, using BULK INSERT...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 8:20 am
Viewing 15 posts - 54,211 through 54,225 (of 59,089 total)