Tuesday, March 27, 2012
General impressions MS OLAP vs. Hyperion Essbase
Monday, March 26, 2012
General Advice - Timesheet application
I can of course use the smalldatetime datatype to store all the start at, finish at and elapsed hours times but wonderd if there was any comparative advantage to using numerics instead and converting to/from HH:MM representation.
Maybe I need to finally figure out how to create and use custom data types?
There's lots of math to do on these things once the data is captured for reporting and such and smalldattime looks like a fairly big waste of space for something that really only deals in hours.
Anyone doen things like this before? Any advice on what not to do?
many thanks
Steve1) Use datetime
2) If necessary, denormalize your datetime field converting them in several int fields. This method sometimes is used in DW environment (with a dimension time)
Friday, March 9, 2012
function naming and execution
I am converting a database from Oracle to SQL-Server 2005 and in that context I needed to implement a function in the database. My database default uses the dbo schema and the function is there too. I define a function called "Translate" and wanted to use it like this :
SELECT
translate(Phonenumber, '0123456789 ()+-', '0123456789') as Phonenumber
FROM
Customer
but what pussled my was that in order to make this work I had to prefix the translate method with "dbo." like this :
SELECT
dbo.translate(Phonenumber, '0123456789 ()+-', '0123456789') as Phonenumber
FROM
Customer
as all "objects" I'm using resides in the dbo schema - why must I prefiks only the function and not the table?Yes, functions will defintely need the owner / schema prefix.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de