Viewing 15 posts - 16 through 30 (of 137 total)
Eric M Russell (4/10/2015)
From what you recall, basically what was the DDL; was it essentially just an integer column?
It was a VARCHAR built from:
1 - 4 = DATEPART(yyyy,GETDATE)
5...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
April 13, 2015 at 9:27 am
A trigger can be set to fire when a table is updated, inserted to, or deleted from. Have the trigger fire some t-sql code to do the processing...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
April 9, 2015 at 7:49 pm
ZZartin (4/3/2015)
Quick question Grant, how many times have you seen systems/processes fail on the 13th of the month? I can count a good handful.
In my last job I managed a...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
April 9, 2015 at 1:49 pm
And what constitutes Day1? Is Day1 always the earliest date in your table?
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
April 9, 2015 at 1:12 pm
First there is no way to join your customer table to your materials table. It does sound like homework and a trick question at that.
If real, then you need...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
April 9, 2015 at 12:41 pm
Are you able to Import the Excel file into a temp table?
( Right-click on [Database Name]-->Tasks-->Import... )
Trying that might expose if there's some kind of error in the Excel file.
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
April 7, 2015 at 1:37 pm
Tony Lanterman (3/13/2015)
One of our contract developers was quite fond of this and often set lines to BLINK. There are few things more annoying than blinking comment code.
Oh...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
March 13, 2015 at 11:48 am
SELECT
em.empid,em.Emp_Name,
[Week] = (SELECT SUM(OTHours) FROM tblOTDetails w WHERE w.empid = e.empid and DATEPART(WW, otdate) = DATEPART(WW, GETDATE())),
[Month] = (SELECT SUM(OTHours) FROM tblOTDetails w WHERE w.empid = e.empid and DATEPART(mm, otdate)...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
March 9, 2015 at 1:02 pm
Alternatively you could design your date fields as VARCHAR(10) and format them any way you wish. Of course that would completely negate the extreme usefulness of the DATETIME type...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
March 4, 2015 at 2:10 pm
I understood your question and AFAIK the answer is NO. Check for yourself under Tools-->Options... You'll find several options for formatting the results of a...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
March 4, 2015 at 2:07 pm
Jeff Moden (3/3/2015)
CELKO (3/3/2015)
While what you say is absolutely true, there are so many nice ways to say this and so many ways to make this useful and you...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
March 4, 2015 at 1:35 pm
MMartin1 (3/2/2015)
This works with TRUE or FALSE >
DECLARE @mybit bit;SET @mybit = 'true';
SELECT @mybit
Though yes/no , on/off do not. Just want to add to this post.
This is interesting....
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
March 4, 2015 at 1:31 pm
February 26, 2015 at 7:45 am
Jeff Moden (2/23/2015)
Like I said, to each their own but I typically won't pluralize table names.
DonlSimpson (2/24/2015)
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
February 26, 2015 at 7:26 am
CELKO (2/24/2015)
You should follow ISO-11179 rules for naming data elements. You failed!
But even worse than all of this, is that you have two tables with the same structure.
Oh?...
Sigerson
"No pressure, no diamonds." - Thomas Carlyle
February 25, 2015 at 8:37 am
Viewing 15 posts - 16 through 30 (of 137 total)