Showing posts with label management. Show all posts
Showing posts with label management. Show all posts

Friday, March 30, 2012

Runtime Customisation

What exactly does "Runtime Customisation" include? Management here seem to have the idea that the users will have a lot of control over which fields are displayed, the order, and be able to drag them around, etc.

From my reading, I think runtime customisation is limited to filtering the data, grouping and sorting.

Can anyone help me out here? Thanks.where the **** u get that option man|||Management have heard the words "Runtime Customisation" and have grand ideas of users creating reports on the fly. I think they're delusional; thanks for verifying this.

Friday, March 23, 2012

Running the Package input file .xmla

Hi,

Is there a way to run the package input .xmla file to the command prompt instead of running it in management studio?

cherriesh

Try the ascmd command-line utility, part of Analysis Services Administrative Samples.

http://www.microsoft.com/downloads/details.aspx?FamilyID=e719ecf7-9f46-4312-af89-6ad8702e4e6e&DisplayLang=en

sql

Wednesday, March 21, 2012

Running SSIS Packages in Management Studio

We are using SQL Server 2005 Standard edition.We have the development studio installed on a developer’s workstation.The SSIS package is accessing network folders using UNC and the tasks in packages are accessing SQL Server with a SQL Server id.

The SSIS package runs fine on the workstation. We deploy the SSIS package as a SSIS store on SQL Server.I receive Error 18456 Severity 14 State 8 error when I run the SSIS package as a SQL Agent job.

When I run the SSIS package from the Integration Services Management Studio, I get The AcquireConnection method call to the connection manager "dboSQLabm" failed with error code 0xC0202009.

I’m sure this is a permission based problem since it runs fine on my workstation.I tried logon onto the SQL Server with my id (I’m an admin to the server).I tried running the agent with my windows id.It looks like I’m getting problem connecting to the SQL Server tables since the logs are properly written to the network drive.

In SQL DTS 2000, all we needed to do was give the SQL agent id permission to the network folder. I tried to search the forums, but none of the solutions seem to work for my situation.

Do you use config files and do not save sensitive? This should take care of this issue.

There are quite a few posts about it in this forum

Philippe

|||The problem I was getting occurred whether I used a config file or not. I had the package set to EncryptSensitiveWithUserKey. I created another thread to get production deployment suggestions. We don't want our DBAs using BIDS to edit SQL connection manager settings when they migrate SSIS packages to production.|||

Then don't let them. Use configurations and the deployment wizard.

-Jamie

Tuesday, March 20, 2012

Running sql scripts

How does one run an sql script against a database then using sql management express.

I have the script and i connect to the correct database using the sql management express and execute the script. It even says that it completed successfully. But when i check the database there is nothing new added.

Is it somthing to do with the community preview version of sql management express??

thanks for any help

In Management Studio, the query window (where you run your query) can connect to different SQL instance/database from the Object Explorer (connect to a SQL instance when you open Management Studio). So check the dropdown list on the left of Execute(!) button to make sure your current query is connecting to the right database then execute the script. Before you check changes in the database, right click on the database ->select Refresh, then check the changes.