Viewing 15 posts - 196 through 210 (of 5,356 total)
June 2, 2005 at 3:19 am
Yes! Alternative b) is the strength of RDBMS. Alternative a) is a violation of 1NF and should be avoided.
June 2, 2005 at 12:40 am
Now that I read this, I remember having used it myself before...
Thanks!
June 1, 2005 at 3:37 pm
I would run a trace to track this down.
June 1, 2005 at 3:35 pm
Please don't multipost:
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=4&messageid=186799
June 1, 2005 at 3:31 pm
I don't like your sarcasm here and I didn't want to get personell.
While you made a good observation on this CLUSTERED PRIMARY KEY,...
June 1, 2005 at 3:06 pm
We have one server here, that's completely busy with the call center database being the only one on that server, while another server hosts some 30+ less frequently used and...
June 1, 2005 at 2:13 pm
I'm not completely against the use of dynamic sql. However, it is way too often too quickly advocated while there are better static solutions available. Just read Erland's dynamic search...
June 1, 2005 at 1:57 pm
Do this at the client.
I can't think of a solution for this right now, since you can't GROUP BY a common criteria here. However, your SELECT statement might be...
June 1, 2005 at 1:53 pm
You were very lucky that you've got the job.
You have several more or less severe mistakes here.
First, a heap is a table without a clustered index. It is...
June 1, 2005 at 1:24 pm
You can't restrict this. Everybody who connects can issue a
SELECT * FROM master..sysdatabases
The reglementing factor here however is the access to the databases.
June 1, 2005 at 12:58 pm
I really like DATETIME columns as candidates for clustered indexes, since I deal very often with range queries for date intervals. I think this is the best way to go...
June 1, 2005 at 12:55 pm
Viewing 15 posts - 196 through 210 (of 5,356 total)