SQL Server 2005 for Developers
I really enjoy Euan Garden's talks. I know a fair bit about SQL05 already, but how can you miss the guy in the Hawaiian shirt.
He had some video looping when I came in. One was apparently from the SQL Server 05 launch event last week. The promo video included the crew at Orange County Choppers and their 'experience' with the tool. Mikey: "SQL Server is .... more ... better than Oracle." Apparently, they had a contest to give a custom Microsoft bike to the best transition project from Oracle to SQL05. The winner had a 9TB database that they migrated.
Camtasia and VPC do not get along. The demos will be on the blog. http://blogs.msdn.com/euanga.
He has 60 slides. Anyone want to see them? No? Go figure.
Euan shows off the Management Studio. Pretty graphs showing resource usage across the server, sizes, etc., all built into the Studio. Trace rights are now a grantable right, so you don't need to be sysadmin to use Profiler. There is more security control, but alas it's now more complex.
"I wish we had Intellisense in T-SQL. Oh wait, I'm the one who cut that feature. I really regret that every time I have to give a demo."
He mentioned that it's a bad idea to prefix your user stored procedures with sp_. That's not something I'd heard of before, but I found some more info here.
Integration services inside Studio. He's using the neat graphical workflow stuff to pull the classic Paradox FishFacts demo db into SQL05. You need a couple of tricks. Use the Jet engine for input with Paradox 5.x as the External Parameter and the folder for the database in the path. Connect the Source to a Sql Server Destination node and hit run. All done. The integration services engine is so powerful that they're developing an 8 day training course.
Next year, there will be a Reporting Services Express server that comes with SQL Express, including a lightweight report builder. The restriction is that the data for the reports must come from the local SQL Express instance. Report Builder lets the dba/developer define a metamodel for end users. This metamodel understands the relationships in the db, hopefully preventing the users from creating huge, bad queries. The Report Builder control understands anything in a DataSet object, so you don't need SQL Server to use it.
He had some video looping when I came in. One was apparently from the SQL Server 05 launch event last week. The promo video included the crew at Orange County Choppers and their 'experience' with the tool. Mikey: "SQL Server is .... more ... better than Oracle." Apparently, they had a contest to give a custom Microsoft bike to the best transition project from Oracle to SQL05. The winner had a 9TB database that they migrated.
Camtasia and VPC do not get along. The demos will be on the blog. http://blogs.msdn.com/euanga.
He has 60 slides. Anyone want to see them? No? Go figure.
Euan shows off the Management Studio. Pretty graphs showing resource usage across the server, sizes, etc., all built into the Studio. Trace rights are now a grantable right, so you don't need to be sysadmin to use Profiler. There is more security control, but alas it's now more complex.
"I wish we had Intellisense in T-SQL. Oh wait, I'm the one who cut that feature. I really regret that every time I have to give a demo."
He mentioned that it's a bad idea to prefix your user stored procedures with sp_. That's not something I'd heard of before, but I found some more info here.
Integration services inside Studio. He's using the neat graphical workflow stuff to pull the classic Paradox FishFacts demo db into SQL05. You need a couple of tricks. Use the Jet engine for input with Paradox 5.x as the External Parameter and the folder for the database in the path. Connect the Source to a Sql Server Destination node and hit run. All done. The integration services engine is so powerful that they're developing an 8 day training course.
Next year, there will be a Reporting Services Express server that comes with SQL Express, including a lightweight report builder. The restriction is that the data for the reports must come from the local SQL Express instance. Report Builder lets the dba/developer define a metamodel for end users. This metamodel understands the relationships in the db, hopefully preventing the users from creating huge, bad queries. The Report Builder control understands anything in a DataSet object, so you don't need SQL Server to use it.
0 Comments:
Post a Comment
<< Home