Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
In DB2, I want to create primary key on partition table. How can I do it?
Create table TEMP1:
CREATE TABLE TEMP1 (
ID INTEGER NOT NULL,
DATEREPORT VARCHAR(8) NOT NULL,
IDTEN INTEGER DEFAULT 0 NOT NULL
)DISTRIBUTE BY HASH (IDTEN, YEAR);
After that, I want to create primary key on ID column but not yet. How can I do?
As far as I know you cannot create a primary key without including all the columns in distribute list. So basically you either have to:
- include ID in the distribute list
- define the primary key using IDTEN and YEAR and ID
After processing your ETL package which loads data into the cube, how do you
ensure that your cube has been processed?
Well it depends on what you are looking for in confirmation.
1: Confirmation of last successful processing
1.1: If the SQL Server agent is processing your cubes, then you can set the agent up to send out an email on completion. This will tell you if the process completed successfully or failed. The only caveat is if you run the job as a SQL Server Analysis command, then the agent wont know if the command failed or was successful. Just make sure to run your commands as a SSIS package and there wont be any issues.
1.2: In addition to agent notifications I use a modified version of the Microsoft SSAS example, AMO Display Object Names. I modified it to read the structure and send me an email with last processing date / times of the cubes and dimensions.
Had to remove some of the code as it contained company info in it, but here is the juxed of it
2: Validating the data, that’s a whole task all unto it self. I used to do this with a SSIS package that would run a MDX query and send the results from that. However, I found that just making sure everything processed correct really solved this issues we where having.
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
hello all. I've got a ssrs 2008 question that has been bugging me for a couple of months. I have built a site for my HR department that takes in applications. HR takes the information and needs to send it to Directors and Supervisors in an application-style form. I was planning on using SSRS mainly because I can just render the application in a pdf by just using the url, which HR could just email to whomever they want to. This would all work fine if all of our HR employees were on the same domain, but they are not and the system admins for some of the domains don't want to build a trust to us, so I can't just tie their domain account to the security of the application report (some of our sites may not even have people on domains).
What I was looking for was a way to have an account on the server itself be the one to run the report so that the user wasn't prompted for login credentials when they looked up an application.
If you are using the server component of SSRS then I'm pretty sure you cannot allow anonymous connections, valid credentials are (should) always required by an internal server.
However there is no reason you can't host the reports in a separate aspx application using the internal app credentials to contact the server.
You could also change the reports to RDLC and embed them in an aspx application where the app fetches the data and supplies the viewer the RDLC file and the dataset, this requires the aspx app to have database credentials but not the end user.
Both solutions are terribly insecure and you need to carefully consider the business implications.
Never underestimate the power of human stupidity
This is a tricky situation, all these different domains have to build some kind trust or all the users who would be accessing these reports can be moved to a different domain altogether which you can use in your application. In that case you can give access to the users of this New domain.
There is not shortcut here which can resolve this, either you use trusted users or use a proxy user to fetch reports for all the users consuming these reports.
Yes...that's how you can achieve it. Meanwhile I got one more option in case if you are using SQL Server 2008 R2, you can create a subscriber database for the users who would access these reports and link all of them with your reports...this is something you can try....I would post some more details once I get more insight on this....