T-SQL

SQLServerCentral Article

Manipulating And Using DateTime Data

  • Article

Working with date and time data in SQL Server can be a bit cumersome using just T-SQL. With the separate datatypes being pulled from SQL Server 2005 for the time being, however, it is something that a DBA needs to get used to. Robert Marda brings us an instructional look at the different datetime data types and some things you should be aware of when developing with them.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2004-10-27

16,824 reads

Technical Article

Utility proc for updating (sub) sequence columns

  • Script

This is a utility proc that I use a lot for datawarehouse transformation/load processing. This is a generic proc for resequencing an integer column in sorted order within a given key combination.Note that 'key' is used here in a general context and not specific, that is there doesn't have to be any keys or indexes […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2004-10-12

107 reads

Blogs

T-SQL Tuesday #204: Are tech blogs dead?

By

This is my late response to T-SQL Tuesday #204. I almost always forget about...

Should You Use CHOOSE(): #SQLNewBlogger

By

I was experimenting with CHOOSE() recently after I was asked a question. In a...

T-SQL Tuesday #204 – Are blogs still relevant? (Roundup)

By

I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...

Read the latest Blogs

Forums

Weird problem altering logins with sysadmin account

By Brandie Tarvin

Has anyone ever seen this before? I have sysadmin permission on a server. I...

Switching Schema II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Switching Schema II

A Practical Approach to Automating SQL Server Email Notifications

By Kunal Rathi

Comments posted to this topic are about the item A Practical Approach to Automating...

Visit the forum

Question of the Day

Switching Schema II

I run this query:

SELECT 
 s.name AS schemaname
 , o.name AS objectname
 FROM sys.objects o
 INNER JOIN sys.schemas s ON s.schema_id = o.schema_id
 WHERE o.name = 'Beer'
I get two rows back for the objects, named dbo.beer and etl.beer. Both the tables have identical schemas and are not partitioned. There are 25 rows in dbo.beer and 0 rows in etl.beer. I run this code:
ALTER TABLE dbo.beer switch TO etl.beer
What happens?

See possible answers