I have a situation which I can resolve by adding a column which would be a datetime or a ntext type.
In terms of performace, which of these would be better to use. The number of records are more than 60000. I was thinking datetime since I could index on it, but not sure if ntext can be…any suggestion or discussion on which would handle memory,speed better…or any other performance issues?
Update: the column i will add are independent- one is date time and other is text, i can resolve the issue by having anyone, NOTE: I am not trying to store datetime as ntext here.
60000 records is nothing for SQL Server.
So there shouldn’t be any noticeable difference. Maybe there would be a difference if it was a REALLY big table (hundreds of millions of records, and above…), but not with your amount of data.
However, as the others already said: your statement that you can either use datetime or ntext sounds very strange to me. If it’s really date and/or time values, use
datetimeand notntext!!!EDIT:
Now that you clarified that you don’t want to store date values in a text column:
I would suggest that you use the
datetimecolumn. It’s better thanntextperformance wise.As a side note: if you prefer to use the text column, you should use
nvarchar(max)instead ofntext.ntextis slower and deprecated.