Viewing 15 posts - 316 through 330 (of 363 total)
I was wanting to do the same thing some time ago... I realized that Table Function parameters can NOT be values from a "Joined" table. I think is is because...
Once you understand the BITs, all the pieces come together ![]()
December 11, 2003 at 11:20 am
There are many ways to filter (WHERE) on dates. The best way for you depends alot on the data, indexes and exactly what you want to query.
Once you understand the BITs, all the pieces come together
December 11, 2003 at 7:13 am
Here is a little example that might help...
-- Show sample time data
Select Time,
DateDiff(HH, '1/1/00', Time) % 24 as TheHours,
DateDiff(n, '1/1/00',...
Once you understand the BITs, all the pieces come together ![]()
December 10, 2003 at 6:24 am
Something like...
CREATE PROCEDURE IntoTest
(@myDate DATETIME = NULL,
@myInt INT = 3,
@myStr VARCHAR(30) = 'hello')
AS
INSERT INTO...
Once you understand the BITs, all the pieces come together ![]()
December 9, 2003 at 7:02 am
Something like...
Exec ('master.dbo.xp_cmdshell ''BCP ' + db_name(db_id()) + '..' + @TBName + ' OUT "' + @OutPutFile + '" -c -S"' + @@Servername + '" -a32768 -T...
Once you understand the BITs, all the pieces come together ![]()
December 8, 2003 at 9:14 am
Thanks Jonathan,
I'll look into deeper on Monday,
but 1 question: Any particular reason you used Char(16) instead of VarChar(16)?
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 4:01 pm
On the Hand Held Computer display, the end user should see "8% Sales Tax" or "6.5% Sales Tax". Customer does not want to see "8.00000% Sales Tax". Some taxes may...
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 2:31 pm
Understood.
Thanks
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 2:21 pm
I'm just curious, but if your SP did a Dynamic SQL (EXEC) with variables all replaced with constants, would your code run in the faster 2 min. time frame?
...
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 2:17 pm
If Object_ID('TempDb..#Temp') is not NULL Drop Table #Temp
Or in some cases...
If Object_ID('TempDb..#Temp') is not NULL Exec ('Drop Table #Temp')
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 11:36 am
It was bugging me, so I dug around a little...
It was VSLive Orlando 2002, Kimberly Trip's "Designing for Performance" session...
The Data Row:
4 Byte Header +
Sum of...
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 11:34 am
Way back, I remember being told that SQL Server will physically reorder the columns, having the fixed length columns first, then the variable length ones. (SQL Server Conf. in Orlando...
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 10:55 am
Thanks, I'll wait a couple/few days, and see if I get responses... if not, then maybe I'll put a link into the other forum.
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 10:47 am
Depending on how long your log data is, you could save the logging data to a local string or output to a text file, then after the rollback, repopulate the...
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 7:59 am
If you just need info on CR or CRLF,
then maybe something like:
SET @NewString = @Str1 + Char(13) + Char(10) + @Str2
Once you understand the BITs, all the pieces come together ![]()
December 5, 2003 at 7:56 am
Viewing 15 posts - 316 through 330 (of 363 total)