Viewing 12 posts - 1 through 12 (of 12 total)
These types of people were the first ones we would weed out...When I would interview people and they didn't know the answer I would always follow up with "I don't...
April 8, 2019 at 2:55 pm
I so agree with Steve. I have not been heavily involved with day to day SQL Server for while now, however, I still educate myself on new functionality, technologies,...
April 8, 2019 at 2:41 pm
I admire all the work put in to accomplish this stuff. But now that Polybase is part of SQL Server, why wouldn't you connect directly to Hadoop from SQL...
July 26, 2017 at 7:29 am
You do know that if you are going to run SSAS and the database instance on the same server their are instance configurations that you need to make regarding SSAS...
April 26, 2016 at 7:19 am
This topic is one of the reasons in a presentation that I often do on the SSIS Catalog, I always begin with how to install the SSISDB and to reset...
March 29, 2016 at 8:11 am
The only thing that scares me is that according to Microsoft, for the stored procedure:
Maps an existing database user to a SQL Server login. This feature will be removed in...
February 23, 2016 at 7:16 am
I am with Ken on this one. I admire your solution but there are less complex ways of solving the problem. Good work though.
January 22, 2016 at 7:56 am
This is exactly why when I initially create environments I create them in TSQL using the SPROCs from SSISDB. In fact I have scripted entire deployments from folders, environments,...
January 21, 2016 at 7:34 am
First tried:
select * from $system.DISCOVER_COMMAND_OBJECTS and received
Executing the query ...
Obtained object of type: Microsoft.AnalysisServices.AdomdClient.AdomdDataReader
Execution complete
So then tried XMLA with restriction on SPID:
<Discover xmlns="urn:schemas-microsoft-com:xml-analysis">
<RequestType>DISCOVER_COMMAND_OBJECTS</RequestType>
<Restrictions>
<RestrictionList>
<SESSION_SPID>894</SESSION_SPID>
</RestrictionList>
</Restrictions>
<Properties></Properties>
</Discover>
Results:
<return xmlns="urn:schemas-microsoft-com:xml-analysis">
<root xmlns="urn:schemas-microsoft-com:xml-analysis:rowset" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"...
December 18, 2015 at 9:26 am
Personally I think executing Powershell scripts within SSIS sets a really bad precedent. There is probably a better solution. Just my opinion, but I would never allow...
December 3, 2015 at 6:45 am
If you are dealing with PHI and HIPPA data and the company has put in 'adequate' safeguards, everyone being HIPPA certified for example, then the responsibility does fall on the...
September 21, 2015 at 11:41 am
If you turned on package logging then you might want to try looking in dbo.sysssislog in MSDB on the server you are running the packages on.
July 27, 2015 at 7:44 am
Viewing 12 posts - 1 through 12 (of 12 total)