SQL Server Agent schedules can be managed independently of jobs. This means you can update the schedule directly without updating the job itself.
You can do this with the sp_update_schedule stored procedure.
t-sql
sp_add_schedule vs sp_add_jobschedule in SQL Server: What’s the Difference?
If you’re in the process of creating a SQL Server Agent job with T-SQL, you may be wondering whether to create its schedule with the sp_add_schedule stored procedure or the sp_add_jobschedule procedure.
Here’s a quick explanation of the difference between these two procedures.
Create a SQL Server Agent Job using T-SQL
SQL Server Agent is a Microsoft Windows service that executes scheduled administrative tasks, which are called jobs in SQL Server.
T-SQL includes a large collection of stored procedures that deal with SQL Server Agent jobs.
Here, we’ll use some of them to create and schedule a SQL Server Agent job.
You can also create SQL Server Agent jobs via the GUI (in SSMS) if you prefer.
How to Run a SQL Server Agent Job using T-SQL
When you first create a SQL Server Agent job, you might want to do a quick test to see if it’s going to actually run without any issues.
This is quite straightforward when using the SSMS GUI, but how do you do it in T-SQL?
Answer: The sp_start_job stored procedure.
SQL Server Error 206: Operand type clash
SQL Server error Msg 206, Level 16 is a common error to get when inserting data into a table.
It happens when you’re trying to insert data into a column that is incompatible with the data type you’re trying to insert.
This could happen if you accidentally try to insert data into the wrong column (or even the wrong table). But it could also happen if you incorrectly assume that SQL Server will convert the data for you.
To fix this issue, make sure you’re inserting the correct data type.
How to Map Multiple Partitions to a Single Filegroup in SQL Server (T-SQL)
If you’re familiar with creating partitioned tables in SQL Server, you might be used to creating a separate filegroup for each partition. This has its benefits, and may very well be the method you would choose in most scenarios.
However, you also have the option of mapping multiple partitions to a single filegroup.
In this article I share two examples of mapping multiple partitions to a single filegroup.
- Example 1 maps all partitions to a single filegroup.
- Example 2 maps some partitions to one filegroup, and some to another.
Find Out Which Partition a Given Value Would be Mapped to in SQL Server (T-SQL)
If you have a partitioned table or index in SQL Server, and you want to determine which partition a given value would be mapped to, you can do this nice and quickly with the $PARTITION system function.
All you need to know is the name of the partition function (and of course, the value you’re interested in).
How to Fix “Conversion failed when converting the value to data type” in SQL Server
SQL Server error Msg 245, Level 16 tells us that there was a problem when trying to convert a value to a specific data type.
You’ll get this error if you try to insert the wrong data type into a column.
To fix this issue, make sure the data type of the value you’re trying to insert, matches the column’s type.
3 Ways to Return the Number of Rows in Each Partition in SQL Server (T-SQL)
If you’ve previously created a partitioned table in SQL Server, and you now want to know how many rows are being stored in each partition, here are three queries you can use.
In particular, you can:
- Query the
sys.dm_db_partition_statsview - Query the
sys.partitionsview - Use the
$PARTITIONfunction in a query
Below are examples of all three.
Execute a Trigger Only When Certain Columns are Updated (SQL Server)
SQL Server has the UPDATE() function that you can use within your DML triggers to check whether or not a specific column has been updated.
While this function only accepts one column, there’s nothing to stop you from including multiple UPDATE() clauses with AND or OR to test for multiple column updates.