Viewing 15 posts - 57,406 through 57,420 (of 59,067 total)
That's strange... I'm thinking we have a service pack problem here... I'll bet you guys are running SP4 on SQL Server 2000... I'm running SP3A... and here's what I get...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2006 at 6:53 am
Mark,
Thanks for posting the table schema...
Sorry to plague you with questions but trying to do this in a very simple fashion... I see that the TimeGenerated column is a DateTime...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2006 at 6:15 am
I'm just about out of tricks on the Text columns, Charlotte... I'm still playing with it but haven't been able to come up with anything, yet.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2006 at 5:53 am
Kind of where I was going with this but it's important, I think, to include the date columns in that so that you endup with a nice, whole datetime as...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 8:02 pm
Nope... that works too... I just thought I'd show another way.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 8:00 pm
I'm thinking that someone has done an update in a transaction with no commit from Query Analyzer... locks up the world sometimes. Use sp_lock and sp_who2 to find out who's...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 6:06 pm
Concur with THAT!! ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 5:52 pm
--===== Return user created tables only. Ignores dtProperties, as well
SELECT Name
FROM dbo.SysObjects
WHERE OBJECTPROPERTY(OBJECT_ID(Name),'IsMSShipped')=0
AND XType = 'U'
'nuff said... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 5:50 pm
Oh no, no, no.... this is a lot easier than that... but I need you to post the CREATE statement for the table...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 5:32 pm
Heh-heh... My first inclination was to say "don't use text columns"
I won't even allow them into code at work because of...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 7:43 am
Thanks Nick... I'm still curious though... why do you need to change the datatype of a column in a view?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 7:38 am
I was leaning towards the previously suggested idea of some sort of permanent table for this and then I started thinking "spid" and then David stole my thunder 
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 7:36 am
Yeah.. that's what I was kinda getting at... if it's all SELECTs, what's the problem ![]()
Also, what I've found is that a lot of...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 7:29 am
Yep... I knew that, Mark
I just didn't think that Shine recognized that because he said your code change didn't work and...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 7:25 am
Yep... First, I changed the function to capture the data type... again, you'll need to change the name of the function...
CREATE FUNCTION dbo.fnColumnsUpdated
(@TableName SYSNAME, @BinaryColNums VARBINARY(128))
RETURNS...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2006 at 7:21 am
Viewing 15 posts - 57,406 through 57,420 (of 59,067 total)