View Complete Post
There's always been disagreement about whether large blobs, such as document and multimedia items, should be stored in the database or file system. In SQL Server 2008 you don't have to choose; filestream storage provides the best of both approaches.
MSDN Magazine May 2009
New spatial data support in SQL Server 2008 opens the door to mapping and querying geometric and geographic data, allowing you to build exciting new applications.
MSDN Magazine February 2009
SQLServer 2008 R2
Excel 2010 x64
I have a fairly complex Excel report where a raw data sheet is updated from 10 or so PivotTables pulling from an Analysis Services Cube, (2008 R2), with a VBA script that refreshes all pivottables, and then does some post-processing, formatting etc.
This was originally developed in Excel 2003, and the updating of all the pivot tables ran in under 10 seconds
I've now recreated in Excel 2010 and *each table* is taking up to a minute to refresh!
I've also observed that I can get the refresh time of a single table back down to 1sec, if I delete all other pivottables from the worksheet/book.
Its deeply frustrating, as I'm touting 2010 as being the way for our business to go...it won't help the cause if I deliver something with a x60 increase in runtime!
I've run traces of both the 2003 and 2010 versions executing against the SQL Server, the only thing I can see is that the 2003 version passes 1 single MDX query, whilst the 2010 version appears to be firing it in sections.
I've posted this in the Excel forum too.
Please can anyone help?
I need to find white spaces in my table. the table contains 35 columns, therefore, I cannot check with AND or OR operator something like this
SELECT * FROM MS_Exchange_IS WHERE (TMZDIFF != '' AND Timestamp != ''..........)
Also I don't want to use cursors as it will greatly hamper the performance of my application.
Please suggest any other option.
Any link or pointers would be helpful
Thanks in Advance,
I've been experimenting with the partitioned table feature in SQL 2008 (evaluation version). Nice work, I can see how the feature would be really useful. I am investigating it for an application that involves a scrolling window based on a datetime
column, so that the table holds one year's worth of data. The datetime is used as an event timestamp, recording it down to the millisecond. New data is loaded every hour. I would like to keep the impact of the new data load minimal, so I want to take
advantage of partition switching when a new hour's worth of data is ready. Trimming old data would only happen once a day. My questions/assertions based on experimenting a little with this and reading what I could find on the subject:
1) Both the partition function and the left-most column of the clustered index should be based on the datetime column value. This takes maximum advantage of the datetime range terms that are in every query generated by the UI (show me events of this
type in the last week) and also allows partition switching for adding new records and trimming old ones.
2) It doesn't make sense to keep an identity column on the partitioned table, despite their convenience as a surrogate key for many editing tools. You would have to add the datetime column to an identity column in a primary key or unique c
I'm trying to use SSIS in Visual Studio 2008 to export a table to Excel 2010 and get the following error:
The table cannot be created. (Microsoft Visual Studio)
Syntax error in field definition. (Microsoft Office Access Database Engine)
at System.Data.OleDb.OleDbCommand.ExecuteCommandTextErrorHandling(OleDbHResult hr)
at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForSingleResult(tagDBPARAMS dbParams, Object& executeResult)
at System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult)
at System.Data.OleDb.OleDbCommand.ExecuteCommand(CommandBehavior behavior, Object& executeResult)
at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)
at Microsoft.DataTransformationServices.Design.PipelineUtils.ExecuteSqlStatement(ConnectionManager connectionManager, String sqlStatement, IServiceProvider serviceProvider, Boolean getReader)
at Microsoft.DataTransformationServices.Design.DtsTableCreator.okButton_Click(Object sender, EventArgs e)
I'm having what I'm hoping will be a simple issue -
My co-worker has created a large report which contains several tables in SSRS 2008. Each table is tied to one dataset, yet only certain data can be returned to each respective table. Right now he's applying filters at the table-level behind each table, however as you can imagine this is not efficient because there is a LOT of data returning for this report.
I'll try and give a simplified example -
There are two tables in the report body - one for containing products relating to both Cats and Dogs, and one for containing products relating to Birds. Each product starts with the name of the specific animal - for example "Cats-Mouse Toy", "Dogs-Frisbee", "Birds-Rubber_Leaf".
Now I need to somehow filter out each product so that they go to their proper tables. As mentioned above, my co-worker was creating a specific filter for each product, but this is proving to be inefficient. For example, there are 52 different products for Birds alone. That would mean 52 different filter entries for each product. What I would like to do is use the LIKE operator but i'm not getting the results I want on the first table.
So, on the first table I need something like: =(Fields!Products.value LIKE &