In SQL Server, you can use the CREATE TRIGGER statement to create a trigger.
A trigger is a special type of stored procedure that automatically runs when an event occurs in the database server.
You can create a DML trigger, a DDL trigger, or a logon trigger.
This article provides an example of creating a DML trigger.
SQL Server supports partitioned tables and indexes. When a partitioned table or index is partitioned, its data is divided into units that can be spread across more than one filegroup.
Therefore, to create a partitioned table in SQL Server, you first need to create the filegroup/s that will hold each partition. You also need to create a partition function and a partition scheme.
So it goes like this:
Below is an example of using these steps to create a table with four partitions.
SQL Server’s Database Mail has a stored procedure called sp_send_dbmail that you can use to send emails from SQL Server.
By default, emails are sent as text, but you can easily change this, so that they’re sent in HTML format.
The @body_format argument is what you use to switch over to HTML format.
If you’re using Database Mail in SQL Server, you may occasionally need to stop or start the mail queue.
You can do this with T-SQL by using the sysmail_stop_sp stored procedure to stop the queue, and the sysmail_start_sp procedure to start it.
If you’ve ever used SQL Server’s Database Mail to email the results of a query, you might have noticed that the results are separated by a space by default.
This is fine if you want a space-separated result set, but what if you want it to be comma-separated?
Fortunately you can use the @query_result_separator argument to do just that. You can use this argument to specify any separator (as long as it’s a char(1)).
When you use the sp_send_dbmail stored procedure to send emails from SQL Server, you have the option of adding query results to the email.
When you do this, you might find that unwanted padding has been added to some columns. Fortunately, you can eliminate this padding with the @query_result_no_padding argument.
When you use the sp_send_dbmail stored procedure to send emails in SQL Server, you would typically include the @profile_name argument to specify which profile to use.
However, if you omit this argument, sp_send_dbmail will use the default private profile for the current user. If the user does not have a default private profile, sp_send_dbmail will use the default public profile for the msdb database.
If none of these are configured, you’ll get the following error:
If you’ve already created an association between a principal and a Database Mail profile, but you now want to change whether the profile is the default profile for that user, you can do that with the sysmail_update_principalprofile_sp stored procedure.
When doing this, you need to provide the name or ID of both the user and the profile. This is because you need to specify exactly which profile/principal association you want to update.
If you’ve already added a Database Mail account to a profile, but you now want to change the sequence number, you can do that with the sysmail_update_profileaccount_sp stored procedure.
When doing this, you need to provide the name or ID of both the account and the profile. This is because you need to specify exactly which profile/account association you want to update.
In SQL Server, you can use the sysmail_help_profileaccount_sp stored procedure on the msdb database to retrieve a list of all associations between accounts and Database Mail profiles.
You can also return account info based on the account name/ID or the profile name/ID.