In SQL Server, you may encounter such an error in some cases.

You can solve this error by using the code below.

USE master;
ALTER DATABASE Old_Database_Name SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
ALTER DATABASE Old_Database_Name MODIFY NAME = [New_Database_Name];
ALTER DATABASE Old_Database_Name SET MULTI_USER;

Good luck to everyone in business and life.

The post Supply a Valid Database Name in SQL Server. To See Available Databases, Use Sys.Databases Error first appeared on MSSQL Query.

When you restore from backup in SQL Server, when you restore to a different server, you may get such an error because the user record does not match.

To fix the user and login mapping, you need to open a query window in SQL Server Management Studio and run the following code on the relevant database.

USE [IslemYapacaginizVeritabaniAdi]
EXEC sp_change_users_login 'Auto_Fix','VeritabaniKullaniciAdi'

Good luck to everyone in business and life.

The post Error 15023 in SQL Server first appeared on MSSQL Query.

In certain situations, you might want to list all the running jobs in SQL Server.

You can easily perform this operation with the help of the code below:

SELECT database_name,
       notify_level_email,
       name,
       enabled,
       description,
       step_name,
       command
FROM msdb.dbo.sysjobs job
    INNER JOIN msdb.dbo.sysjobsteps steps
        ON job.job_id = steps.job_id
WHERE job.enabled = 1;

When you execute the above code, you will see a result similar to the following:

As you can see, all jobs have been listed.

Wishing everyone success and ease in their professional and personal lives.

The post Listing All Jobs Running in SQL Server first appeared on MSSQL Query.

In SQL Server you may want to convert XML to table in some cases.

You can easily do this by revising the sample code below.

DECLARE @TempTablo TABLE (
	KullaniciId INT
   ,KullaniciAdi NVARCHAR(50)
   ,Sifre NVARCHAR(50)
)
DECLARE @xml XML
SET @xml = '
<row KullaniciId="1" KullaniciAdi="Yavuz" Sifre="1234" />
<row KullaniciId="2" KullaniciAdi="Selim" Sifre="5678" />'

INSERT INTO @TempTablo
	SELECT
		Tbl.Col.value('@KullaniciId', 'INT')
	   ,Tbl.Col.value('@KullaniciAdi', 'NVARCHAR(50)')
	   ,Tbl.Col.value('@Sifre', 'NVARCHAR(50)')
	FROM @xml.nodes('//row') Tbl (Col)

SELECT
	*
FROM @TempTablo

When you run the above code, you will see a result similar to the one below.

As you can see, we have converted the XML into a table.

Good luck to everyone in business and life.

The post Converting XML to Table in SQL Server first appeared on MSSQL Query.

In SQL Server, in some cases, you may want to clear the backup history and job history.

SQL Server keeps track of every backup and restore it performs. This information is recorded in the tables below.

msdb.dbo.backupfile
msdb.dbo.backupfilegroup
msdb.dbo.backupmediafamily
msdb.dbo.backupmediaset
msdb.dbo.backupset
msdb.dbo.restorefile
msdb.dbo.restorefilegroup
msdb.dbo.restorehistory

There is no automatic cleanup of backup and restore records in SQL Server, but cleaning these records can become important over time.

Before upgrading SQL Server, if any of these tables exceed 10,000 rows this may cause the upgrade to hang, so it is recommended to delete old records.

You can run the procedure called sp_delete_backuphistory to reduce the rows in all these tables. This procedure deletes all backup and restore history information for backup sets older than a specified date. An example is shown below.

EXEC msdb..sp_delete_backuphistory '20231201 12:00:00.000'

Similarly, you can revise the example below for yourself to remove records from msdb.dbo.sysjobhistory.

EXEC msdb..sp_purge_jobhistory @oldest_date = '20231201 12:00:00.000'

You can set up a Job to clear these tables, but you’ll have to put some thought into how often you need to clear them.

Good luck to everyone in business and life.

The post How to Clear Backup History and Job History in SQL Server? first appeared on MSSQL Query.

There is a small but useful new feature for creating Views with SQL Server 2016 SP1. OR ALTER statement. If you add this statement to your code to create the View, SQL Server will know whether it needs to run a CREATE or ALTER statement.

Below you can see a Vew example created for the Adventureworks database.

CREATE OR ALTER VIEW EmployeeReport
AS
SELECT 
	p.FirstName, 
	p.MiddleName, 
	p.LastName, 
	e.HireDate, 
	e.JobTitle
FROM Person.Person p
JOIN HumanResources.Employee e 
	ON p.BusinessEntityID = e.BusinessEntityID

This feature is especially useful when gradually developing your Views. You can focus on the change in View and no need to switch between CREATE and ALTER.

Good luck to everyone in business and life.

The post Using CREATE or ALTER View in SQL Server first appeared on MSSQL Query.

In SQL Server, in some cases, you may have to use the Geography data type.

The data type that allows us to keep the coordinates in SQL Server is the Geography data type.

Besides this service, SQL Server also offers methods that allow us to perform some operations on these coordinates. You can see an example usage below.

DECLARE @geo_istanbul geography
SET @geo_istanbul = geography::Point(41.010467,28.939179 , 4326)
SELECT @geo_istanbul

Point(Latitude, Longitude, SRID) gives us the coordinates of a point on the earth. The variables inside the point are latitude, longitude and SRID, respectively.

SRID is a reference, it tells us whether the system is planar or like the shape of the earth. The 4326 we use is the one used in normal GPS systems. We will always use it.

You may think that we can’t write the “Point(41.010467,28.939179 , 4326)” part, which you see directly above, on the table, but unfortunately you need to make a definition as above. The reason for this is that this system stores data of the Geography type as binary in the database.

In the example below, you can see how to add a Geography data type to a table.

IF OBJECT_ID('tempdb..#GeoTest') IS NOT NULL
    DROP TABLE #GeoTest
CREATE TABLE #GeoTest ([CoordinateLocation] [geography] NULL);
INSERT INTO #GeoTest (CoordinateLocation)
SELECT GEOGRAPHY::STPointFromText('POINT(41.010467 28.939179)', 4326);
SELECT *
FROM #GeoTest;

The method we can use the most is the STDistance() method. This method calculates the distance between two points on the earth. You can see an example on this subject below.

DECLARE @istanbul geography, @izmir geography
SET @istanbul = GEOGRAPHY::STPointFromText('POINT(41.00527 28.97696)', 4326)
SET @izmir = GEOGRAPHY::STPointFromText('POINT(38.41885  27.12872)', 4326)
SELECT @istanbul.STDistance (@izmir)/1000

Those who wish

They can check it from https://www.meridianoutpost.com/resources/etools/calculators/calculator-latitude-longitude-distance.php

Good luck to everyone in business and life.

The post Using the Geography Data Type in SQL Server first appeared on MSSQL Query.

In SQL Server you may want to calculate the time between two rows in some cases.

You can easily do this by revising the sample code below.

--Tablonun oluşturulması

CREATE TABLE TestTable(
Id INT PRIMARY KEY IDENTITY(1,1),
IslemId INT,
Durum NVARCHAR(20),
Tarih DATETIME
)


--Tabloya veri eklenmesi

INSERT INTO TestTable (IslemId, Durum, Tarih)
	VALUES (100, N'Başladı', '2022-08-01 08:00:00.000'),
	(101, N'Başladı', '2022-08-02 07:30:00.000'),
	(100, N'Durdu', '2022-08-03 17:00:00.000'),
	(102, N'Başladı', '2022-08-04 08:00:00.000'),
	(102, N'Durdu', '2022-08-04 17:00:00.000'),
	(101, N'Durdu', '2022-08-05 18:00:00.000')

-- Tablonun kontrol edilmesi

SELECT * FROM TestTable

--İki satır arasındaki süreyi hesaplamak

SELECT
	IslemId, 
	CONVERT(DATE, testTablosu.Tarih) AS 'Başlama Zamanı',
	CONVERT(DATE, taskEnd.Tarih) AS 'Bitiş Zamanı',
	DATEDIFF(day, testTablosu.Tarih, taskEnd.Tarih) as 'Gün Farkı'
FROM TestTable testTablosu
OUTER APPLY (
	SELECT TOP(1)
		taskEnd.Tarih
	FROM TestTable taskEnd
	WHERE 
		taskEnd.Tarih > testTablosu.Tarih
		AND taskEnd.Durum = 'Durdu'
		AND taskEnd.IslemId = testTablosu.IslemId
	ORDER BY Tarih
	) taskEnd
WHERE
	testTablosu.Durum = 'Başladı'

When you create the table above and run the relevant codes, you will get a result as follows.

As you can see, we have calculated the time between two lines.

Good luck to everyone in business and life.

The post Calculating Time Between Two Rows in SQL Server first appeared on MSSQL Query.

In SQL Server, in some cases you may want to list the largest tables and Indexes in the database.

You can easily do this using the code below.

Listing the Largest Tables

SELECT TOP 100
	s.[name] AS [schema]
   ,t.[name] AS [table_name]
   ,p.[rows] AS [row_count]
   ,CAST(ROUND(((SUM(a.total_pages) * 8) / 1024.00), 2) AS NUMERIC(36, 2)) AS [size_mb]
   ,CAST(ROUND(((SUM(a.used_pages) * 8) / 1024.00), 2) AS NUMERIC(36, 2)) AS [used_mb]
   ,CAST(ROUND(((SUM(a.total_pages) - SUM(a.used_pages)) * 8) / 1024.00, 2) AS NUMERIC(36, 2)) AS [unused_mb]
FROM sys.tables t
JOIN sys.indexes i
	ON t.[object_id] = i.[object_id]
JOIN sys.partitions p
	ON i.[object_id] = p.[object_id]
		AND i.index_id = p.index_id
JOIN sys.allocation_units a
	ON p.[partition_id] = a.container_id
LEFT JOIN sys.schemas s
	ON t.[schema_id] = s.[schema_id]
WHERE t.is_ms_shipped = 0
AND i.[object_id] > 255
GROUP BY t.[name]
		,s.[name]
		,p.[rows]
ORDER BY [size_mb] DESC

Listing the Biggest Indexes

SELECT TOP(100)
    s.[name] AS [schema],
    t.[name] AS [table_name],
    i.[name] AS [index_name],
    i.[type_desc],
    p.[rows] AS [row_count],
    CAST(ROUND(((SUM(a.total_pages) * 8) / 1024.00), 2) AS NUMERIC(36, 2)) AS [size_mb],
    CAST(ROUND(((SUM(a.used_pages) * 8) / 1024.00), 2) AS NUMERIC(36, 2)) AS [used_mb], 
    CAST(ROUND(((SUM(a.total_pages) - SUM(a.used_pages)) * 8) / 1024.00, 2) AS NUMERIC(36, 2)) AS [unused_mb]
FROM
    sys.tables t
    JOIN sys.indexes i ON t.[object_id] = i.[object_id]
    JOIN sys.partitions p ON i.[object_id] = p.[object_id] AND i.index_id = p.index_id
    JOIN sys.allocation_units a ON p.[partition_id] = a.container_id
    LEFT JOIN sys.schemas s ON t.[schema_id] = s.[schema_id]
WHERE 
    t.is_ms_shipped = 0
    AND i.[object_id] > 255 
GROUP BY
    t.[name], 
    s.[name],
    i.[name],
    i.[type_desc],
    p.[rows]
ORDER BY 
    [size_mb] DESC

Good luck to everyone in business and life.

The post Listing Largest Tables and Indexes in Database in SQL Server first appeared on MSSQL Query.

In SQL Server, in some cases, you may want to print the initials of the words of a given sentence side by side.

You can easily do this using the function below.

CREATE FUNCTION [dbo].[fn_Cumle_Bas_Harfi_Alma] ( @cumle NVARCHAR(4000) )
RETURNS NVARCHAR(2000)
AS
BEGIN
    DECLARE @donensonuc NVARCHAR(2000);

    SET @cumle=RTRIM(LTRIM(@cumle));
    SET @donensonuc=LEFT(@cumle,1);

    WHILE CHARINDEX(' ',@cumle,1)>0 BEGIN
        SET @cumle=LTRIM(RIGHT(@cumle,LEN(@cumle)-CHARINDEX(' ',@cumle,1)));
        SET @donensonuc+=LEFT(@cumle,1);
    END

    RETURN @donensonuc;
END
GO


--Using the Function

SELECT dbo.fn_Cumle_Bas_Harfi_Alma('Yavuz Selim Kart') AS SadeceBasHarfler

When you create and run the above function, you will see a result similar to the one below.

As you can see, we have written the initials of the word.

Good luck to everyone in business and life.

The post Function to Print Words Side by Side in SQL Server first appeared on MSSQL Query.

In SQL Server you may want to get the second word in the given sentence in some cases.

You can easily do this using the code below.

DECLARE @Cumle NVARCHAR(264);

SET @Cumle = N'Yavuz Selim Kart';

SELECT LTRIM(SUBSTRING(
                          @Cumle,
                          CHARINDEX(' ', @Cumle),
                          CHARINDEX(
                                       ' ',
                                       LTRIM(SUBSTRING(
                                                          @Cumle,
                                                          CHARINDEX(' ', @Cumle),
                                                          LEN(@Cumle) - CHARINDEX(' ', @Cumle)
                                                      )
                                            )
                                   )
                      )
            );

When you run the above code, you will see a result similar to the one below.

As you can see, we have taken the second word in the given sentence.

Good luck to everyone in business and life.

The post Getting Second Word in Given Sentence in SQL Server first appeared on MSSQL Query.

In SQL Server, in some cases, you may want to convert the VARCHAR type date to dd.mm.yyyy.

You can easily do this using the code below.

DECLARE @tarih VARCHAR(30) = '5.06.2023'
SELECT
	CONVERT(VARCHAR, CONVERT(DATE, @tarih, 104), 104)

When you run the above code, you will see a result similar to the one below.

 

As you can see, we have converted the VARCHAR type date as dd.mm.yyyy.

Good luck to everyone in business and life.

The post Converting VARCHAR Type Date to dd.mm.yyyy in SQL Server first appeared on MSSQL Query.

If you’re programming on the CSharp side, you need Properties.

It can take a lot of time to create a table or view and then create a Property in SQL Server.

Using the procedure below, you can easily create the class structure of your table.

CREATE  PROCEDURE [dbo].[usp_GenerateClassFromViewAndTable]
  @TabloViewAdi NVARCHAR(100),
  @ClassAdi NVARCHAR(100)
AS
BEGIN
declare @Sonuc varchar(max) = 'public class ' + @ClassAdi + '
{'

select @Sonuc = @Sonuc + '
    public ' + ColumnType + NullableSign + ' ' + ColumnName + ' { get; set; }
'
from
(
    select 
        replace(col.name, ' ', '_') ColumnName,
        column_id ColumnId,
        case typ.name 
            when 'bigint' then 'long'
            when 'binary' then 'byte[]'
            when 'bit' then 'bool'
            when 'char' then 'string'
            when 'date' then 'DateTime'
            when 'datetime' then 'DateTime'
            when 'datetime2' then 'DateTime'
            when 'datetimeoffset' then 'DateTimeOffset'
            when 'decimal' then 'decimal'
            when 'float' then 'double'
            when 'image' then 'byte[]'
            when 'int' then 'int'
            when 'money' then 'decimal'
            when 'nchar' then 'string'
            when 'ntext' then 'string'
            when 'numeric' then 'decimal'
            when 'nvarchar' then 'string'
            when 'real' then 'float'
            when 'smalldatetime' then 'DateTime'
            when 'smallint' then 'short'
            when 'smallmoney' then 'decimal'
            when 'text' then 'string'
            when 'time' then 'TimeSpan'
            when 'timestamp' then 'long'
            when 'tinyint' then 'byte'
            when 'uniqueidentifier' then 'Guid'
            when 'varbinary' then 'byte[]'
            when 'varchar' then 'string'
            else 'UNKNOWN_' + typ.name
        end ColumnType,
        case 
            when col.is_nullable = 1 and typ.name in ('bigint', 'bit', 'date', 'datetime', 'datetime2', 'datetimeoffset', 'decimal', 'float', 'int', 'money', 'numeric', 'real', 'smalldatetime', 'smallint', 'smallmoney', 'time', 'tinyint', 'uniqueidentifier') 
            then '?' 
            else '' 
        end NullableSign
    from sys.columns col
        join sys.types typ on
            col.system_type_id = typ.system_type_id AND col.user_type_id = typ.user_type_id
    where object_id = object_id(@TabloViewAdi)
) t
order by ColumnId

set @Sonuc = @Sonuc  + '
}'

PRINT  @Sonuc

END
GO

--Use of the procedure

EXEC usp_GenerateClassFromViewAndTable 
@TabloViewAdi = N'TableViewName' 
,@ClassAdi = N'ClassNameYouWanttoCreate'

Good luck to everyone in business and life.

The post Procedure to Create Property from Tables and Views in SQL Server first appeared on MSSQL Query.

In this article, I will provide information about viewing the size of log files in SQL Server.

In SQL Server we may want to view the size of log files in some cases.

You can easily do this with the help of the code below.

SELECT DB_NAME(mf.database_id) AS 'DB Name',
       name AS 'File Logical Name',
       'File Type' = CASE
                         WHEN type_desc = 'LOG' THEN
                             'Log File'
                         WHEN type_desc = 'ROWS' THEN
                             'Data File'
                         ELSE
                             type_desc
                     END,
       mf.physical_name AS 'File Physical Name',
       size_on_disk_bytes / 1024 AS 'Size(KB)',
       size_on_disk_bytes / 1024 / 1024 AS 'Size(MB)',
       size_on_disk_bytes / 1024 / 1024 / 1024 AS 'Size(GB)'
FROM sys.dm_io_virtual_file_stats(NULL, NULL) AS divfs
    JOIN sys.master_files AS mf
        ON mf.database_id = divfs.database_id
           AND mf.file_id = divfs.file_id
WHERE CASE
          WHEN type_desc = 'LOG' THEN
              'Log File'
          WHEN type_desc = 'ROWS' THEN
              'Data File'
          ELSE
              type_desc
      END = 'Log File'
ORDER BY DB_NAME(mf.database_id);

When you run the code, you will get a result like the one below.

As you can see, the size of the log files is displayed.

Good luck to everyone in business and life.

The post Viewing the Size of Log Files in SQL Server first appeared on MSSQL Query.

In SQL Server, in some cases you may want to list tables by creation date.

You can easily do this using the code below.

SELECT
	name
   ,create_date
FROM sys.tables
ORDER BY create_date DESC

Good luck to everyone in business and life.

The post Listing Tables by Creation Date in SQL Server first appeared on MSSQL Query.

In SQL Server, the PRINT statement prints up to 4000 characters. So what will you do if the content of the dynamic queries you write is longer than 4000 characters?

In SQL Server, in some cases, you may want to PRINT statements with more than 4000 characters.

You can easily do this using the procedure below.

CREATE PROCEDURE LONGPRINT
    @String NVARCHAR(MAX)
AS
BEGIN
    BEGIN TRY

    DECLARE @CurrentEnd BIGINT;
    DECLARE @Offset TINYINT; 
    SET @String = replace(replace(@String, CHAR(13) + CHAR(10), CHAR(10)), CHAR(13), CHAR(10))

    WHILE LEN(@String) > 1
    BEGIN
        IF CHARINDEX(CHAR(10), @String) BETWEEN 1 AND 4000
        BEGIN
            SET @CurrentEnd =  CHARINDEX(CHAR(10), @String) -1
            SET @Offset = 2
        END
        ELSE
        BEGIN
            SET @CurrentEnd = 4000
            SET @Offset = 1
        END   
        PRINT SUBSTRING(@String, 1, @CurrentEnd) 
        SET @String = SUBSTRING(@String, @CurrentEnd + @Offset, LEN(@String))   
    END 
    END TRY
    BEGIN CATCH
        DECLARE @ErrorMessage VARCHAR(4000)
        SELECT @ErrorMessage = ERROR_MESSAGE()    
        RAISERROR(@ErrorMessage,16,1)
    END CATCH
END

--Use of the Procedure

DECLARE @Degisken VARCHAR(MAX)
SET @Degisken = REPLICATE('x', 6000)
EXEC LONGPRINT @Degisken

When you create the above procedure and run the code, you will see a result similar to the one below.

As you can see, we have printed 6000 characters with the LONGPRINT procedure.

Good luck to everyone in business and life.

The post Customized PRINT Procedure in SQL Server first appeared on MSSQL Query.

Most people tend to prefix “sp_” to the name of the Stored Procedure when creating a Stored Procedure in SQL Server.

There are several reasons why this is considered bad practice.

Microsoft says you shouldn’t do this.

You can read Microsoft’s statement below.

Avoid using the sp_ prefix when naming Stored Procedures. This prefix is used by Microsoft SQL Server to identify system procedures. Using the prefix can break the application code if there is a system procedure with the same name.

This means that if you accidentally name your Stored Procedure with the same name as one of SQL Server’s Stored Procedure, your Stored Procedure will not be called. Instead, the SQL Server System Stored Procedure is called.

For example, if you have created a Stored Procedure named “sp_configure” in your database, it will never be executed when you call it because there is a system Stored Procedure named “sp_configure” in the master database and will be called instead.

Second, when SQL Server sees the prefix “sp_” at the beginning of a Stored Procedure, it first tries to find that procedure in the master database. As stated in the Microsoft documentation above, ” This prefix is used by SQL Server to denote system procedures “, so when SQL Server sees the phrase “sp_” prefix, it starts searching for system procedures. But after searching all the procedures in the master database and determining that your procedure is not there, it will return to your database to try to find the stored procedure.

As noted in the above post, procedures named with the “sp_” prefix will run slower. Of course, this may not always be noticed.

There are times when the above situation is an exception.

Use DatabaseOrnek 
EXEC dbo.sp_configure

ile

Use DatabaseOrnek 
EXEC DatabaseOrnek.dbo.sp_configure

The second example will call your procedure correctly.

But for this to work, you have to call it like (databasename.semaname.procedure) every time.

Unless you are intentionally creating a Stored Procedure in the SQL Server system database, there is no valid reason to name the Stored Procedure with the “sp_” prefix. It is not very convenient to send SQL Server to wrong database to find Stored Procedure. It’s confusing, inefficient, and can cause performance issues. So why take the risk? To help maintain peak performance of your databases, avoid using the “sp_” prefix in your Stored Procedure names.

Good luck to everyone in business and life.

The post Why You Shouldn’t Prefix “sp_” Before Your Stored Procedures in SQL Server? first appeared on MSSQL Query.

In SQL Server you may want to list all supported collations in some cases.

You can easily do this using the query below.

SELECT name,
       COLLATIONPROPERTY(name, 'CodePage') AS Code_Page,
       description
FROM sys.fn_HelpCollations();

Good luck to everyone in business and life.

The post Listing All Collations Supported in SQL Server first appeared on MSSQL Query.

In SQL Server, in some cases, when you change the Collation of the database, the Collation may not change in the columns and you may want to change the Collation of all columns.

You can easily do this using the query below.

DECLARE @collate NVARCHAR(100);
DECLARE @table NVARCHAR(255);
DECLARE @column_name NVARCHAR(255);
DECLARE @column_id INT;
DECLARE @data_type NVARCHAR(255);
DECLARE @max_length INT;
DECLARE @row_id INT;
DECLARE @sql NVARCHAR(MAX);
DECLARE @sql_column NVARCHAR(MAX);

SET @collate = N'Turkish_CI_AI';

DECLARE local_table_cursor CURSOR FOR
SELECT [name]
FROM sysobjects
WHERE OBJECTPROPERTY(id, N'IsUserTable') = 1;

OPEN local_table_cursor;
FETCH NEXT FROM local_table_cursor
INTO @table;

WHILE @@FETCH_STATUS = 0
BEGIN

    DECLARE local_change_cursor CURSOR FOR
    SELECT ROW_NUMBER() OVER (ORDER BY c.column_id) AS row_id,
           c.name column_name,
           t.Name data_type,
           c.max_length,
           c.column_id
    FROM sys.columns c
        JOIN sys.types t
            ON c.system_type_id = t.system_type_id
        LEFT OUTER JOIN sys.index_columns ic
            ON ic.object_id = c.object_id
               AND ic.column_id = c.column_id
        LEFT OUTER JOIN sys.indexes i
            ON ic.object_id = i.object_id
               AND ic.index_id = i.index_id
    WHERE c.object_id = OBJECT_ID(@table)
    ORDER BY c.column_id;

    OPEN local_change_cursor;
    FETCH NEXT FROM local_change_cursor
    INTO @row_id,
         @column_name,
         @data_type,
         @max_length,
         @column_id;

    WHILE @@FETCH_STATUS = 0
    BEGIN

        IF (@max_length = -1)
            SET @max_length = 4000;

        IF (@data_type LIKE '%char%')
        BEGIN TRY
            SET @sql
                = N'ALTER TABLE ' + @table + N' ALTER COLUMN ' + @column_name + N' ' + @data_type + N'('
                  + CAST(@max_length AS NVARCHAR(100)) + N') COLLATE ' + @collate;
            PRINT @sql;
            EXEC sp_executesql @sql;
        END TRY
        BEGIN CATCH
            PRINT 'ERROR: Some index or contraint rely on the column' + @column_name + '. No conversion possible.';
            PRINT @sql;
        END CATCH;

        FETCH NEXT FROM local_change_cursor
        INTO @row_id,
             @column_name,
             @data_type,
             @max_length,
             @column_id;

    END;

    CLOSE local_change_cursor;
    DEALLOCATE local_change_cursor;

    FETCH NEXT FROM local_table_cursor
    INTO @table;

END;

CLOSE local_table_cursor;
DEALLOCATE local_table_cursor;

GO

Good luck to everyone in business and life.

The post Changing Collation of All Columns in SQL Server first appeared on MSSQL Query.

In SQL Server you may need to use DROP IF EXISTS in some cases.

You can easily do this using the code below.

Note: The commands below work on SQL Server 2016 and above.

1 -) Drop a Table

DROP TABLE IF EXISTS dbo.TableName;

2 -) Drop a View

DROP VIEW IF EXISTS ViewName;

3 -) Drop a Index

DROP INDEX IF EXISTS my_index ON IndexName;

4 -) Drop a Procedure

DROP PROCEDURE IF EXISTS ProcedureName;

5 -) Drop a Function

DROP FUNCTION IF EXISTS FunctionName;

6 -) Drop a Schema

DROP SCHEMA IF EXISTS SchemaName;

7 -) Drop a Trigger

DROP TRIGGER IF EXISTS my_trigger ON TriggerName

8 -) Drop a Foreign Key

ALTER TABLE TabloName
DROP CONSTRAINT IF EXISTS ForeignKeyName;

9 -) Drop a User

DROP USER IF EXISTS UserName;

The above examples show different usage scenarios of “DROP IF EXISTS” command in SQL Server. These commands are useful for checking objects for existence before deleting them and reduce the chance of errors when writing code.

Good luck to everyone in business and life.

The post All Uses of DROP IF EXISTS in SQL Server first appeared on MSSQL Query.