T-SQL: Get only Date from DateTime

Sadece tarih bilgisidir.... Saat, dakika, saniye hep 0

SELECT DATEADD(dd, 0, DATEDIFF(dd, 0, GETDATE()))
2009-01-16 00:00:00.000







SQL SERVER - Tek insert into ile birden fazla kayıt girebilmek - UNION ALL kullanımı

Ref:http://blog.sqlauthority.com/2007/06/08/sql-server-insert-multiple-records-using-one-insert-statement-use-of-union-all/

UNION
UNION ilişkili tabloların aynı tipte verileri olması kaydıyla DISTINCT ile getirmesidir. JOIN lemesi gibi.

UNION ALL
UNION ALL, UNION komutuna eşittir bir farkla, o da tüm değerleri seçmesi.

Union all çiftlenmiş kayıtlarıda getirir. Tüm kayıtlarını getirir ve tablolarını birleştirir.

A UNION komutu SELECT DISTINCT sonucunu getirir. Eğer tüm satırların eşsiz olarak ayrıştığını biliyorsanız UNION ALL kullanın, çünkü daha hızlıdır.

Örneğin:
Table 1 : First,Second,Third,Fourth,Fifth
Table 2 : First,Second,Fifth,Sixth

Result Set:
UNION: First,Second,Third,Fourth,Fifth,Sixth (This will remove duplicate values)
UNION ALL: First,First,Second,Second,Third,Fourth,Fifth,Fifth,Sixth,Sixth (This will repeat values)


USE YourDB
GO
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('First',1);
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('Second',2);
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('Third',3);
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('Fourth',4);
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('Fifth',5);
GO


yerine

USE YourDB
GO
INSERT INTO MyTable  (FirstCol, SecondCol)
    SELECT  'First' ,1
    UNION ALL
SELECT  'Second' ,2
    UNION ALL
SELECT  'Third' ,3
    UNION ALL
SELECT  'Fourth' ,4
    UNION ALL
SELECT  'Fifth' ,5
GO


sonuç:
INSERT : 5 saniye
INSERT SELECT UNION ALL : 40 milisaniye

SELECT INTO

Ref:reference

USE YourDB
GO
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('First',1);
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('Second',2);
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('Third',3);
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('Fourth',4);
INSERT INTO MyTable  (FirstCol, SecondCol)
        VALUES ('Fifth',5);
GO

INSERT INTO SELECT

Ref: http://blog.sqlauthority.com/2007/06/08/sql-server-insert-multiple-records-using-one-insert-statement-use-of-union-all/

USE AdventureWorks
GO
    ----Create TestTable
CREATE TABLE TestTable (FirstName VARCHAR(100), LastName VARCHAR(100))
    ----INSERT INTO TestTable using SELECT
INSERT INTO TestTable (FirstName, LastName)
    SELECT FirstName, LastName
    FROM Person.Contact
    WHERE EmailPromotion = 2
    ----Verify that Data in TestTable
SELECT FirstName, LastName
    FROM TestTable
    ----Clean Up Database
DROP TABLE TestTable
GO

Cannot resolve the collation conflict between “SQL_Latin1_General_CP1254_CI_AS” and “Turkish_CS_AI” in the equal to operation

ALTER DATABASE kanTahlilleri_new COLLATE SQL_Latin1_General_CP1254_CI_AS

Kaynak: http://www.ahmetkaymaz.com/2006/12/29/sql-serverde-language-ve-collation-kavrami/

select ilce.Ilce_text+‘/’+Il.Il_text
from Il_kodlarI Il
left join Ilce_kodu ilce on ilce.Il_kodu = Il.Il_kodu
collate Turkish_CS_AI

MSSQL 2005 Hata Yakalama TRY CATCH

BEGIN TRY

select 1/0

END TRY
BEGIN CATCH

-- Hatayı görüntüleyelim
SELECT
ERROR_NUMBER() AS HATANUMARASI
,ERROR_MESSAGE() AS HATAMESAJ
,ERROR_SEVERITY() AS ONEM
,ERROR_STATE() AS DURUM

-- Hatayı tabloya yazalım
INSERT INTO Errors
SELECT ERROR_NUMBER()
,ERROR_MESSAGE()
,ERROR_STATE()
,ERROR_SEVERITY()

END CATCH


ERROR_NUMBER() : Oluşan hatanın kodunu verir
ERROR_MESSAGE() : Oluşan hatanın tam metnini verir. Bu hata mesajı hatanın parametreleri, açıklaması, zamanlaması gibi bilgileri içerir.
ERROR_SEVERITY() : Hatanın önem derecesini bildirir
ERROR_STATE() : Hatanın durum numarasını döndürür.
ERROR_LINE() : Hatanın oluştuğu satırı bildirir.
ERROR_PROCEDURE() : Hatanın oluştuğu stored procedure’un veya trigger’ın adını döndürür

SQL 2005 ile database olaylarını izlemek. Loglama

Original:http://www.simple-talk.com/content/print.aspx?article=396

SQL Server 2005 DDL Trigger Workbench

25 May 2007

by Robyn Page and Phil Factor

/* How about automatically tracking and logging all database changes, 
including changes to tables, views, routines, queues and so on? With SQL
Server 2005 it isn't that hard, and we'll show how it is done. If you 
haven't got SQL Server 2005, then get SQL Server Express for free. It 
works on that! While we're about it, we'll show you how to track all
additions, changes and deletions of Logins and Database Users, using
a similar technique.

Contents
   Logging all changes to the database with source code.
   Preventing changes to database objects,
   Logging all changes to the Logins and database users,
   Further reading 
 

Logging all changes to the database with source code.
-----------------------------------------------------

To start off, we'll write a simple trigger that tracks all database 
events. This will include creating, altering or dropping an 
APPLICATION_ROLE, ASSEMBLY, AUTHORIZATION_DATABASE, CERTIFICATE, 
CONTRACT, FUNCTION, INDEX, MESSAGE_TYPE, PARTITION_FUNCTION, 
PARTITION_SCHEME, PROCEDURE, QUEUE, REMOTE_SERVICE_BINDING,
ROLE, ROUTE, SCHEMA, SERVICE, STATISTICS, TABLE, TRIGGER, USER, 
VIEW,  or XML_SCHEMA_COLLECTION. It will also record the creation, 
or dropping of an EVENT_NOTIFICATION, SYNONYM, or TYPE and track 
all GRANT_DATABASE, DENY_DATABASE, and REVOKE_DATABASE DDL.

The new DDL triggers work very like the DML triggers you know and love.
The most radical change is that the details of the event that fired the 
trigger are available only in XML format. You have to get serious with 
XPath queries to extract the XML which is in the format...

<EVENT_INSTANCE>
    <EventType>type</EventType>
    <PostTime>date-time</PostTime>
    <SPID>spid</SPID>
    <ServerName>name</ServerName>
    <LoginName>name</LoginName>
    <UserName>name</UserName>
    <DatabaseName>name</DatabaseName>
    <SchemaName>name</SchemaName>
    <ObjectName>name</ObjectName>
    <ObjectType>type</ObjectType>
    <TSQLCommand>command</TSQLCommand>
</EVENT_INSTANCE>
*/

--Before you do anything else, create a database called TestLogging

USE [TestLogging]
GO
/*now we will create a table that will be a change log. We will put 
in it the detail of each DDL SQL Statement and the user that did it.
We'll trap the login and the original login just to check for context 
switching. We'll record the type of object, the type of event and the 
object name, and, of course the SQL that did it! Who needs source
control?*/
CREATE TABLE [dbo].[DDLChangeLog]
    (
      [DDLChangeLog_ID] [int] IDENTITY(1, 1)
                              NOT NULL,
      [InsertionDate] [datetime] NOT NULL
        CONSTRAINT [DF_ddl_log_InsertionDate] 
            DEFAULT ( GETDATE() ),
      [CurrentUser] [nvarchar](50) NOT NULL
        CONSTRAINT [DF_ddl_log_CurrentUser]  
            DEFAULT ( CONVERT([nvarchar](50), USER_NAME(), ( 0 )) ),
      [LoginName] [nvarchar](50) NOT NULL
        CONSTRAINT [DF_DDLChangeLog_LoginName]  
            DEFAULT ( CONVERT([nvarchar](50), SUSER_SNAME(), ( 0 )) ),
      [Username] [nvarchar](50) NOT NULL
        CONSTRAINT [DF_DDLChangeLog_Username]  
            DEFAULT ( CONVERT([nvarchar](50), original_login(),(0)) ),
      [EventType] [nvarchar](100) NULL,
      [objectName] [nvarchar](100) NULL,
      [objectType] [nvarchar](100) NULL,
      [tsql] [nvarchar](MAX) NULL
    )
ON  [PRIMARY]

GO
/* now we'll create the trigger that fires whenever any database level
DDL events occur. We won't bother to record CREATE STATISTIC events*/
CREATE TRIGGER trgLogDDLEvent ON DATABASE
    FOR DDL_DATABASE_LEVEL_EVENTS
AS
    DECLARE @data XML
    SET @data = EVENTDATA()
    IF @data.value('(/EVENT_INSTANCE/EventType)[1]', 'nvarchar(100)')
        <> 'CREATE_STATISTICS' 
        INSERT  INTO DDLChangeLog
                (
                  EventType,
                  ObjectName,
                  ObjectType,
                  tsql
                )
        VALUES  (
                   @data.value('(/EVENT_INSTANCE/EventType)[1]',
                              'nvarchar(100)'),
                  @data.value('(/EVENT_INSTANCE/ObjectName)[1]',
                              'nvarchar(100)'),
                  @data.value('(/EVENT_INSTANCE/ObjectType)[1]',
                              'nvarchar(100)'),
                  @data.value('(/EVENT_INSTANCE/TSQLCommand)[1]',
                              'nvarchar(max)')
                ) ;
GO

--let's create a Table, view, and procedure, and then drop them, and after
-- that, see what was recorded in the log
USE [TestLogging]
GO
CREATE TABLE [dbo].[PublicHouses]--the test Table
    (
      [pubname] [varchar](100) NOT NULL,
      [Address] [varchar](100) NOT NULL,
      [postcode] [varchar](20) NOT NULL,
      [outcode] VARCHAR(4)
    )
ON  [PRIMARY]
GO
USE [TestLogging]
GO
CREATE VIEW [dbo].[vCambridgePubs]--the test view
AS  SELECT TOP ( 100 ) PERCENT
            pubname,
            Address + '  ' + postcode AS Expr1
    FROM    dbo.PublicHouses
    WHERE   ( postcode LIKE 'CM%' )
GO
CREATE PROCEDURE spInsertPub--the test stored procedure
    @pubname VARCHAR(100),
    @Address VARCHAR(100),
    @postcode VARCHAR(20)
AS 
    INSERT  INTO PublicHouse
            (
              pubname,
              Address,
              Postcode,
              outcode
            )
            SELECT  @pubname,
                    @Address,
                    @Postcode,
                    LEFT(LEFT(@Postcode, 
                       CHARINDEX(' ', 
                       @Postcode + ' ') - 1),
                        4)
GO
DROP VIEW vCambridgePubs
GO
DROP PROCEDURE spInsertPub ;
GO
DROP TABLE PublicHouses ;
GO
-- now, having done all that we can then see what happened. As you know,
-- this is the only way you'll ever see the current build statements for
-- your tables! Now try changing the database objects via SSMS and have a
-- look at the SQL DDL that gets executed!

SELECT  *
FROM    DDLChangeLog
ORDER BY insertionDate 

-- To help, here is a better rendering of the log. We create an HTML table
--and format it up prettily
DECLARE @HTMLCode VARCHAR(MAX)
SELECT  @HTMLCode = COALESCE(@HTMLCode, ' <style type="text/css">
    <!--
    #changes{
     border: 1px solid silver;
     font-family: Arial, Helvetica, sans-serif;
     font-size: 11px;
     padding: 10px 10px 10px 10px;
    }
    #changes td.date{ font-style: italic; }
    #changes td.tsql{ border-bottom: 1px solid silver; color: #00008B; }
    -->
    </style><table id="changes">
') + '<tr class="recordtop">
<td class="date">' + CONVERT(CHAR(18), InsertionDate, 113) + '</td>
<td class="currentuser">' + currentUser + '</td>
<td class="loginname">' + LoginName
        + CASE WHEN loginName <> UserName THEN '(' + UserName + ')'
               ELSE ''
          END + '</td>
<td class="eventtype">' + EventType + '</td>
<td class="objectname">' + ObjectName + ' (' + objectType + ')'
        + '</td></tr>
<tr class="recordbase"><td colspan="6" class="tsql"><pre>' + tsql
        + '</pre></td></tr>
'
FROM    DDLChangeLog
ORDER BY insertionDate ;
SELECT  @HTMLCode + '
</table>'
GO
--Which gives this...

25 May 2007 10:47:	dbo	SIMPLETALK\RobynPage	CREATE_TABLE	PublicHouses  (TABLE)
CREATE TABLE [dbo].[PublicHouses]--the test Table ( [pubname] [varchar] (100) NOT NULL, [Address] [varchar] (100) NOT NULL, [postcode] [varchar] (20) NOT NULL, [outcode] VARCHAR (4) ) ON [PRIMARY]
25 May 2007 10:47:	dbo	SIMPLETALK\RobynPage	CREATE_VIEW	vCambridgePubs  (VIEW)
CREATE VIEW [dbo].[vCambridgePubs]--the test view AS SELECT TOP (100) PERCENT pubname, Address + ' ' + postcode AS Expr1 FROM dbo.PublicHouses WHERE (postcode LIKE 'CM%')
25 May 2007 10:47:	dbo	SIMPLETALK\RobynPage	CREATE_PROCEDURE	spInsertPub  (PROCEDURE)
Create procedure spInsertPub--the test stored procedure @pubname varchar (100), @Address varchar (100), @postcode varchar (20) as insert into PublicHouse (pubname, Address, Postcode, outcode) Select @pubname, @Address, @Postcode, left (left (@Postcode, charindex (' ',@Postcode+' ')-1),4)
25 May 2007 10:47:	dbo	SIMPLETALK\RobynPage	DROP_VIEW	vCambridgePubs  (VIEW)
Drop View vCambridgePubs
25 May 2007 10:47:	dbo	SIMPLETALK\RobynPage	DROP_PROCEDURE	spInsertPub  (PROCEDURE)
DROP PROCEDURE spInsertPub;
25 May 2007 10:47:	dbo	SIMPLETALK\RobynPage	DROP_TABLE	PublicHouses  (TABLE)
DROP TABLE PublicHouses ;


--once we finish logging we can...
--Drop the trigger.
DROP TRIGGER trgLogDDLEvent ON DATABASE
GO
--Drop table ddl_log.
DROP TABLE DDLChangeLog
GO
/*
Of course, this can be very valuable for Database Development work.

Preventing changes to database objects,
---------------------------------------

BOL seem to be very proud of their example code that prevents a table
being altered, though, if you have security nailed down properly, this
shouldn't happen anyway. */

CREATE TRIGGER trgNoMonkeying ON DATABASE
    FOR DROP_TABLE, ALTER_TABLE
AS
    DECLARE @Message VARCHAR(255)
    SELECT  @message = 'You are forbiddent to alter or delete the '''
            + EVENTDATA().value('(/EVENT_INSTANCE/ObjectName)[1]',
                                'nvarchar(100)') + ''' table'
    RAISERROR ( @Message, 16, 1 )
    ROLLBACK ;
GO



CREATE TABLE NewTable ( Column1 INT ) ;
GO
DROP TABLE NewTable
/*
'Msg 3609, Level 16, State 2, Line 1
The transaction ended in the trigger. The batch has been aborted.
Msg 50000, Level 18, State 1, Procedure trg, Line 8
You are forbiddent to alter or delete the 'NewTable' table'

Logging all changes to the Logins and database users
---------------------------------------------------- 

Another good use for triggers is to provide information about security
 events*/
GO
USE master
GO
--in MASTER, we'll creat a log for all the databases security events. 
CREATE TABLE [DDLSecurityLog]
    (
      [DDLSecurityLog_ID] [int] IDENTITY(1, 1)
                                NOT NULL,
      [InsertionDate] [datetime] NOT NULL
           CONSTRAINT [DF_ddl_log_InsertionDate] 
               DEFAULT ( GETDATE() ),
      [CurrentUser] [nvarchar](50) NOT NULL
           CONSTRAINT [DF_ddl_log_CurrentUser] 
               DEFAULT ( CONVERT([nvarchar](50), USER_NAME(), ( 0 )) ),
      [LoginName] [nvarchar](50) NOT NULL
           CONSTRAINT [DF_DDLSecurityLog_LoginName] 
               DEFAULT ( CONVERT([nvarchar](50), SUSER_SNAME(), ( 0 )) ),
      [Username] [nvarchar](50) NOT NULL
           CONSTRAINT [DF_DDLSecurityLog_Username] 
               DEFAULT ( CONVERT([nvarchar](50), original_login(), ( 0 )) ),
      [EventType] [nvarchar](100) NULL,
      [objectName] [nvarchar](100) NULL,
      [objectType] [nvarchar](100) NULL,
     [DatabaseName] [nvarchar](100) NULL,
      [tsql] [nvarchar](MAX) NULL
    )
ON  [PRIMARY]
/*
Now we will write a trigger that inserts into our security log all
server security events. There is a bug which prevents you just 
specifying all the security events, you have to list 'em*/


IF EXISTS ( SELECT  *
            FROM    sys.server_triggers
            WHERE   name = 'trgLogServerSecurityEvents' ) 
    DROP TRIGGER trgLogServerSecurityEvents ON ALL SERVER
GO
CREATE TRIGGER trgLogServerSecurityEvents ON ALL SERVER
    FOR CREATE_LOGIN, ALTER_LOGIN, DROP_LOGIN, GRANT_SERVER, DENY_SERVER,
        REVOKE_SERVER, ALTER_AUTHORIZATION_SERVER
AS
    DECLARE @data XML
    SET @data = EVENTDATA()
    INSERT  INTO master..DDLSecurityLog
       (
       EventType,
       ObjectName,
       ObjectType,
       TSQL,
      DatabaseName
       )
    VALUES
       (
        @data.value('(/EVENT_INSTANCE/EventType)[1]', 'nvarchar(100)'),
        @data.value('(/EVENT_INSTANCE/ObjectName)[1]', 'nvarchar(100)'),
        @data.value('(/EVENT_INSTANCE/ObjectType)[1]', 'nvarchar(100)'),
          'Server',
        @data.value('(/EVENT_INSTANCE/TSQLCommand)[1]', 'nvarchar(max)')
        ) 
GO
/*
Now we have to create another trigger in each database which recors all
the database security changes*/
USE testlogging--back to our database!
GO
CREATE TRIGGER trgLogDatabaseSecurityEvents ON DATABASE
    FOR DDL_DATABASE_SECURITY_EVENTS
AS
    DECLARE @data XML
    SET @data = EVENTDATA()
    INSERT  INTO master..DDLSecurityLog
         (
         EventType,
         ObjectName,
         ObjectType,
        DatabaseName,
         tsql
         )
    VALUES  
         (
         @data.value('(/EVENT_INSTANCE/EventType)[1]', 'nvarchar(100)'),
         @data.value('(/EVENT_INSTANCE/ObjectName)[1]', 'nvarchar(100)'),
         @data.value('(/EVENT_INSTANCE/ObjectType)[1]', 'nvarchar(100)'),
         @data.value('(/EVENT_INSTANCE/DatabaseName)[1]', 'nvarchar(max)'),
         @data.value('(/EVENT_INSTANCE/TSQLCommand)[1]', 'nvarchar(max)')
         ) 
GO
/* now everything is in place let's test it. We will simulate an intruder's
cunning attempt to create himself as a loging with sysAdmin rights and his
gaining access as a database user. We could always prevent the transaction 
but that would just draw his attention to the trigger being there!
*/ 

USE [master]
GO
/* Heh! Heh!*/
CREATE LOGIN [Intruder] WITH PASSWORD= N'silly', DEFAULT_DATABASE=
    [TestLogging], DEFAULT_LANGUAGE= [Portugu?(Brasil)], CHECK_EXPIRATION=
    OFF, CHECK_POLICY= OFF
GO
EXEC master..sp_addsrvrolemember @loginame = N'Intruder',
    @rolename = N'sysadmin'
GO
USE [TestLogging]
GO
CREATE USER [Intruder] FOR LOGIN [Intruder]
GO
--now we will drop the database user
IF EXISTS ( SELECT  *
            FROM    sys.server_principals
            WHERE   name = N'Intruder' ) 
    DROP LOGIN [Intruder]
GO
--and drop the login
DROP USER [Intruder]
GO
/* now we can see that the whole activity has been logged. Because the
initial CREATE  LOGIN contained a password, it has not been recorded.
*/
SELECT  * FROM    master..DDLSecurityLog

--so to end up, we just clean up!
DROP TRIGGER trgLogDatabaseSecurityEvents ON DATABASE
DROP TRIGGER [trgNoMonkeying] ON DATABASE
GO
USE master
GO
DROP TRIGGER trgLogServerSecurityEvents ON ALL SERVER
DROP TABLE DDLSecurityLog 
GO
USE [TestLogging]
GO
DROP TABLE NewTable
GO

/*
for further reading

   Designing DDL Triggers
   Using the EVENTDATA Function
   Understanding DDL Triggers
   Implementing DDL Triggers


*/ formatted by the Simple-Talk Prettifier

© Simple-Talk.com