CURRENT_TIMESTAMP
is standard ANSI SQL, and so is theoretically one tiny little island of ‘don’t need to change’ amongst your thousands of SQL Server-specific lines of SQL if you ever need to move databases….
More Related Contents:
- Retrieving the date in SQL Server; CURRENT_TIMESTAMP vs GetDate()
- Incorrect syntax near ‘)’ calling stored procedure with GETDATE
- Max Nbr of Months W/ No Activity in Past 12 Months
- Export from SQL Server to Excel
- SQL server query to output the data shown below
- hide/remove header and footer
- How to use a variable for the database name in T-SQL?
- How do you view ALL text from an ntext or nvarchar(max) in SSMS?
- SQL Server: SELECT only the rows with MAX(DATE)
- Create a view with ORDER BY clause
- What does ‘COLLATE SQL_Latin1_General_CP1_CI_AS’ do?
- INSERT INTO vs SELECT INTO
- Possible to store value of one select column and use it for the next one?
- LEN function not including trailing spaces in SQL Server
- How to view transaction logs in SQL Server 2008 [closed]
- Scheduled run of stored procedure on SQL server
- SQL Server ORDER BY date and nulls last
- Best way to implement an audit trail in SQL Server?
- How can I change from SQL Server Windows mode to mixed mode (SQL Server 2008)?
- What happens to the primary key Id when it goes over the limit?
- how to write number to word function in sql server [closed]
- Milliseconds wrong when converting from XML to SQL Server datetime
- Using GROUP BY with FIRST_VALUE and LAST_VALUE
- Conditional JOIN Statement SQL Server
- Is there an “IF EXISTS” test for a linked server?
- How do you deal with blank spaces in column names in SQL Server?
- Unique identifier (guid) as primary key in database design
- How to extract this specific substring in SQL Server?
- SQL Server stored procedure return code oddity
- ODBC Call Failed with stored procedure – Pass through query