Viewing 15 posts - 241 through 255 (of 432 total)
SQLJocky (5/4/2010)
May 4, 2010 at 3:17 pm
Do you mean is it possible to shrink the database files using the DBCC SHRINKFILE or DBCC SHRINKDATABASE commands? Yes it is possible. In general shrinking databases is not a...
May 4, 2010 at 12:26 am
From your description it sounds like your problem may be a foreign key violation. Is that so? If so then you could use the ON UPDATE CASCADE option to ensure...
April 30, 2010 at 1:04 pm
So you have a badly designed application and therefore you have to work around it in the database. Fair enough, we've all been there. 180 million rows is not a...
April 30, 2010 at 1:00 pm
Danny Sheridan (4/30/2010)
Each month I have to load billing data into monthly tables (item01 for January, item02 for February, item03 for March, etc.)
Why would you do that? Use one table...
April 30, 2010 at 12:24 pm
If you are only changing one row then I don't understand your problem. Either the constraint is violated or it isn't.
A single UPDATE statement can change multiple columns. What is...
April 30, 2010 at 9:44 am
You could also use a proc and an independent sequence table. This has the advantage that you can make the target column NOT NULL and/or UNIQUE if you want to:
CREATE...
April 30, 2010 at 9:06 am
What was the error message? If it was actually a foreign key violation then enable the ON UPDATE CASCADE option on the foreign key constraint.
If it really was a unique...
April 30, 2010 at 7:43 am
PaulB-TheOneAndOnly (4/16/2010)
Ninja's_RGR'us (4/15/2010)
April 28, 2010 at 3:32 pm
Scott Coleman (4/28/2010)
An IDENTITY column will help you find the most recently-inserted row
Possibly it will if your inserts are serialized. If you have multiple connections with multi-statement transactions then it...
April 28, 2010 at 3:01 pm
This is not a very sensible use of a trigger in my opinion. Supplying a default value for one column isn't much justification for the overhead and inconvenience of a...
April 27, 2010 at 3:35 pm
Jeff Moden (4/27/2010)
Heh... obviously not a fan of WITH (INDEX(0)) or the "Quirky" Update, huh?
WITH (INDEX(0)) doesn't mean a table is ordered. It just specifies a hint for an execution...
April 27, 2010 at 9:48 am
TheSQLGuru (4/27/2010)
Tables are UNORDERED sets of data unless they have a CLUSTERED INDEX on them.
Tables are unordered sets even if they do have a clustered index. A clustered index is...
April 27, 2010 at 8:09 am
If your table lacks a key then obviously you ought to add one at the first opportunity, otherwise it could be difficult to make any sense of the results. Why...
April 26, 2010 at 6:20 am
PaulB-TheOneAndOnly (4/23/2010)
I'll love to see an ER diagram
But please not ones like these created with the Management Studio "designer". Silly pictures like that don't even qualify as an ER diagram...
April 23, 2010 at 5:49 am
Viewing 15 posts - 241 through 255 (of 432 total)