Comments
Sort by recent activity
Some additional info on this. I discovered part of the problem - at least related to the difference in errors reported. I think the UI's "verify" was smart enough to build the DB on the localhost (2019) instance where the dev DB resides. The default instance for the Invoke-DatabaseBuild is a (localDB) instance, which is compatibility 130. Using -TemporaryDatabaseServer 'Data Source=localhost'is more consistent with "verify" in SSMS. / comments
Some additional info on this.I discovered part of the problem - at least related to the difference in errors reported. I think the UI's "verify" was smart enough to build the DB on the localhost (...
Updating to 4.2.20161.20485 and restarting my computer seems to have fixed. Going to leave this one as unanswered for a wee bit to make sure the issue doesn't reappear. / comments
Updating to 4.2.20161.20485 and restarting my computer seems to have fixed. Going to leave this one as unanswered for a wee bit to make sure the issue doesn't reappear.
I think you misunderstood. I know it is settable at the "customize for this level..." - that's what I used. The issue is that it turned notifications on for ALL alerts - not just ones that were previously set to notify. / comments
I think you misunderstood. I know it is settable at the "customize for this level..." - that's what I used. The issue is that it turned notifications on for ALL alerts - not just ones that were p...
Good question. Maybe something like: $sourceDB = New-DatabaseConnection [...] New-DatabaseMigration -InputObject <PathToSqlProjectFile> -Source $sourceDB Source DB could also be the default dev DB from the sql proj file. It would behave similar to the process that happens in SSMS when we "generate migration(s)". / comments
Good question. Maybe something like:$sourceDB = New-DatabaseConnection [...]New-DatabaseMigration -InputObject <PathToSqlProjectFile> -Source $sourceDBSource DB could also be the default dev DB fr...
Oh - and sometimes, I will use a round-trip data modeling tool (e.g. dbschema) for the schema mods. / comments
Oh - and sometimes, I will use a round-trip data modeling tool (e.g. dbschema) for the schema mods.
I used to use the VS plugin. Now, mostly the SSMS plugin. I imagine most work will still occur in the UI. However, I would also find value in being able to automate. For example, i could write a powershell script that adds a column, updates a sproc to use that column, gens the migration, and commits the code, triggering a CI/CD process. Just a nice-to-have. / comments
I used to use the VS plugin. Now, mostly the SSMS plugin. I imagine most work will still occur in the UI. However, I would also find value in being able to automate. For example, i could write ...
Cool. Thank you for confirming, @Ivo_Miller. / comments
Cool. Thank you for confirming, @Ivo_Miller.
Thanks, @Russell D . That makes sense (not documented due to not supporting direct querying of the DB). I looked at "base monitor.log" file (found it in .\localhost\BaseMonitor). Didn't see anything regarding notification/email failure during the time frame when this occurred. Might be time for a support case. / comments
Thanks, @Russell D . That makes sense (not documented due to not supporting direct querying of the DB).I looked at "base monitor.log" file (found it in .\localhost\BaseMonitor). Didn't see anythin...
Thanks, @Russell D , for the fn tip (TicksToDateTime). Is this in the docs anywhere? Also, wondering if you might have a follow-up to my request for which logs to look at (and what to look for in them) for failed email notification. Here is what I see from my query: [image] / comments
Thanks, @Russell D , for the fn tip (TicksToDateTime). Is this in the docs anywhere? Also, wondering if you might have a follow-up to my request for which logs to look at (and what to look for in...
Thanks, @Russell D. I wrote the following SQL based on your guidelines: SELECT TOP(10)
at.Name AS AlertTypeName
,a.AlertId
,a.TargetObject
,a.Raised
,n.NotificationDate
,n.NotificationType
FROM
alert.Alert AS a
INNER JOIN alert.Alert_Type AS at
ON(a.AlertType = at.AlertType)
LEFT JOIN alert.Notifications AS n
ON(a.AlertId = n.AlertId)
--LEFT JOIN alert.
WHERE
at.Name = N'Job failing'
ORDER BY
a.AlertId DESCI'm assuming that NULL for NotificatonDate and NotificationType means no notification was sent. Before submitting a support ticket wondering if you could help me navigate the myriad log files. Where would I look for issue related to notifications not being sent? Thanks, -Peter PS Any tips on parsing/interpreting your "fancy" Date column values (e.g. 637249573070000000)? / comments
Thanks, @Russell D. I wrote the following SQL based on your guidelines:SELECT TOP(10)
at.Name AS AlertTypeName
,a.AlertId
,a.TargetObject
,a.Raised
,n.NotificationDate
,n.NotificationType
FR...