SELECT not working when it follows an UPDATE - php

Question

I'm using PHP to send a query to Sql Server. The problem is, my "SELECT 1 AS updateResults" statement doesn't work if it's done after the UPDATE statement. A resource is returned to PHP but it doesn't have any rows.
Here's a simplified version of my query:
--SELECT 1 AS updateResults --if this is done before the UPDATE, a row gets returned
UPDATE theTable SET theValue = 'x' WHERE theRow = '5'
SELECT 1 AS updateResults --if this is done after the UPDATE, a row doesn't get returned
My UPDATE query is valid and does what it's supposed to do.
I've also tried the "SELECT 'updateResults' = 1" format and tried putting a ; at the end of each statement and it didn't make a difference.
Any ideas?
Here's the PHP code:
$updateSQL = "BEGIN TRANSACTION
DECLARE #result1 int
DECLARE #result2 int
--SELECT 1 AS updateResults --if this is here, the row gets returned
UPDATE theTable
SET endDate = '" . $endDate . "'
WHERE permitYear = '" . $permitYear . "'
UPDATE theTable
SET startDate = '" . $startDate . "'
WHERE permitYear = '" . $nextYear . "'
--Test to make sure both records were saved
SELECT #result1 = permitYear
FROM theTable
WHERE permitYear = '" . $permitYear . "'
AND endDate = '" . $endDate . "'
SELECT #result2 = permitYear
FROM theTable
WHERE permitYear = '" . $nextYear . "'
AND startDate = '" . $startDate . "'
if ((#result1 > 0) AND (#result2 > 0))
BEGIN
COMMIT TRANSACTION
SELECT 1 AS updateResults
END
ELSE
BEGIN
ROLLBACK TRANSACTION
SELECT 0 AS updateResults
END";
$updateRS = sqlsrv_query($con, $updateSQL);
if (!is_resource($updateRS)) {
//There was a problem. A resource wasn't returned. It never fails here
exit;
}
if (!sqlsrv_has_rows($updateRS)) {
echo ("fail for no rows returned");
exit;
}
$updateARR = sqlsrv_fetch_array($updateRS);
//It makes it here if the SELECT is done before the UPDATE
if ($updateARR['updateResults'] == '1') {
//success
}
else {
//save problem
}
Additional info: If I take out the 2 UPDATE statements it runs as expected and returns the updateResults row.

Answer 1

You should query select like this
SELECT * FROM table1 WHERE 'updateResults' = 1

Answer 2

I ended up doing this in two SQL statements rather than one. Here's what I did:
I took out the SELECT x AS updateResults lines from the $updateSQL then:
$updateSQL = ...(same as the question, without the SELECT x AS updateResults lines)...
sqlsrv_query($con, $updateSQL);
$testSQL = "
DECLARE #result1 int
DECLARE #result2 int
SELECT #result1 = permitYear
FROM theTable
WHERE permitYear = '" . $permitYear . "'
AND endDate = '" . $endDate . "'
SELECT #result2 = permitYear
FROM Transportation.dbo.PermitDate
WHERE permitYear = '" . $nextYear . "'
AND startDate = '" . $startDate . "'
if ((#result1 > 0) AND (#result2 > 0))
BEGIN
SELECT 1 AS updateResults
END
ELSE
BEGIN
SELECT 0 AS updateResults
END
";
$testRS = sqlsrv_query($con, $testSQL);
if (!is_resource($testRS)) {
//There was a problem. A resource wasn't returned
}
if (!sqlsrv_has_rows($testRS)) {
//fail for no rows
}
$testARR = sqlsrv_fetch_array($testRS);
if ($testARR['updateResults'] == '1') {
//success
}
else {
//fail - the changes were not saved
}

Answer 3

Did you try to reverse the order of the SELECT and UPDATE statements when they're part of the transaction? If not, I would try:
Instead of:
COMMIT TRANSACTION
SELECT 1 AS updateResults
Try:
SELECT 1 AS updateResults
COMMIT TRANSACTION

Answer 4

I didn't have "SET NOCOUNT ON" so the SQL messages such as "(1 row(s) affected)" were being returned before the SELECT results. My code should have been:
$updateSQL = "SET NOCOUNT ON
BEGIN TRANSACTION
...
This way the SQL messages would be supressed.
As a side note, after I figured out the issue I noticed the following: Even though I wasn't using a stored procedure for this, I noticed when you create a stored procedure in SQL Server Management Studio, it even puts the following in the template for you:
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;