Viewing 15 posts - 481 through 495 (of 581 total)
decimal(9,5) means the highest number you can do is 9999.99999
The 9 includes the 5 digits to the right of the point.
May 23, 2006 at 7:06 pm
So you want to combine a figure for the month to date with a figure for yesterday? I assume you don't want your month-to-date receipts broken down by day. You...
May 23, 2006 at 7:04 pm
need to see some code
May 23, 2006 at 6:37 pm
May 21, 2006 at 2:44 pm
If you want to use TSQL only, you would need to use either a linked server or a remote server with a lot of stored procs with many parameters. I...
May 21, 2006 at 2:17 pm
Do you allow them to specify parentheses as well? If not, they are likely to get some unexpected results if they mix AND with OR - especially since AND is...
May 21, 2006 at 2:00 pm
Answer 1 is correct if you want a necessary (but not sufficient) condition for a BLU - the non clustered index must not be a covering index.
Answer 2 is correct if you...
August 3, 2005 at 10:09 am
These are a bit dirty and make use of implicit conversions but they are probably pretty efficient:
create function dbo.dateportion (@d as datetime)
returns datetime
as
begin
return floor(cast(@d as float))
end
create function dbo.timeportion (@d as...
April 11, 2005 at 7:40 pm
So OS files on your database server aren't backed up?
May 28, 2004 at 9:46 am
If you haven't got SQL backups (inc. tran log backups as in previous post) to cover the period immediately before the incident (but surely you must have???), your only hope...
May 28, 2004 at 3:39 am
Previous poster's point is a good one, arising from the problem of searching on a derived value. Given that the data presumably has a high cardinality ( many different values),...
March 31, 2004 at 1:36 am
The syntax quoted from BOL shows that the first three params are mandatory: they aren't contained in square brackets.
March 24, 2004 at 4:06 am
Phone nos should be all different (at least within each group) in example data.
March 5, 2004 at 3:03 am
Repeated data in NoelD's example:
Table_Pos_Dep_Phone
AssocID DepID PosID fk_PhoneID
1D1P1228374 2D1P1232527 3D1P2234222 4D1P2123423 5D1P2123423 6D2P1123423 7D2P1123423 8D2P3123423 9D2P3123423 10D2P3123423
I'd suggest something like:
tblDept: DeptID (PK) Description e.g. 'Finance' ...
tblJob: JobID (PK) Description e.g. 'Clerical Assistant' ...
tblPost: PostID (PK) DeptID (FK) JobID (FK) Description (non-normal data for illustration only) e.g. 'Finance Clerical Asst...
March 5, 2004 at 3:01 am
Viewing 15 posts - 481 through 495 (of 581 total)