Some good scalability points on using LINQ in Enterprise applications.
So while there is a lot of overlap, LINQ to SQL is targeted more toward rapidly developing applications against your existing Microsoft SQL Server schema, while the Entity Framework provides object- and storage-layer access to Microsoft SQL Server and 3rd party databases through a loosely coupled, flexible mapping to existing relational schema.
.NET HITMAN: Difference between LINQ to SQL and the Entity Framework
Speed up SSIS to Oracle loads... without a 3rd-party component... but not quite as easily.
Great Article. This helped me speed up my Load. It is 8 times faster this way.
Mark Malakanov poorly maintained blog: SSIS 2005. Fast load into non-MS OLE DB destination
One reason to switch to 64-bit SQL Server.
The 32-bit platform
The 32-bit platform (x86) has the least amount of buffer cache. Buffer cache cannot reside within the Address Windowing Extension (AWE)-controlled memory space; it has to be in the first 2 Gigs of RAM allocated to the SQL Server instance. On the 32-bit platform SQL Server 2000 and SQL Server 2005, both use the same base calculation to find the amount of procedure cache to use. SQL Server will use up to 1 GB of memory, or 50% of the memory, whichever is lower.
SQL Server memory configurations for procedure cache and buffer cache
Looks like Cumulative Update 8 just isn't cutting it.
After lot of demands from user community (https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=326575) MS finally decided to create SP3 for SQL Server 2005. It will be shipped after official launch of SQL2008, but still we should see SP3 in 2008. That's a good news, because all Cumulative Updates (new CU7 was published two days ago http://support.microsoft.com/kb/949095/en-us) were not recommended to install and SP2 brought a lot of problems with it.
Some good feedback so far.... I still want one of these!
This is by far the coolest thing since sliced bread, it takes some getting used to but I am getting better fast. I was having trouble at first with moving forward in UT3 and had to ask my GURU for help. The fix was easy, I clench my teeth a lot so he told me to lower the movement to 3.0 on the joystick 1 profile and wala I am unstoppable. OCZ ROCKS. The more I play the more I see how slow my keyboard is, I had to set my mouse sensitivity up so it could keep up with the advanced profile movements.
OLAP PivotTable Extensions is an Excel 2007 add-in which extends the functionality of PivotTables on Analysis Services cubes. The Excel 2007 API has certain PivotTable functionality which is not exposed in the UI. OLAP PivotTable Extensions provides an interface for some of this functionality. It can be launched from the following menu option in the right-click menu for PivotTables:
Setting the Project Properties to Run64BitRuntime = false resolves this.... and while scheduling you'll need to use the x86 version of dtexec.
Both versions of the provider have the same ID. To specify whether the Integration Services runtime uses an available 64-bit version of the provider, you set the Run64BitRuntime property of the Integration Services project. If the Run64BitRuntime property is set to true, the runtime finds and uses the 64-bit provider; if Run64BitRuntime is false, the runtime finds and uses the 32-bit provider. For more information about properties you can set on Integration Services projects, see Integration Services Considerations on 64-bit Computers and Integration Services in Business Intelligence Development Studio.
Day after day we are working with Cube Browser but when the project or cube designer has closed we lost our query, sometime it takes a long time to reorder again all our dimensions.
This add-in is giving us the ability to save personal views and run it as a new request.
I develop it for SSAS 2005 & 2008 (SSAS 2008 with VS 2008).
Sync'ing logins with Log Shipping.
One of the problems restoring a database to a new server is dealing with out of sync logins. The link between a database user name and a server user name is the SID that is generated when the login is added to SQL Server. There are stored procedures to sync the SID's but they have to be run for each user that is out of sync in each database. If you are bringing up a DR server that houses 60 log shipped databases, this can be a very tedious task.
Sync All Logins on a Server in a single click using SP_MSForEachDB - SQL Server Central
One way to eliminate cursors scraping across your tables like fingers on a chalkboard.
Useful script.
Show content differences between two tables/views
Show content differences between two tables/views - SQL Server Central
Softartisans Officewriter has some interesting products with SQL & Sharepoint integration.
Live Document Libraries
SharePoint Document Libraries are a convenient and increasingly popular way to share files across an organization. SharePoint adds powerful features, such as access control and versioning, on top of basic file availability. However, Document Libraries can only serve static documents. For example, if you wanted to store a spreadsheet with sales data, you would need to constantly edit the document to insure that the employees who download the file are getting the latest data. This limitation does not allow a company to take advantage of the fact that these documents are being stored on a server with ready access to the latest corporate data.
Publish data from:
SQL Server
ADO.NET
Business Data CatalogOfficeWriter turns SharePoint Document Libraries into Live Document Libraries, service the most current data from any ADO.NET or Business Data Catalog data source. Every time a user requests the document, you can return the latest data.
When does Something = Something = Something? Only in SQL....
This little piece of code will run through a table and sequentially number the field you specify. The only drawback is that it will determine the order based on the physical order of the table.
declare @intCounter int
set @intCounter = 0
update Yaks
SET @intCounter = YakSequenceNumber = @intCounter + 1
Convert MDX fields to SQL
Saturday, December 15th, 2007A number of our customers have reporting systems that use both MDX and SQL, retrieving data from both OLAP and SQL Server databases. This generates the problem of converting an MDX field ([Dimension].[Hierarchy].&[Attribute]) into SQL Server field value (Attribute). The following code is a Reporting Services custom code section that will rip off the MDX and leave you with the value.
Public Function MDXParamToSQL(Parameter As String, All As String) As String
Dim Val As String
Val = ParameterIf Val.Contains(”[”) Then
If Val.ToLower().Contains(”].[all]”) Then
Return All
Else
Val = Val.Substring(1, Val.LastIndexOf(”]”) - 1)
Val = Val.Substring(Val.LastIndexOf(”[”) + 1)
Return Val
End If
Else
Return Val
End IfEnd Function
