I would disable the indexes instead of scripting/dropping them. This has pretty much the same affect as scripting/dropping but, I think, is a lot simpler to manage.

Have a...

FK's should not be a problem for applications that read data (Analysis Services only reads data for most of its activities). Indexes on the FK columns on your fact...

Try the following

SELECT { [Measures].[Satis Miktari] } ON Columns,

{STRTOSET('[Dim Time].[Week Of Year].&[@MyWeekParamater]') ,

STRTOSET('[Dim Time].[Week Of Year].&[@MyWeekParamater].PrevMember')}

*

{[Dim Stores].[Store Name].allmembers } on rows

FROM

[HCRetailSales]

Analysis Services had some big changes done to it between SQL 2000 and SQL 2005. From 2005 to 2008 there were more changes but not so major.

There is a...

You could create a sproc that starts the job - specify 'EXECUTE AS' in the definition of the sproc so that it runs as a user who is allowed to...

Firstly, Reporting Services wants to have measures on columns and all other information required to be shown on the report needs to be rows. This is part of the...

You could write a stored proc to delete the data, add the stored procedure to the publication with the option set to replicate the execute of the stored procedure. ...

Been a while for me also but I think you will need to add an alias to EACH of the client machines using the Client Network Utility (should be in...

Replication will be quite happy with 100k rows. Depending on network speed etc it might take a while.

Yes you should be reorg-ing indexes periodically. Replication agents INSERT, UPDATE and DELETE data as required just like any other database and, hence, the table issues with fragmentation will...

For transaction replication with updateable subscriptions, your table must have a primary key

The tables will also need a uniqueidentifier column called "msrepl_tran_version" on each table. It may be the...

Ivanna Noh (12/21/2009)

Those little fine tuning screws at the bridge are great - so easy to get a perfect tuning that way (assuming...

These are warnings being issues because you have not changed the default data type for each of the fields on your input file. If you know the correct sizes...

I would not use Merge Replication for the scenario you are describing because there is a very real chance that the same ticket can be sold since merge replication does...

One factor for me was the neck width. I have large hands and too often I would find that I would be fretting one string and touching an adjacent...