Viewing 15 posts - 2,041 through 2,055 (of 2,356 total)
Jeff Moden (6/12/2015)
phosplait (6/12/2015)
@jeff, there is no begin in the function. It is an inline function that does a cross apply with another inline function onto a range of dates
Just...
June 15, 2015 at 9:04 am
Option 3???
Flag records as closed and move them to archive after xx months?
There will probably be a need to view, and possibly change these records for a period of time...
June 8, 2015 at 11:19 am
Put a case statement in the ORDER BY clause of your query:
ORDER BY CASE WHEN BitField = 0 THEN 1
...
June 5, 2015 at 7:08 pm
Is this what you had in mind?
SELECT X.SomeColumn, X.AnotherColumn, X.SomeThirdColumn
FROM
(SELECT 1 as OrderingCol, t1.SomeColumn, t1.AnotherColumn, t2.SomeThirdColumn
FROM
Table1 t1 INNER JOIN Table2 t2
ON t1.ID = t2.fkID
WHERE t1.BitField = 0
UNION
SELECT 2 as...
June 5, 2015 at 12:06 pm
krismaly (6/5/2015)
Is there no straight forward answer?why we have to change to varchar then to INT?
What are you trying to do?
If the date is 01/01/2014, are you trying to store...
June 5, 2015 at 11:15 am
Andy Warren (6/5/2015)
June 5, 2015 at 9:52 am
Andy Warren (6/5/2015)
June 5, 2015 at 8:23 am
There is a standard format for VIN's since 1980.
You can create a function that will validate the VIN
Start here.
June 4, 2015 at 1:37 pm
mwilliams4nc (6/4/2015)
Now using SQL 2008R2, very familiar in parts, very different in others, I'm learning every day.
I am...
June 4, 2015 at 12:53 pm
This is not an uncommon scenario, and you can this with no issues.
Where you run into issues is when you modify the replicated objects in the subscriber database.
A...
June 4, 2015 at 11:02 am
Eirikur Eiriksson (6/2/2015)
Lowell (6/2/2015)
i belive a serverice stop and start of SQL automatically bumps identity seeds by 1000 in SQL2012read about the feature / defect here:
Only seen this with AO,...
June 2, 2015 at 1:21 pm
Ed Wagner (6/2/2015)
Lowell (6/2/2015)
i belive a serverice stop and start of SQL automatically bumps identity seeds by 1000 in SQL2012read about the feature / defect here:
Well, that's an interesting one....
June 2, 2015 at 12:26 pm
Just remove the column you do not want to see from the SELECT statement
SELECT.GLMASTER.COMPANY,
.GLMASTER.ACCT_UNIT,
.GLNAMES.DESCRIPTION,
.GLMASTER.ACCOUNT,
.GLCHARTDTL.ACCOUNT_DESC,
--REMOVE THIS COLUMN
.GLNAMES.ACTIVE_STATUS
FROM (
.GLMASTER LEFT JOIN.GLNAMES ON (.GLMASTER.ACCT_UNIT =.GLNAMES.ACCT_UNIT)
AND (.GLMASTER.COMPANY =.GLNAMES.COMPANY)
)
LEFT JOIN.GLCHARTDTL ON.GLMASTER.ACCOUNT =.GLCHARTDTL.ACCOUNT
WHERE (
(
(.GLMASTER.ACCT_UNIT) <> 10002
AND...
May 28, 2015 at 1:09 pm
You are using the UI, correct?
Well, don't do that! 🙂
SELECT Field_I_DO_Want_To_See1, Field_I_DO_Want_To_See2, Field_I_DO_Want_To_See3
FROM SomeTable
WHERE Field_I_Do_Not_Want_To_See = 'Foo'
May 28, 2015 at 12:48 pm
Insert into TableB
(
UserName, ProjectName, processdate, Recordprocess, Comments, RecordProcessExt
)
SELECT DISTINCT @UserName, 'Test Project', getDate(), Col1, 'Test Comments', col1+ 'TR'
from Table1
May 28, 2015 at 10:51 am
Viewing 15 posts - 2,041 through 2,055 (of 2,356 total)