Viewing 15 posts - 58,771 through 58,785 (of 59,067 total)
Angela,
Lookup "Expanding Hierarchies" in "Books Online"... has full explanation and an easily modifiable example script that could be changed to a stored procedure. That's one way to do this.
Another way...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2005 at 7:33 pm
Here's a couple of other ways...
SELECT
LEFT(SalesName,25) As Name
FROM
CommERV
WHERE
ProcessDate = '1/1/05'
AND RevDate = '1/1/05'
AND TIN = '2042416'
SELECT
CAST(SalesName AS VARCHAR(25)) As Name
FROM
CommERV
WHERE
ProcessDate...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2005 at 9:24 pm
If you have a clustered index or a primary key on the table (and you absolutely should have a Primary Key on every table), the data will be displayed in...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2005 at 9:14 pm
Andrew,
You'll need to limit the outputs of the UDF's to make it fit your needs, but here's the whole ball of wax... explanation is in the comments. Includes the test...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2005 at 8:57 pm
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
Viewing 15 posts - 58,771 through 58,785 (of 59,067 total)