Below is a script I use to determine table size. Basically, it walks through the user databases and for each table. The information is converted in GB. It’s a pretty simple use of MS sp_spaceused with sp_msforeachtable. More info on sp_spaceused.
Full script, below. Download script here.
Found this reference … JUST IN TIME!
Thanks Thavash This is by far my most visited page.
http://thavash.spaces.live.com/blog/cns!CF6232111374DFD2!155.entry
| Command | Result |
| FormatDateTime(Parameters!Date.Value,1) | Tuesday, April 10, 2007 |
| FormatDateTime(Parameters!Date.Value,2) | 4/10/2007 |
| FormatDateTime(Parameters!Date.Value,3) | 12:00:00 AM |
| FormatDateTime(Parameters!Date.Value,4) | 00:00 |
…but the better way to do it would be to use …
2) The Format command and specify the exact format you require. For example…
| Command | Result |
| Format(Parameters!Date.Value,”dd-MM-yyyy”) | 10-04-2007 |
| Format(Parameters!Date.Value,”dd/MM/yyyy”) | 10/04/2007 |
| Format(Parameters!Date.Value,”MMM-dd-yyyy”) | Apr-10-2007 |
| Format(Parameters!Date.Value,”MMM-dd-yy”) | Apr-10-07 |
So 3 M’s give you “Apr” ….anyway this is quite useful if you’re looking for Day/Month/Year , since the system will default to MM/DD/YYYY.
Using this you should be able to display the date format you want , or send through a particular format to a Stored Proc.
EDITED 22/08/2007 : If the Format Command doesn’t work , try converting the value to a date , eg.
| Format(Cdate(Parameters!Date.Value),”dd-MM-yyyy”) |
I’m a sucker for the Maint Wizards and everytime I touch a SQL Job.. It reverts the ownership to my domain account. ( Not a Good Practice to use my domain account … I know). I manually change the ownership back to sa (actually, dbo as sa is disabled…ssssh) . OR I CAN USE THE BELOW HANDY-DANDY SCRIPT . As always .. Buyer-Beware! Written for SQL Server 2005..
Here is a script I wrote to do the heavy lifting:
SQL Server Management Studio 2005 (SP2) updates has a wide range of reports that give the users vital information about server health and database objects. You can even add your own custom reports to create you own application database dashboards. The reports are created just like SQL Server Reporting Services RDL’s.
Some Links to help you along:
Listing of some Available Reports HERE
How to make your own Custom Reports HERE
One thing I forget to do often is to include the actual item I’m returning in the Select Statement in the Group By. Meaning , if I use a case statement of some function to change the value that I’m returning, then I should include that and not the base column name in the Group By part of the select statement
/*
If you write something like this and the Col2 has multiple 'Unique' Values
then you will get a row for each value distinct Col2 value that says 'Other'
*/SELECT [Col1]
,Case When [Col2] = 10 then 'Ten'
Else 'Other' End as [LameExample]
,Count(*) as CNT
FROM [dbo].[lameTableExample]
GROUP BY [Col1], [Col2]
-- This Example will return Only two rows
SELECT [Col1]
,Case When [Col2] = 10 then 'Ten'
Else 'Other' End as [LameExample]
,Count(*) as CNT
FROM [dbo].[lameTableExample]
GROUP BY [Col1]
, Case When [Col2] = 10 then 'Ten'
Else 'Other' End
Select Case has a simple overview of using CASE in a SQL Query with the SUM() function.