On different server?

HI All,
Currently we have two servers in our poduction farm. One runs
sharepoint and the other is the database server. Can i install
reporting services o nthe sharepoint server and tell it point to the
database server? Right now I have it installed the db server, but
would like to move it to the other server.
Any ideas
Thanks!
-SJOn Jul 5, 9:25 am, SJ <sjour...@.gmail.com> wrote:
> HI All,
> Currently we have two servers in our poduction farm. One runs
> sharepoint and the other is the database server. Can i install
> reporting services o nthe sharepoint server and tell it point to the
> database server? Right now I have it installed the db server, but
> would like to move it to the other server.
> Any ideas
> Thanks!
> -SJ
SJ,
Yes, you can install it on the sharepoint server and point it to the
DB server. During installation it will ask you the location of the DB
server.|||Yes, you can install Reporting Services on a computer without SQL Server
installed (as long as it has access to a SQL Server to store its meta data).
However, you need a SQL Server license for the computer where Reporting
Service runs.
"SJ" <sjourdan@.gmail.com> wrote in message
news:1183652738.671128.102340@.n60g2000hse.googlegroups.com...
> HI All,
> Currently we have two servers in our poduction farm. One runs
> sharepoint and the other is the database server. Can i install
> reporting services o nthe sharepoint server and tell it point to the
> database server? Right now I have it installed the db server, but
> would like to move it to the other server.
> Any ideas
> Thanks!
> -SJ
>|||On Jul 5, 1:38 pm, "Norman Yuan" <NotR...@.NotReal.not> wrote:
> Yes, you can install Reporting Services on a computer without SQL Server
> installed (as long as it has access to a SQL Server to store its meta data).
> However, you need a SQL Server license for the computer where Reporting
> Service runs.
> "SJ" <sjour...@.gmail.com> wrote in message
> news:1183652738.671128.102340@.n60g2000hse.googlegroups.com...
>
> > HI All,
> > Currently we have two servers in our poduction farm. One runs
> > sharepoint and the other is the database server. Can i install
> > reporting services o nthe sharepoint server and tell it point to the
> > database server? Right now I have it installed the db server, but
> > would like to move it to the other server.
> > Any ideas
> > Thanks!
> > -SJ- Hide quoted text -
> - Show quoted text -
Thank you both for the reply's I reall appreciate it!
-SJ

OLE DB Provider for ODBC/Win XP

I have SQL Server Developer Edition which runs on Windows XP and it has been
running fine thus far. I am now trying to run Analysis Services on it and it
needs OLE DB Provider for ODBC. I downloaded MDAC 2.8 and installed it on my
Windows XP platform. The installation went without a hitch but when I go to
Data Sources (ODBC), I cannot see OLE DB Provider for ODBC listed. Does OLE
DB Provider for ODBC only run on Windows 2000 or Windows NT?
Thanks,
AlistairOops, that should be OLE DB Provider for OLAP.
Alistair
"lestersal" <lestersal@.cox.net> wrote in message
news:yLs3c.40660$1k.22567@.okepread01...
> I have SQL Server Developer Edition which runs on Windows XP and it has
been
> running fine thus far. I am now trying to run Analysis Services on it and
it
> needs OLE DB Provider for ODBC. I downloaded MDAC 2.8 and installed it on
my
> Windows XP platform. The installation went without a hitch but when I go
to
> Data Sources (ODBC), I cannot see OLE DB Provider for ODBC listed. Does
OLE
> DB Provider for ODBC only run on Windows 2000 or Windows NT?
> Thanks,
> Alistair
>|||The Data Sources (ODBC) control panel applet only deals with ODBC data
sources and drivers. You are referring to an OLE DB provider.
OLE DB has a similar data sources interface. Try creating a empty text
file, and save it with a .udl file extension. Then double-click that file
and you should get the OLE DB interface.
Brannon Jones
Developer - MDAC
This posting is provided "as is" with no warranties and confers no rights.
"lestersal" <lestersal@.cox.net> wrote in message
news:5oA3c.40902$1k.38183@.okepread01...
> Oops, that should be OLE DB Provider for OLAP.
> Alistair
> "lestersal" <lestersal@.cox.net> wrote in message
> news:yLs3c.40660$1k.22567@.okepread01...
> been
and
> it
on
> my
> to
> OLE
>

OLE DB Command Stage: Capturing Rejects

Hello group, I have a question regarding the OLE DB Command Stage. Currently, I am reviewing a Data Flow that runs in production. This Data Flow Inserts to the various dimension tables in our warehouse. For a particular dimension table, the flow is like this:

Read Source records for Product combinations LookUp Product combinations against the current dimProduct table (cached in memory) Rows not found are then subjected to another LookUp on the dimProduct table (not cached). This is to find any rows inserted during the current run Rows not found are then Inserted to dimProduct using a Stored Procedure invoked by an OLE DB Command Successful Inserts then continue on, Rejected Inserts should be captured to a Flat File on our server for review.

Apparently, this last step has never been successful at capturing Rejects. Obviously, we would want to review these records to find the reason for failure. We get an empty file.

Currently, in the Stored Procedure we are using logic like this:

IF @.PRODUCTCOUNT <> 0

BEGIN

RAISERROR ('DUPLICATE PRODUCT!', 10, 1)

RETURN

END

Questions:

Is the RAISERROR command going to give us Output? Can we implement the OUTPUT command in our Proc invocation? I have not found any documentation that says the OLE DB Command Stage supports Error logging (Although columns are available to be added in the Input/Output columns tab?) Should we be using another Stage to accomplish this?

Any thoughts are welcome, thanks for your time!

rg

IF @.PRODUCTCOUNT <> 0

BEGIN

RAISERROR ('DUPLICATE PRODUCT!', 10, 1)

RETURN

END

In my experience, the error disposition on the OLE DB Command does not work. At least I haven't been able to get it to work. It will ignore RAISERROR statements, yet fail the component on a divide by zero, but never redirect a row. Even if the error redirection did work, you wouldn't be able to get the error description you're trying to raise.

Happily, output parameters DO work (which still surprises me since it isn't documented and isn't really intuitive). I recommend you use an output parameter for the error description, assign it to a column in the data flow, and put a Conditional Split right after the OLE DB Command evaluating the column to roll your own error redirection.

|||

Jay, thanks for the tip. The research was leading me in the direction that the error disposition was less than robust. Thanks for the confirmation, I will pursue using OUTPUT parameters for this data flow.

Thanks for the help! I have much more experience with a different ETL toolset, so even the little things right now are a challenge.

OLE DB Command not updating

I have a data flow task, and in that is an OLE DB Source that upon success, connects to an OLE DB Command. The OLE DB Source runs a sql command from a variable. (I've tested the sql; it parses and returns values.) The OLE DB Command is a very simple update sql statement with one column mapping. When I execute the task, it says it is successful, but when I check the table, nothing has been updated. I have ensured the connection is successful, and I am connecting to the correct db. Any suggestions would be helpful! Thanks!

Use SQL Profiler to capture the SQL statements that are being sent to the database. Odds are there is something related to the parameter mapping that is preventing the command from doing what you need it to.

Another thing to check is to ensure that the commands are being executed against the database that you think they are. If you have multiple connection managers, this can be easy to do.

|||

I found the problem. The variable used in the OLE DB source I thought I had changed to call a new stored procedure. However, its value was not actually changing and it was calling the wrong procedure, returning no values. My next question is why when I change the value in the properties window, does the variable not take the change?

|||Is the variables EvaluateAsExpression property set to true? This would cause that behavior.|||

Lindsay wrote:

I found the problem. The variable used in the OLE DB source I thought I had changed to call a new stored procedure. However, its value was not actually changing and it was calling the wrong procedure, returning no values. My next question is why when I change the value in the properties window, does the variable not take the change?

Did SQL Profiler end up being useful?

|||

Phil, yes the EvaluateAsExpression property was set to True; how embarassing LOL. Thank you!!

|||

Matthew, I've never used SQL Profiler before today, and am not familiar with it. I must need to modify the trace, because it has been running for a few hours now (actually I totally forgot about it)!!

|||

Lindsay wrote:

Matthew, I've never used SQL Profiler before today, and am not familiar with it. I must need to modify the trace, because it has been running for a few hours now (actually I totally forgot about it)!!

Oh no! It's probably best to just stop the trace at this point.

I'm sorry - I didn't mean to make things more complex. If you start the trace right before you run the package, and then stop it right after the package completes, you can then look through a (relatively) small set of queries sent to the server. In t his context, one of them should leap out because it the same query repeating over and over again. There are many ways to filter the data before and after it's recorded, but this is often the quickest and easiest way to see what the client application (in this case, SSIS) is REALLY sending to the server.