Viewing 15 posts - 6,931 through 6,945 (of 7,419 total)
Grant Fritchey (10/11/2012)
ScottPletcher (10/11/2012)
Grant Fritchey (10/11/2012)
As an aside, the CHAR(2) would be a really poor choice for the first column in a compound key. You'd want to use either the...
October 11, 2012 at 12:25 pm
Grant Fritchey (10/11/2012)
As an aside, the CHAR(2) would be a really poor choice for the first column in a compound key. You'd want to use either the INT or the...
October 11, 2012 at 10:40 am
Here's an alternative:
SELECT u.*, n.ID, n.notes
FROM UserTable u
INNER JOIN Notes n ON
(u.lastaccounttype = 'account1' AND n.account1 = 1) OR
(u.lastaccounttype = 'account2' AND...
October 11, 2012 at 9:55 am
No. Autogrow can be changed anytime, on either data or log, and will be used the next time the file grows dynamically.
But I suggest using a fixed amount instead...
October 11, 2012 at 9:43 am
I know you want some specifics that you can apply to creating all indexes on all tables, but there really aren't any.
There are some general rules for creating proper indexes,...
October 11, 2012 at 9:11 am
If you're going to search by Col1 and Col4, then, in general, put them first in the index, to narrow the row range immediately as much as possible.
I didn't say...
October 11, 2012 at 8:47 am
The nvarchar(20) does make that a problematic clustering key, but it still depends.
A three-column is not slower to do lookup on if that's what you (almost) always specify in the...
October 10, 2012 at 3:54 pm
Sean Lange (10/9/2012)
maryjane9110024 (10/9/2012)
October 10, 2012 at 11:16 am
It's also possible you need the other index instead, rather than in addition to, the one you have know.
You always need to look at the usage stats too when looking...
October 10, 2012 at 11:07 am
Or just add the required permission(s) to the model db. Every db created after that will automatically have the same permission(s).
October 9, 2012 at 11:47 am
jarid.lawson (10/8/2012)
ScottPletcher (10/8/2012)
SELECT lastname
FROM HR.Employees
WHERE
lastname LIKE '%[/]%' AND
lastname NOT LIKE '%[/]%[/]%'
Still have to add the line that removes / in the first...
October 8, 2012 at 2:47 pm
SQL Server muss immer the log gescrieben.
October 8, 2012 at 10:48 am
SELECT lastname
FROM HR.Employees
WHERE
lastname LIKE '%[/]%' AND
lastname NOT LIKE '%[/]%[/]%'
October 8, 2012 at 10:26 am
Michael T2 (10/5/2012)
actually that wont work, if shipweight2 and shipweight3 are both null it will update them both. I dont want that
No, if both are NULL, only shipweight2 will UPDATE,...
October 8, 2012 at 7:58 am
Viewing 15 posts - 6,931 through 6,945 (of 7,419 total)