Viewing 15 posts - 58,696 through 58,710 (of 59,039 total)
I found it and I was correct...
They first found memory leaks in the SP_OA procs in SQL Server 6.5 and supposedly fixed it... see the following URL:
http://support.microsoft.com/kb/151601/EN-US
I guess...
July 9, 2005 at 8:13 pm
It sounds like you may need to build a "Calendar Table". Lot's of folks have wriiten about their construction and use. I'd also recommend taking a peek at the following...
July 9, 2005 at 11:27 am
Jon,
What kind of VB functionality are you looking to do?
July 9, 2005 at 9:18 am
IF OBJECT_ID('TempDB..#Results') IS NOT NULL
DROP TABLE #Results
SELECT IDENTITY(INT,1,1) AS RowNum,
...other columns as you need...
INTO #Results
FROM ...your tables and joins...
ORDER BY ...the order you...
July 7, 2005 at 8:18 pm
You CAN get an estimated execution plan when you use temp tables by first executing just the code that makes the temp tables and then doing the execution plan. If...
July 7, 2005 at 7:51 pm
Pretty sharp, Womalley... sometimes ya gotta do what ya gotta do.
July 7, 2005 at 7:45 pm
The use of xp_CmdShell is considered to be a security risk by most DBA's and, I believe, the default is you must have"SA" (not just "dbo" rights to use it. You...
June 25, 2005 at 8:31 am
rschaeferhig,
You were quite right... you didn't change much. In fact, when I built a test Directory and Employees table and inserted the records you showed in a previous...
June 7, 2005 at 10:02 pm
Obviously, the code I posted had to be changed to accomodate your particular requirements. You are correct... something went drastically wrong. If you could post the schema of your personnel...
June 6, 2005 at 9:21 pm
Sure... with examples... I used temp tables for the example so I don't clutter up my hard drive... you don't have to (in fact, I recommend that you don't)...
June 3, 2005 at 6:28 pm
Bull2000,
If you use the concatenate method using the TAB character (CHAR(9) in code) instead of a comma as a delimiter, the output might just cut&paste into Excel with no other...
May 26, 2005 at 7:02 am
Cory...
This works the way you want... leading zeros and mm/dd/yyyy format intact...
DECLARE @Date VARCHAR(30)
SET @Date = '2/3/2005'
SELECT CONVERT(VARCHAR(10),CONVERT(DATETIME,@Date),101)
----------
02/03/2005
(1 row(s) affected)
May 19, 2005 at 9:13 pm
The log file probably grew for a pretty good reason. If you shrink it and it decides to grow again, especially if the growth size is small or is a...
May 17, 2005 at 12:46 am
Try this, instead...
"select boy + REPLACE(STR(age,7,4),' ','') + ' is years old'
May 15, 2005 at 10:40 am
If it truly is a "DateTime" column, it just doesn't matter what format you store it in so long as it is one recognized by SQL. It will have...
May 15, 2005 at 10:18 am
Viewing 15 posts - 58,696 through 58,710 (of 59,039 total)