Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

Coming In August Expand / Collapse
Author
Message
Posted Wednesday, July 9, 2008 9:24 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 3:05 PM
Points: 31,284, Visits: 15,750
Comments posted to this topic are about the item Coming In August






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #531340
Posted Thursday, July 10, 2008 5:45 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, November 24, 2014 2:02 PM
Points: 259, Visits: 716
One other feature with SQL 2008, which is seldom mentioned is the new multi-server query in SSMS 2008. This is a really useful feature where you can run a query across multiple servers in a server registration group and produce a single result set with the SQL instance automatically appended as the first column. Works against 2000, 2005, and 2008 servers. I've been using multi-server query since CTP 5 to quickly produce stats across the 150 SQL Servers I manage.


Post #531505
Posted Thursday, July 10, 2008 11:50 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: 2 days ago @ 8:20 AM
Points: 906, Visits: 2,007
Multi-server query sounds cool, could be very nice for consolidating job execution and DBCC info. I'm VERY thankful for separate date and time data types, I like the combined type, but there are times when it will drive you nuts. The spatial data type is very good for people running GIS apps like ArcInfo and the rest of the ESRI suite, which is basically every state, county, and local government, plus forestry, geology industries, law enforcement, etc. It exists in Oracle and DB/2, it was implemented in SQL Server as a varbinary. I think adding the spatial data type will add a lot of third-party value to SQL Server once programmers start working with it.

-----
Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson
Post #531844
Posted Thursday, July 10, 2008 2:37 PM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Monday, November 24, 2014 4:29 PM
Points: 752, Visits: 920
I like all the changes that I have seen so far and everything indicates that it is an improvement over SQL Server 2005.

Unfortunately, it looks like there is nothing in it which is compelling enough, at least for my current situation as a DBA, to justify the corporate money and man hours which would need to be spent upgrading and testing.

And no matter how little they say they have changed, I would suggest doing thorough testing when moving to a new version. In fact, I would say it is generally a good idea to do some testing before rolling out service packs much less a new version.


---
Timothy A Wiseman
SQL Blog: http://timothyawiseman.wordpress.com/
Post #531976
Posted Thursday, July 10, 2008 3:55 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 3:07 PM
Points: 2,049, Visits: 3,592
Not every organization will be able to reap benefits by moving to 2008 however, if you have the chance you should go. The one thing I will state emphatically is that if you are thinking of going to 2005 from 2000, don't bother. Make the leap.

Aside from the things Steve mentioned, SSMS has had some improvements which are pretty cool as well like Intellisense and the display of missing indexes when looking at execution plans (only able to be viewed when you looked at the often confusing XML plans in 2005). I will probably post about some of these features in my blog in the next couple of days when I get time to breathe.


David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #532026
Posted Thursday, July 10, 2008 7:15 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 4:32 PM
Points: 35,612, Visits: 32,209
Date and Time!! - They're finally separate so you can query as salesdate > '2008/07/09' instead of salesdate > '2008/07/09 00:00:00'.


You can do that in all versions of SQL Server since 6.5... nothing new there.

I, too, can't wait until the split of Date and Time... leaves much opportunity to easily get to 15,000 posts in a hurry explaining to people how to fix what they have unwittingly done by using the split. ;)


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #532076
Posted Friday, July 11, 2008 12:08 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 40,456, Visits: 36,912
cmille19 (7/10/2008)
One other feature with SQL 2008, which is seldom mentioned is the new multi-server query in SSMS 2008.

Works against 2000, 2005, and 2008 servers.


It works to SQL 7 boxes as well.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #532143
Posted Friday, July 11, 2008 12:16 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 40,456, Visits: 36,912
Jeff Moden (7/10/2008)

I, too, can't wait until the split of Date and Time... leaves much opportunity to easily get to 15,000 posts in a hurry explaining to people how to fix what they have unwittingly done by using the split. ;)


I can see times when only a date is needed, or only a time, however I foresee lots of people having a data and a time stored in different columns in 1 table when they should be stored in a datetime.

Is gonna be fun doing a between when the date and the time are separate.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #532148
Posted Friday, July 11, 2008 6:48 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 4:32 PM
Points: 35,612, Visits: 32,209
GilaMonster (7/11/2008)
I can see times when only a date is needed, or only a time...


It's probably because I've not had enough coffee this morning, yet... can you tell me when you see a serious advantage to having only a date or a time column why wouldn't storing just Date or just Time isn't some form of "lost data"? Even storing duration as just a TIME is a problem because you'd never be able to store values over 24 hours.



--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #532367
Posted Friday, July 11, 2008 7:35 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 40,456, Visits: 36,912
A time table - Physics 101, Lecture room 2B, 9am every monday.

Movie schedules. Movie X shows every day this week at 17:00, 20:30 and 23:00

A store list with their opening and closing times

An example I've actually used - storing the start time and end time of daily jobs

I can certanly do that with a datetime (and I have done it), but then I have to set some form of meaningless date.

Is it the norm? No. Are there cases where it's useful? Absolutely.

I would never store duration as a time. That's asking for nasty maths. Store is as a number of hours/minutes/seconds, depending on the granularity required.




Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #532432
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse