Activity overview
Latest activity by eklein
It was in SSMS only, but that is the only environment that I normally work in If it makes a differance here is the current release levels SQL Server Management Studio 15.0.18338.0 SQL Server Management Objects (SMO) 16.100.41011.9 Microsoft Analysis Services Client Tools 15.0.19205.0 Microsoft Data Access Components (MDAC) 10.0.19041.1 Microsoft MSXML 3.0 5.0 6.0 Microsoft .NET Framework 4.0.30319.42000 Operating System 10.0.19042 / comments
It was in SSMS only, but that is the only environment that I normally work in If it makes a differance here is the current release levels SQL Server Management Studio 15.0.18338.0SQL Server Ma...
It was in SSMS only, but that is the only environment that I normally work in / comments
It was in SSMS only, but that is the only environment that I normally work in
Very minor bug in "expand wildcard"
I know this is a minor issue but it's so odd I thought I would pass it along. Looking at the following code SELECT *FROM( SELECT rpt_rec_num, LEFT(cell_row, 3) AS cell_row, ...
string_agg not recognized as a grouping function
Running version 9.1.1.4243 I had following code SELECT TOP ( 50 ) cd.RPT_REC_NUM , cd.component , cd.sheet , cd.cell_row ...
Format fails if SQLCMD mode variable is present
the following
UPDATE [provider_master]
set FIPS = p.fips_code,
MSA = p.msa_code,
longatude = p.fac_long,
latatude = p.fac_lat
FROM provider_master ...
Update without where warning
While I like the intent of the warning of update/delete without a where clause, I find myself having frequent issues with code like the following :
UPDATE [wk_srv]
SET [surg_disch_mc&#...
Thank you The work around is easy enough for now / comments
Thank you The work around is easy enough for now
Format SQL function fails if SQLCMD mode variable is present
The following code
SELECT * FROM dbo.sheet_master
WHERE RPT_REC_NUM IN ( SELECT RPT_REC_NUM
FROM Cost_report_$(HCycleN).dbo.rrn_status
WHERE Rec_status = 'dropped'
)
will...
Yes that could very well be the case. Sorry to inconvenience you. When you get that situation, (failure without an identified error) you might want to issue a different error message suggesting an error in the proceeding/following code. I'm sure I am not the first to think Sql prompt was the problem, when it was really my code that was faulty. / comments
Yes that could very well be the case. Sorry to inconvenience you. When you get that situation, (failure without an identified error) you might want to issue a different error message suggesting...