SQL Server
Home
Options
51
SQL-Server-Team on 03-23-2019 02:13 PM
4
SQL-Server-Team on 03-23-2019 02:12 PM
3
Jakub Szymaszek on 03-23-2019 02:09 PM
12
Jakub Szymaszek on 03-23-2019 02:06 PM
9
SQL-Server-Team on 03-23-2019 02:05 PM
18
Jakub Szymaszek on 03-23-2019 02:02 PM
6
SQL-Server-Team on 03-23-2019 02:00 PM
9
Jakub Szymaszek on 03-23-2019 01:59 PM
6
Ronit Reger on 03-23-2019 01:56 PM
64
SQL-Server-Team on 03-23-2019 01:44 PM
2
raulgarciamsft on 03-23-2019 01:43 PM
4
jackrichins on 03-23-2019 01:43 PM
14
Jakub Szymaszek on 03-23-2019 01:42 PM
1
SQL-Server-Team on 03-23-2019 01:40 PM
3
Jakub Szymaszek on 03-23-2019 01:39 PM
15
Jakub Szymaszek on 03-23-2019 01:39 PM
39
raulgarciamsft on 03-23-2019 01:38 PM
8
raulgarciamsft on 03-23-2019 01:37 PM
16
raulgarciamsft on 03-23-2019 01:37 PM
27
SQL-Server-Team on 03-23-2019 01:33 PM
12
SQL-Server-Team on 03-23-2019 01:32 PM
4
SQL-Server-Team on 03-23-2019 01:32 PM

The following has evaluated to null or missing: ==> images[0]?split("src=")[1] [in template "common-functions" at line 135, column 28] ---- Tip: It's the final [] step that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #local itemImageUrl = images[0]?split... [in template "common-functions" in function "getImage" at line 135, column 5] ----

raulgarciamsft on 03-23-2019 01:32 PM
13
raulgarciamsft on 03-23-2019 01:29 PM
1
jackrichins on 03-23-2019 01:22 PM
40
SQL-Server-Team on 03-23-2019 01:21 PM
15
SQL-Server-Team on 03-23-2019 12:57 PM
22
SQL-Server-Team on 03-23-2019 12:57 PM
25
SQL-Server-Team on 03-23-2019 12:50 PM
16
SQL-Server-Team on 03-23-2019 12:50 PM
Latest Comments
@Perry Skountrianos Is there any known issue with using the SqlSessionStateProviderAsync with tables/stored procedures created with the SQL Server 2016 scripts mentioned above?
0 Likes
When will this make it into Azure SQL DB?
0 Likes
https://gist.github.com/ramnov/a927a97438819df547a7bbd13b404386 https://gist.github.com/ramnov/de62737a1146e50ad0125f018eafae6a https://gist.github.com/ramnov/0532070291d2a7af1934898b0e85d32b
1 Likes
@LeoHu it collects stats based on lightweight profiling (link to docs on this feature are in the post). That said, it is an opt-in feature under preview precisely because there's only so much we can measure in our labs, and we count on you to help us determine if the expected low cost is true for di...
0 Likes
So this is a preference under Tools/Options? That would be cool if it was a permanent option for SSMS, though I too wonder about the performance impact
0 Likes