You might already know this but thought to post it because it brushed up my knowledge and hope it brush up your knowledge too.

SQL Server starts its compiling process by checking the syntax of the code and then it checks the existence of the referenced objects. Unfortunately, this check does not always run (or it runs in different way). For example, you can create (or compile) a SP that has a reference to a table that is not exist but you cannot create a SP that has a reference to table that is exist but referred columns. Check  the below code.

   1: create table TestTable100 (id int)

   2: go

   3:  

   4: -- this SP has reference for a table that is not exists (TestTable101)

   5: -- but you can run this script and TestSP is successfully created

   6: create proc TestSP

   7: as

   8: begin

   9:  

  10:     select * from TestTable101

  11: end

  12: go

  13:  

  14: -- this SP has a reference to the correct table but has referenced to the column 

  15: -- that is not exist.

  16: -- SQL Server does not create this SP because it checks for column names

  17: alter proc TestSP

  18: as

  19: begin

  20:  

  21:     select name from TestTable100

  22: end

  23: go

Did it remind you something? Hope it does.

The 3rd SS SLUG will be held on Wednesday, 20th June 2007 at Microsoft Sri Lanka. Gogula will be starting the first session, exploring some design patterns of data warehousing and Joy will be continuing the second session covering SSRS, focusing on Report Builder. Not only that, we will be doing a short session regarding SQLBackup too. So, are you in Sri Lanka, looking for some SQL knowledge, or need to share your knowledge. Then visit, pay attention, share and win some fabulous prizes.

This is the latest article written about scaling out querying architecture in Analysis Services. Check this out. It is really worthwhile for reading.

I had not tried this but the requirement came yesterday, see the possibility of setting SSIS package as a data source for SSRS reports. By default, it is not enabled, you will not see anything related to SSIS in the DataSource Type drop-down in the data source dialog box. Follow below set if you need to set SSIS packages as data source for your reports.

• Open RSReportDesigner.config file through text editor. It is stored in the \Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies folder.
• Remove comment marks that have been set for SSIS extensions under data and designer element. Save and close it.
• Open the rsreportserver.config file in the \Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer folder.
• Clear comment marks set for SSIS extension under data element.

Now you can access and process SSIS packages for reports. I may be writing complete procedure and publish but this is total enough for starting the experiment.

I am knee-deep in my MSc assignments, all my extra hours are allocated to it. I find bit difficult to allocate time for writing my blog posts, completing my articles for SQL Server Universe. Anyway, only few months more, working hard to pass with flying colors.