Viewing 15 posts - 53,746 through 53,760 (of 59,089 total)
Ummmm.... you didn't save a copy of the original report that worked?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 10:27 pm
Not a problem... let us know either way after you try it? Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 10:24 pm
Ray...
If, for some reason, you elect to go with the second form, you may also want to check out the following command as a possible source for your Insert...
EXECUTE...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 10:22 pm
BTW....did u tied second statement....it should fail cause all data will go in first row/ first column only....over 8k bites it will fail
Prakash... did YOU try it? Your...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 10:16 pm
Besides, I believe that the first script will probably blow the doors off the second script.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 10:09 pm
You bet... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 10:04 pm
Whether I agree with bit-masking in SQL Server or not, I enjoyed the article. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 5:01 pm
I'm looking for a way to check for a view or table and if it is there, do nothing, if it is not there create it. Typically there is the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 4:40 pm
Have you actually tried that and gotten it to work?
Besides, if you're gonna take the time to define a table variable, you might just skip that step and...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 6:12 am
Right in the middle of the million rows is a record or two that is mangled. Rejecting the file isn't an option. The import routine needs to be able to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 6:09 am
Two way street here... HOW did you resolve it?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2007 at 5:58 am
I'm a little worried about what will happen when several sources are using it at once while the deletes are running
Good to be worried about these types of things... try...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 7:47 pm
Heh... graduates from "Micromanagement 101", I'm afraid... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 7:11 pm
[font="Courier New"]DECLARE @PostalAddress TABLE (StreetAddressTxt VARCHAR(100))
INSERT INTO @PostalAddress (StreetAddressTxt)
SELECT '123456\78910' UNION ALL
SELECT 'ABCDEFG\HIJKLM'
SELECT * FROM @PostalAddress
UPDATE @PostalAddress
SET StreetAddressTxt = SUBSTRING(...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 7:02 pm
If you have a small file example (emphasis on "small"), attach it to a post and let's take a crack at it... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 6:03 pm
Viewing 15 posts - 53,746 through 53,760 (of 59,089 total)