Viewing 15 posts - 58,771 through 58,785 (of 59,063 total)
High praise from the resident MVP. Thanks, Frank.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2005 at 8:09 pm
I would do as you said... add the extra column with the 2 character country code to the Country table .
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2005 at 12:29 pm
The first 6 characters of date format 100 (mon dd yyyy hh:miAM (or PM)) almost have what you need except for the single blank space. Here's another way to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2005 at 8:11 pm
Hector,
I'm on my way out, just now so I need to be brief but I'll be back.
The usual problem with "comma delimited" files is when an extra comma is added...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2005 at 12:53 pm
Hello Hector,
I don't think you want to use ISQL to do this. BCP will not only determine errors, but any records that don't match the table definition can be automatically...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 18, 2005 at 11:19 pm
When you have 0% to start with and the task is large, an 80 or 90% solution would probably be pretty useful as a start. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2005 at 9:22 pm
There's some pretty good posts here that already work, but I thought I'd throw in my 2 cents... this is what I use and it will find "whatever" in all...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2005 at 6:02 am
If the Recovery Mode is set to Simple, as you say it is, turn on the TRUNCATE LOG ON CHECKPOINT option and delete in smaller chunks. You may have to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2005 at 5:37 am
No, there is not. You can, however, paste a date from Query Analyzer... or you could set the table up to fill the column with GETDATE() as a default for...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2005 at 5:29 am
Thanks, Joe...
>If you absolutely after a few weeks of research cannot find an industry standard, then you have to pick a method to create your own. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2005 at 4:52 pm
Thanks Joe... great explanation about why sequential numbering of records and the use of the IDENTITY property is so bad. I really appreciate the in-depth explanation (especially the history behind...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2005 at 2:11 pm
>And a proper table does not have IDENTITY either since it can never be a key
How do you generate unique customer numbers for new customers if you don't use IDENTITY?
(Edit)...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2005 at 11:07 pm
Great job all around Frank! Congrats on the MVP!
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2005 at 10:53 pm
I believe ISQLW will launch Query Analyzer. I think you meant ISQL and it is fairly well deprecated compared to OSQL. That, not withstanding, if you use OSQL to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2005 at 11:06 pm
Viewing 15 posts - 58,771 through 58,785 (of 59,063 total)