Activity overview
Latest activity by TonyD
Investigating Common SQL Server Problems using SQL Monitor
Dear FoRGs,
I hope everyone is doing OK! For those that don't know, I'm a content specialist/editor here at Redgate, primarily responsible for our technical product articles (https://www.red-gate....
Yes, true. This is more designed as a way to help you catch the changes you didn't know were coming. Setting up the Agent alert and job step is a little tricky, but it's (hopefully) plain sailing after that. / comments
Yes, true. This is more designed as a way to help you catch the changes you didn't know were coming. Setting up the Agent alert and job step is a little tricky, but it's (hopefully) plain sailing a...
Hi @lmacdonald. We just published an article on our Product learning website that may well suit your requirements. The idea, in brief, is that you include a simple RAISERROR() statement in the SQL batch that makes the change. A SQL Agent alerts detects it, and runs a job that uses the new API to send a message to SQL Monitor and annotate the Overview graph for the server affected by the change. Here's the link to the article: https://www.red-gate.com/hub/product-learning/sql-monitor/tagging-sql-server-changes-in-sql-monitor. Yes, I confess, I 'borrowed' your forum post title and used it for the article! It would be great to know if this works for you, or what you'd need instead. Best, Tony. / comments
Hi @lmacdonald. We just published an article on our Product learning website that may well suit your requirements. The idea, in brief, is that you include a simple RAISERROR() statement in the SQL ...
Writing opportunity: Help fellow users master SQL Clone
Dear Friends,
We're recently released SQL Clone v4, which introduces a
feature called Teams that allows administrators to control of data
security and access control, and then allow users the free...
@Nick_Foster - if you need a scripted solution, we just published a 'how-to' article on Product Learning that might help. It uses SQL Change Automation pre-deployment scripts to create 'stubs' of any cross-database references where the objects don't yet exist. It doesn't require any changes to the source scripts themselves. See: Database Build Blockers: Mutually Dependent Databases / comments
@Nick_Foster - if you need a scripted solution, we just published a 'how-to' article on Product Learning that might help. It uses SQL Change Automation pre-deployment scripts to create 'stubs' of a...
@TheMatelix: many thanks for your response (and sorry for taking a while to get back to you). So I suppose part of what I wanted to understand was, if you need 5 (say) development/test copies of what (in production) is a multi-terabyte database, what's your process for setting up the SQL Server instances and databases for dev and test work? Does it involve use of containers? I'm assuming not, from what you say above. / comments
@TheMatelix: many thanks for your response (and sorry for taking a while to get back to you). So I suppose part of what I wanted to understand was, if you need 5 (say) development/test copies of wh...
@ben_b. Thanks for that - i now have a new rrc snippet (report row count)! So, on the topic of a consistent naming convention for snippets, which will be important if we're building out a more extensive library, what do people think? One proposal so far (courtesy of @Phil_Fact0r) is that snippets always start with a verb describing the action: alter, add, change, create, enable, modify, drop, disable, insert, create, check, execute, find, report. Then you identify the target object using the standard short code:
AF = Aggregate function (CLR)
C = CHECK constraint
D = DEFAULT (constraint or stand-alone)
F = FOREIGN KEY constraint
FN = SQL scalar function
FS = Assembly (CLR) scalar-function
FT = Assembly (CLR) table-valued function
IF = SQL inline table-valued function
IT = Internal table
P = SQL Stored Procedure
PC = Assembly (CLR) stored-procedure
PG = Plan guide
PK = PRIMARY KEY constraint
R = Rule (old-style, stand-alone)
RF = Replication-filter-procedure
S = System base table
SN = Synonym
SO = Sequence object
U = Table (user-defined)
V = View
EC = Edge constraint
SQ = Service queue
TA = Assembly (CLR) DML trigger
TF = SQL table-valued-function
TR = SQL DML trigger
TT = Table type
UQ = UNIQUE constraint
X = Extended stored procedure
ET = External Table
So, cTT (create table type), chXA (change xact-abort setting) and so on. Thoughts? / comments
@ben_b. Thanks for that - i now have a new rrc snippet (report row count)! So, on the topic of a consistent naming convention for snippets, which will be important if we're building out a more ext...
There are some odd ones in there - "neo" can go for starters. / comments
There are some odd ones in there - "neo" can go for starters.
Working with containers for development and testing
Hello Friends!
How many of you are actively using Containers for your development
and test work for your applications and/or databases? I'd love to hear about
the sorts of apps and services you're...
Hey Tim, thanks for your response - and good to hear from you. Hope all is well! Yes, I think most people just save the snippets they really need, for those times when someone is standing over your shoulder in a "is it fixed yet?" kind of way. I think our idea was that while SSMS templates are grouped by type of object, the Prompt Snippet library would be organized into different types of development task. Consistent naming is actually an interesting issue is we attempt to expand the snippet library - I'm forever forgetting the shortcut/initialism I've given a snippet. / comments
Hey Tim, thanks for your response - and good to hear from you. Hope all is well! Yes, I think most people just save the snippets they really need, for those times when someone is standing over your...