They recognize their design presents challenge to scalability. But between now and the rewrite, I'm saddled up and will not lack for tiltable windmills
The trick is to build a correlated subquery where you get a list of subjects that the student in question hasn't taken
DECLARE @N TABLE(NID INT, NName varchar(10))
DECLARE @C TABLE(CID INT, CName varchar(10))
DECLARE @E TABLE(NID INT, CID INT)
INSERT INTO @N VALUES(1,'John'),(2 ,'Matt'),(3,'Smit...
interesting ... i have one set of queries that go from ~1 minute runtimes to ~100 minute runtimes with the new CE in 2014 but only with a cold cache. warm cache results return the expected improvement with the new CE.
It's intermittent here. Worked long enough for me to do what I wanted. Going to sleep now, no doubt all will be well by the time I wake up. Thanks for the info.
Our team had an issue where an
Insert into Table2
Select * from Table1
Did not fill specific columns. We tested several times.
Select * from Table1
All the data was present.
Truncate Table2
Insert into Table2
Select * from Table1
The same specific columns where not filling. The rest of...
You should really be explicitly stating what columns go where and definitely not using a Select * on an Insert
Insert into Table2(column1, column2, column3)
Select column1, column2, column3
from Table1
now you KNOW Table1.Column1 maps to Table2.Column2
As part of an automated SQL Server installation process, I'd like to programmatically check whether a Windows Failover Cluster has already been validated.
There are some ways to validate the cluster programmatically, such as the Powershell cmdlet Test-Cluster, but I haven't been able to find a w...
Could you perhaps post the columns so we have some clue as to what's going on? At the moment we are kind of forced to take your word for it which make it impossible to see what's happening and help you out. The results of selecting from table 1 would help as well. — Zane14 secs ago
So basically in SQLServer a NULL means there is no value and thus can't be compared which returns some unexpected results.
For example, the following query doesn't return rows where value IS NULL but I want it to:
SELECT *
FROM table
where
(value != 26)
and
date IS NULL
and
last_m...
i dont like using parentheses. i mean ... c'mon ... order of operations isnt really maths, right? why can't the parser just read my mind instead??!!!???!!!
I've got this CTE and it's giving me fits. I'm getting the following Error which I can't track down.
Conversion failed when converting the varchar value 'Actual' to data type int.
The problem is I have no column in any table called Actual. I'm not even sure where to begin. I've tried breaking t...
what's the point of COALESCE(m.ModalityID,NULL)? COALESCE is used to replace null with another value - right now you are replacing null with null. — bluefeet ♦1 min ago
@bluefeet: maybe it's just a placeholder for a value OP doesn't know yet, but it doesn't hurt and is not the reason for the issue, is it? — Tim Schmelter3 mins ago
@Zane there are so many things wrong - DISTINCT and GROUP BY
I attempted to respond nicely
@TimSchmelter I'm just pointing out something in the code that doesn't make a whole lot of sense. We are here to try and help people improve their skills, correct? — bluefeet ♦2 mins ago
@swasheck I get it to, but I also added another comment offering a suggestion for them to research. It sure seems the person who wrote that query doesn't know what they are doing
That would be like if I paraphrased to CASE WHEN Column1 is NULL then NULL else NULL as DumbThingToDo people would think I'm a fucking idiot, and with good cause.
@Zane: How would I know? Maybe COALESCE(Value,(SELECT SomethingElseWhichIDontKnowYet)). Maybe OP wants to remember that it can be null and must be replaced with something else. I don't know. It just seems to be very unlikely that OP doesn't know the functionality of COALESCE. — Tim Schmelter2 mins ago
If one of my devs brought me that query I think it would be time to take them back behind the barn and put them down.
This question appears to be off-topic because it is about debugging a mystery data point that has not been explicated. Needle-in-haystack operation that is incumbent upon the OP to discover and remedy. Without a full dump of the table, we have literally no idea which data point is being forced into an implicit conversion (and failing). — swasheck52 secs ago
Our team had an issue where an
Insert into Table2
Select * from Table1
Did not fill specific columns. We tested several times.
Select * from Table1
All the data was present.
Truncate Table2
Insert into Table2
Select * from Table1
The same specific columns where not filling. The rest of...
You should really be explicitly stating what columns go where and definitely not using a Select * on an Insert
Insert into Table2(column1, column2, column3)
Select column1, column2, column3
from Table1
now you KNOW Table1.Column1 maps to Table2.Column2
So basically in SQLServer a NULL means there is no value and thus can't be compared which returns some unexpected results.
For example, the following query doesn't return rows where value IS NULL but I want it to:
SELECT *
FROM table
where
(value != 26)
and
date IS NULL
and
last_m...
I've got this CTE and it's giving me fits. I'm getting the following Error which I can't track down.
Conversion failed when converting the varchar value 'Actual' to data type int.
The problem is I have no column in any table called Actual. I'm not even sure where to begin. I've tried breaking t...
