SQL & LINQ

SQL Reporting Services Error Installing TFS 2010

Dennis Bottjer — Thu, 09 Sep 2010 06:18:01 GMT

Over the weekend I spun up a new virtual machine for a practice TFS 2010 Installation. The TFS installation process is much improved. It can loosely be broken into two phases which are installation and configuration. The installation is the easy part which basically prepares the server and copies some bits to the drive. The configuration is a little more difficult but provides some guidance to help make the important decisions. During the configuration you make the following three key decisions.

Install WSS 3.0 or use an existing SharePoint installation
Install SQL Express or use an existing SQL Instance
Install Reporting Services

During the configuration I received TF255275 Error during the Reporting Services portion of the configuration. My reporting services database was created and configured for SharePoint Mode.

Reference: http://www.sathishtk.com/blog/post/2009/10/15/TFS-2010-TF255275-Error.aspx

Despite referencing the TFS 2010 Beta the above blog post helped resolve the issue. Essentially, I had to change the database to Native Mode. However, as a commenter mentions I had to delete the Report Database and recreate it in Native Mode before the configuration wizard would complete.

Cumulative Update Package 2 for SQL Server 2008 Service Pack 1

Dennis Bottjer — Mon, 04 Jan 2010 02:57:06 GMT

Issues:

SharePoint 2010 Foundation and Server require the Cumulative Update Package 2 for SQL Server 2008 Service Pack 1 to use SQL Server 2008 as the backend Database.

Solution:

SQL Server 2008 will not install properly on Windows 2008 Server without SQL Server 2008 Service Pack 1. Download Download SQL Server 2008 Service Pack 1.

To use SQL Server 2008 for the backend database for SharePoint Foundation or Server download Download and Install Cumulative Update Package 2 for SQL Server 2008 Service Pack 1.

Note: Installing the Cumulative Update Package 2 for SQL Server 2008 Service Pack 1 will update SQL Server’s build number to 10.00.2714.

Additional Information:

Fixes Contained in the Cumulative Update

Technorati Tags: SharePoint,SharePoint 2010,SQL Server 2008,SQL Server Updates,Installing SQL 2008

Oklahoma City SQL Server Developers Group Kick Off Meeting

dbottjer — Fri, 10 Apr 2009 09:48:38 GMT

Oklahoma City has a new user group thanks to the hard work of Kristin Ferrier. The Oklahoma City SQL Server Developers Group will meet monthly. The Group’s first meeting is Monday April 13th. See details below:

Event Details:

We are excited to invite you to the first meeting of the Oklahoma City SQL Server Developers Group! Mike Hotek, former SQL Pass speaker, has graciously agreed to be our first speaker.

Topic: Q&A with Mike Hotek (open topics are Database Administration and T-SQL in both SQL Server 2005 and 2008)

Mike will be open to questions on the topics of both database administration and T-SQL with respects to both SQL Server 2005 and 2008. This is a format that Mike has used with great success in a variety of presentation arenas, including SQL Pass.

Mike is a SQL Server specialist with three decades of experience as a developer and database professional. He is the Vice-President of FilAm Software Technology, a development company located in the Philippines as well as the Vice-President of MHS Enterprises, a development company based in the Dallas, TX area. He has deployed applications and environments spanning every feature within the SQL Server product as well as authoring/co-authoring 8 books on SQL Server.

When: Monday, April 13th
Time: 6:00 p.m. - 8:00 p.m.
Location: Oklahoma City Downtown Library (300 Park Avenue) on the 4th Floor in the Friends of the Library Room

Socialization time will be from 6:00 p.m. - 6:20 p.m. Mike will then begin taking your questions from 6:20 p.m. - 8:00 p.m.

We would like to thank GDH Consulting for sponsoring the location.
We would, also, like to thank OakTree Software for donating a grand prize for the first meeting. OakTree will donate a 3-day SQL class (value $1,275). It must be a class that is already running. Here is a link to their schedule - http://www.oaktreesoftware.com/course_list.aspx

FYI...No food or drinks will be provided, however, you many bring your own.

Please RSVP at the following link: http://www.surveymonkey.com/s.aspx?sm=7Mh_2fXhN0wq_2fzCRnTnUGJbQ_3d_3d

Technorati Tags: Oklahoma City,SQL Developers,Oklahoma Developers,Oklahoma User Groups

Multi-Tenant Data Architecture Reviewed

dbottjer — Wed, 09 May 2007 00:44:00 GMT

[Dave] first brought Multi-Tenant Data Architecture MSDN Article to my attention a few months ago. Unfortunately, I've had this article in my items to review folder. Anyway, I finally read the article in detail and thought it quite valuable. Basically, the article describes several approaches for designing a Multi-Tenant Data Architecture. It reviews each approach and reviews the pros and cons.

[RoyAshbrook] blogged his thoughts on Multi-Tenant Data Architecture.

Space Used By SQL Indexes

dbottjer — Mon, 30 Oct 2006 11:59:00 GMT

select 
    [name] As IndexName,
    type_desc,
    space_used_in_kb = (page_count * 8.0),
    space_used_in_mb = (page_count * 8.0 / 1024.0) 
from 
    sys.indexes I
inner join
    sys.dm_db_index_physical_stats(db_id(), object_id('.'), null, null, null) P on I.[object_id] = P.[object_id] and I.[index_id] = P.[index_id]
Order By
  space_used_in_kb desc

SQL Formatting for Easier Debugging

dbottjer — Sat, 21 Oct 2006 11:03:00 GMT

SELECT [IssueHistoryID]
      ,[StafferID]
      ,[IssueID]
      ,[Comment]
      ,[DateCreated]
  FROM [IssueVision].[dbo].[IssueHistory]

This Simple query was created from a demo Microsoft Smart Client Application called IssueVision. To create it I right clicked on IssueHistory table in SQL Server Management Studio 2005. Notice the commas are all to the left of the column names. Commonly, I see queries written like this instead:

SELECT [IssueHistoryID],
       [StafferID],
       [IssueID],
       [Comment],
       [DateCreated]
  FROM [IssueVision].[dbo].[IssueHistory]

The first example with the commas on the left is faster to debug and modify. Notice the only modification I need to make to comment out a column/line is to place "--" in front of the comma as shown below.

SELECT [IssueHistoryID]
      ,[StafferID]
      ,[IssueID]
      ,[Comment]
    --,[DateCreated]
  FROM [IssueVision].[dbo].[IssueHistory]

I realize this tip is a subtle point. Seems a little strange that I'm actually analizing the placement of a comma. However, I have become quite fond of this style b/c it saves time and helps me to reduce simple syntax mistakes while testing/debugging large sprocs. Try it with some more complex SQL and see what you think.

SQL Query By Year

dbottjer — Sat, 10 Dec 2005 07:12:00 GMT

Say you want to query a table returning all the records from a certain year. An easy way to do this is to use SQL’s Year Function as follows:

Select * From <Table> Where Year(<DateTimeField>) = 2006

SQL Table Naming Conventions

dbottjer — Fri, 23 Sep 2005 05:34:00 GMT

How do you name your SQL Tables? Are the names singular or plural? A friend suggested that tables should be singular because they represent a single record instance of data stored in the table. When multiple records are selected then a collection is created.

For example, if you create a table called student each record in that table represents one student. Each row or record in the student table represents one instant of the student table. If you select several students from the student table you are creating a collection of student records. The collection should be plural not the table name.

Stored Procs Vs. Dynamic SQL

dbottjer — Tue, 02 Aug 2005 06:16:00 GMT

There are many great topics of debate in software development. DataSets Vs. Objects, Smart Clients Vs. Web Apps, and Stored Procs Vs. Dynamic SQL. Many have argued that writing stored procedures is rigid and doesn't allow for an easy way to build detailed where clauses. Furthermore, SQL Server 2000 caches execution plans so in theory SQL Statements should be optimized if used often. Finally, .NET allows for parameterized queries helping to protect dynamic queries from SQL Interjection.

Even with these arguements against stored procedures the arguements for them are greater. First, Stored Procs use less bandwidth to do the same amount of work as a dynamic query. For example, if my client application is using dynamic SQL then it has to pass the entire SQL statement to the SQL Server for processing. In contrast, if the client application is using stored procedures all it has to do is call the stored procedure by name and pass to that procedure any required parameters. By using stored procedures less information is sent from the client to the server to do the same amount of work. Note: This can also be viewed as a security benefit because less information is being transmitted accross the wire that describes the exact design of your database. Next, Stored Procedures can be controlled by database security. That is a user be denied access to the tables within a database but be granted access through stored procedures. The stored procedures become the only way that user can read, add, update, or delete data from the database. Using stored procedures provides a useful layer of abstraction and a cleaner application design It is possible for a change to be made within a store procedure that will not require modifications to the application. If the client application were using dynamic sql such changes could only be made through a code change and then a redployment. Store Procedures can implement batch processing easier and more effectively than dynamic SQL.