Viewing 15 posts - 2,791 through 2,805 (of 59,098 total)
To get the nice-warm-fuzzies on that, though, start a new session and run the following code... It should run just fine in the new session where you haven't set the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2022 at 10:58 pm
IF you add the statement
SET DATEFORMAT DMY;
before you attempt the INSERT, the error will go away and the INSERT runs successfully.
Although this is an option -...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2022 at 10:51 pm
Unless you meant conversion at the datasource ?
As Jeffrey Williams is implying, that would be the best solution.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2022 at 6:35 pm
IF you add the statement
SET DATEFORMAT DMY;
before you attempt the INSERT, the error will go away and the INSERT runs successfully.
Although this is an option - don't do...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2022 at 6:33 pm
SELECT f1_AllCount = COUNT(f1.PartId)
,f1_UnqCount = COUNT(DISTINCT f1.PartID)
FROM Technology.Receipe ft
JOIN ExtractReports.dbo.TechnologyPlPartsFeaturValuesOrg f1 ON ft.featureid = f1.featureid
WHERE ft.operatorid = 1;
result is
f1_AllCount f1_UnqCount
124140 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2022 at 6:29 pm
jcelko212's post got me thinking
I tried to change the datatype of the paydate column to date by using the alter command but ended up getting this error "Conversion failed...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2022 at 5:03 am
so how to use cross apply as you write below
The optimizer attempts to SORT 65 million rows after a merge join. Yeeeesh. One way to re-write the query would...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2022 at 4:47 am
I've found that I really don't need all of that stuff for SQL Server. xp_LoginInfo and sp_validatelogins usually provide what I need. If not, then I go to the Windows...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2022 at 9:50 pm
Please learn what a table is. First, we need to fix your non-table.
CREATE TABLE Expenses (emp_id CHAR(10) NOT NULL, pay_date DATE NOT NULL, -- read ISO-8601 formats expense_type VARCHAR(30)...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2022 at 9:09 pm
I suspect a couple of accidental CROSS JOINs is the issue. Please run the following code and post the results.
SELECT f1_AllCount = COUNT(f1.PartId)
...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2022 at 6:16 pm
Ah... I see what you mean. Guess I'll have to look up how to do a "StaNine" and see if I can make a function or a GP proc for...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2022 at 9:03 pm
That procedure just calls some individual functions used to get each Stanine.
If you are looking for a formula for determining the bellcurve, we pay for studies to be done...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2022 at 8:26 pm
It has one big select statement that besides tables also joins one view and one table-valued function. It does not have explicit transaction.
But what I can do about blockings?...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2022 at 8:13 pm
Thank you Phil for this idea, i will test and let you know if this is working.
It would still be nice to know the need for this particular format. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2022 at 8:08 pm
Excellent !!! Thank you very much!!
Any chance of us getting a peek at your "StaNine" stored procedure?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2022 at 8:06 pm
Viewing 15 posts - 2,791 through 2,805 (of 59,098 total)