Comments for SQL Server Consulting

Comment on Unable to modify tables in SQL Server 2008 by abbas

abbas — Thu, 27 Oct 2011 11:01:16 +0000

hello
thanks a lot

Comment on Error: 0xC00F9304 The Excel Connection Manager is not supported in the 64-bit version of SSIS by Dean

Dean — Mon, 20 Jun 2011 05:27:32 +0000

Thanks for the tip. You made my day

Comment on Error 7221: Could not relay results of procedure from remote server by Guillermo

Guillermo — Thu, 07 Apr 2011 22:01:25 +0000

Thank You.

It solve my problem too.

Comment on How to Audit SSAS role permissions by Sam Kane

Sam Kane — Thu, 24 Mar 2011 20:06:50 +0000

Here are this and some other articles on Analysis Services Security Testing:

http://ssas-wiki.com/w/Articles#Testing_Security

Comment on How to Audit SSAS role permissions by admin

admin — Mon, 07 Feb 2011 23:26:18 +0000

Thanks for the tip Darren. I was not aware of this utility and I will take a look.

Comment on How to Audit SSAS role permissions by Darren Gosbell

Darren Gosbell — Mon, 07 Feb 2011 01:18:06 +0000

You should also check out the Roles report in the BIDSHelper project http://bidshelper.codeplex.com

Comment on Integration Services in a SQL Server 2K8 Clustered Environment by Ted Krueger

Ted Krueger — Fri, 26 Mar 2010 01:52:17 +0000

>>it’s not REALLY active/active

Yeah, I know exactly what you are saying and agree. This might be a good connect suggestion to submit.

Comment on Integration Services in a SQL Server 2K8 Clustered Environment by admin

admin — Fri, 26 Mar 2010 01:42:46 +0000

Thanks for the comments Ted. I agree there are other ways of doing it so it’s not that bad. It’s just not what you would have expected. It’s kind of like when you have an ACTIVE/ACTIVE cluster….it’s not REALLY active/active per say, it’s multi-instance. You know what I’m saying?

Comment on Integration Services in a SQL Server 2K8 Clustered Environment by Ted Krueger

Ted Krueger — Fri, 26 Mar 2010 00:42:06 +0000

Hey John, I understand your frustration with the SSIS windows service. Although, it being a gateway to utilize SSMS for operations on SSIS package state and a few other simply tasks I don’t think qualifies it as a point of failure. Now that is argumentative in the terms and relations of a true DR or HA setup but given the fact the operations can be handled by other tools provided and also by the means it technically does not stop SSIS from functioning correctly, I can see the reasoning for not pushing as hard to get it in by the SSIS team.

I don’t disagree with you but think it may be harsh to say it is a failure by the team. I’m a big DR/HA guy and ‘everything’ should be considered but at the same time, the act of a disaster can have functions performed differently given that state of the systems.

Good post and I look forward to more from you.

Comment on Trigger Hell by John

John — Sun, 14 Mar 2010 18:06:49 +0000

Thanks for the comment Josef. Data integrity does indeed belong in the database but I do not believe the best place is in the triggers. The logic can be applied via triggers but 9 times out of ten it is better served in the calling procedures etc. The main reason opponents say they want to put it in the triggers is to save code and enforce the logic no matter which application hits the tables/views etc. Some people call it being efficient to reuse code while other just call it being lazy. I myself find it a nightmare to debug applications that have trigger after trigger for everything and I have found it much easier to avoid using triggers and apply it to the procs themselves. I’m not saying it is wrong, I just think it’s a lot cleaner. Would you rather pay the extra time when there is an issue or when you are developing? I myself think it is better to spend the time in development then when there is a critical production issue that needs to be tended to.