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

On 2003 cluster (SQL 2000) connection pooling causes crash

For performance reasons we have (successfully) used pooling in our apps and
services on almost one hundred installations, NT 4.0 to 2000 servers (SQL
7.0 - 8.0), NT 4.0 to XP workstations without a problem in any combination.
Now with 5.2 (2003) server a local client is unable to connect and crashes
within the SQLDriverConnect call (SQLConnect as well). Does not return at
all.
When the same runs on any other client (4.0, 2000, XP), everything is OK.
The problem comes and goes with SQL_ATTR_CONNECTION_POOLING
100% sure the bug is not in our code - the pure MS-supplied code as shown in
Q164221 crashes precisely the same way.
When SQLSetEnvAttr(...SQL_ATTR_CONNECTION_POOLING...) is not used, it's ok,
BUT:
To quit using benefits of pooling is a solution with severe impact on
performance.
Any hint?
TIA
Jaroslav Pivonka
mailto:jpivonka@.centrum.cz
// Windows Server 2003, 2 in a cluster, SQL Server 2000 EE SP4 (8.00.2039)
Hi
I am assuming that your are not using AWE memory, as you should apply hotfix
2040 for SQL Server SP4
(http://support.microsoft.com/default...b;en-us;899761)
As to the connection pooling, check the versions of the ODBC drivers between
your various platforms. You will notice Windows 2003 has the most recent
one.
It may be a bug in the driver, or it may be that the feature is not working
anymore.
Do you have the same problem with Windows XP SP2 or Windows 2003 SP1?
If so, I would open a case with Microsoft Support Services.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jaroslav" <Jaroslav@.discussions.microsoft.com> wrote in message
news:1D39DE4D-FA1C-4A8B-A4D7-CBFCBB60D29A@.microsoft.com...
> For performance reasons we have (successfully) used pooling in our apps
> and
> services on almost one hundred installations, NT 4.0 to 2000 servers (SQL
> 7.0 - 8.0), NT 4.0 to XP workstations without a problem in any
> combination.
> Now with 5.2 (2003) server a local client is unable to connect and crashes
> within the SQLDriverConnect call (SQLConnect as well). Does not return at
> all.
> When the same runs on any other client (4.0, 2000, XP), everything is OK.
> The problem comes and goes with SQL_ATTR_CONNECTION_POOLING
> 100% sure the bug is not in our code - the pure MS-supplied code as shown
> in
> Q164221 crashes precisely the same way.
> When SQLSetEnvAttr(...SQL_ATTR_CONNECTION_POOLING...) is not used, it's
> ok,
> BUT:
> To quit using benefits of pooling is a solution with severe impact on
> performance.
> Any hint?
> TIA
> Jaroslav Pivonka
> mailto:jpivonka@.centrum.cz
> // Windows Server 2003, 2 in a cluster, SQL Server 2000 EE SP4 (8.00.2039)
>
|||"Mike Epprecht (SQL MVP)" wrote:

> Hi
> I am assuming that your are not using AWE memory, as you should apply hotfix
> 2040 for SQL Server SP4
> (http://support.microsoft.com/default...b;en-us;899761)
Negative. 2GB each server.
Moreover it seems to be an ODBC problem, not server.

> As to the connection pooling, check the versions of the ODBC drivers between
> your various platforms. You will notice Windows 2003 has the most recent
> one.
> It may be a bug in the driver, or it may be that the feature is not working
> anymore.
Hopefully the first is true and somebody will fix it soon.
So far we have put a switch outside, enabling us not to use pooling (default
is yes), into a couple of generic services running on the cluster so we can
leave all but two new systems as they were, and on the new installations
we'll keep waiting until a patch comes.

> Do you have the same problem with Windows XP SP2 or Windows 2003 SP1?
Up to XP SP2 using MDAC 2.8 SP1 everything works fine.
The problem came with Windows 2003 Server SP1 having MDAC 2.8. SP2

> If so, I would open a case with Microsoft Support Services.
Please try to check it. I have proven that freshly installed systems
(nothing but Win2003 SP1 w MDAC 2.8 SP2, SQL 2000 EE (8.00.2039)) fail to run
locally even the sample code shown in Q164221 (MS only, not a line of ours).
Remote clients (pre-2003) are ok.
Thanks
Jaroslav Pivonka
sql

OLEDB 7399

Hi everyone,
i have a great problem!
Unexpectedly, my Sql 2000 Server (enterprise edition) is
unable to query data from other sql 7 or 200o servers.
this is very strange, because it has never been appened
until last friday.
It's possible to create link to ather linked servers, but
when I try to do any select query, the erroe is 7399.
The knowledge base articles I have read unitl nuw have
been unuseless.
Please help me with any suggestion.
Thank's
GabrieleMake sure you are connecting to a SQL Server and not an Access database. Th
e error you are getting is for an OLEDB Connection to Access DB.|||I'm sure I'm using SQL.
This is the entire error I receive:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error. The provider did not give
any information about the error.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IUnknown::QueryInterface
returned 0x80004005: The provider did not give any information about
the error.].
Regards
Gabriele
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||
>--Original Message--
>Make sure you are connecting to a SQL Server and not an
Access database. The error you are getting is for an
OLEDB Connection to Access DB.
>.
>
I'm sure I'm using SQL.
This is the entire error I receive:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error. The provider
did not give
any information about the error.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
IUnknown::QueryInterface
returned 0x80004005: The provider did not give any
information about
the error.].
Regards
Gabriele

OLE/DB provider returned message: Deferred prepare could not be completed

I have 2 SQL servers. And in the first one I have added the second SQL as a Link Server. When I run an SQL statement on the linked server I get the following message.

Server: Msg 7202, Level 11, State 1, Line 1
Could not find server 'PROD' in sysservers. Execute sp_addlinkedserver to add the server to sysservers.
[OLE/DB provider returned message: Deferred prepare could not be completed.]

The SQL statement that I am runnins is

Select * from openquery(PROD,'Select * from PROD.GMS.dbo.qryDispCL')

But when I run only the SQL statement "Select * from PROD.GMS.dbo.qryDispCL" it works perfect. But I need to have the first statement running.

Please help. Your valuable feedback is greatly appriciated.

It's really strange... You can run this to check registered server:

EXEC sp_helpservers

If the server 'PROD' is not in the result, then run this to add it:

EXEC sp_addlinkedserver 'PROD'

Note: you may need to add login information for the 'PROD' server with 'sp_addlinkedsrvlogin'.

ole db, odbc, mdac what does enterprise manager register server use?

I hear a lot about different ways of pulling data off of sql servers.
When you go to register a server in enterprise manager what method of
data access is it using? ole db, odbc, ?
"tbone" <tony.despain@.gmail.com> wrote in message
news:1139251537.917459.100430@.g44g2000cwa.googlegr oups.com...
>I hear a lot about different ways of pulling data off of sql servers.
> When you go to register a server in enterprise manager what method of
> data access is it using? ole db, odbc, ?
>
My best guess is that it is using the SQL-DMO API. How the API is
connecting, who knows. I would guess that it is either using SQL OLE-DB, or
it may be using DBLib.
Rick Sawtell
MCT, MCSD, MCDBA

ole db, odbc, mdac what does enterprise manager register server use?

I hear a lot about different ways of pulling data off of sql servers.
When you go to register a server in enterprise manager what method of
data access is it using? ole db, odbc, ?"tbone" <tony.despain@.gmail.com> wrote in message
news:1139251537.917459.100430@.g44g2000cwa.googlegroups.com...
>I hear a lot about different ways of pulling data off of sql servers.
> When you go to register a server in enterprise manager what method of
> data access is it using? ole db, odbc, ?
>
My best guess is that it is using the SQL-DMO API. How the API is
connecting, who knows. I would guess that it is either using SQL OLE-DB, or
it may be using DBLib.
Rick Sawtell
MCT, MCSD, MCDBA

ole db, odbc, mdac what does enterprise manager register server use?

I hear a lot about different ways of pulling data off of sql servers.
When you go to register a server in enterprise manager what method of
data access is it using? ole db, odbc, ?"tbone" <tony.despain@.gmail.com> wrote in message
news:1139251537.917459.100430@.g44g2000cwa.googlegroups.com...
>I hear a lot about different ways of pulling data off of sql servers.
> When you go to register a server in enterprise manager what method of
> data access is it using? ole db, odbc, ?
>
My best guess is that it is using the SQL-DMO API. How the API is
connecting, who knows. I would guess that it is either using SQL OLE-DB, or
it may be using DBLib.
Rick Sawtell
MCT, MCSD, MCDBA

OLE DB provider ran out of memory

I run 2 sql servers same nt4 sp5 and server 1 has 2G
memory, server 1 is linked to server 3 and vice versa.
server 1 has a limit of 1.5G max memory setting for sql
server and I recently ran into this error when initiating
job from server03
OLE DB provider 'SQLOLEDB' reported an error.
The provider ran out of memory. [SQLSTATE 42000] (Error
7399) Could not relay results of procedure 'xxx' from
remote server 'server01'.
[SQLSTATE 42000] (Error 7221) Associated statement is not
prepared
[SQLSTATE HY007] (Error 0) OLE DB provider 'SQLOLEDB'
reported an error.
The provider ran out of memory. [SQLSTATE 42000] (Error
7399)
Could not relay results of procedure 'xxx' from remote
server 'server01'.
[SQLSTATE 42000] (Error 7221). The step failed.
not sure if it's a memory cache problem or what. at my
wits endThe problem is more than likely on Server 3 not 1. You say Server 1 has 2GB
with a 1.5GB max setting, what about Server 3? Linked Servers and OLEDB
type activity is usually taken from the memory to leave portion and not the
memory pool. Memory to leave can be adjusted by using the -g statup
parameter for sql server. I also suggest you set a mx memory on Server 3 if
not already.
Andrew J. Kelly
SQL Server MVP
"Paul" <anonymous@.discussions.microsoft.com> wrote in message
news:c33101c3ee91$64e3dfb0$a101280a@.phx.gbl...
> I run 2 sql servers same nt4 sp5 and server 1 has 2G
> memory, server 1 is linked to server 3 and vice versa.
> server 1 has a limit of 1.5G max memory setting for sql
> server and I recently ran into this error when initiating
> job from server03
> OLE DB provider 'SQLOLEDB' reported an error.
> The provider ran out of memory. [SQLSTATE 42000] (Error
> 7399) Could not relay results of procedure 'xxx' from
> remote server 'server01'.
> [SQLSTATE 42000] (Error 7221) Associated statement is not
> prepared
> [SQLSTATE HY007] (Error 0) OLE DB provider 'SQLOLEDB'
> reported an error.
> The provider ran out of memory. [SQLSTATE 42000] (Error
> 7399)
> Could not relay results of procedure 'xxx' from remote
> server 'server01'.
> [SQLSTATE 42000] (Error 7221). The step failed.
> not sure if it's a memory cache problem or what. at my
> wits end
>

OLE DB provider ran out of memory

I run 2 sql servers same nt4 sp5 and server 1 has 2G
memory, server 1 is linked to server 3 and vice versa.
server 1 has a limit of 1.5G max memory setting for sql
server and I recently ran into this error when initiating
job from server03
OLE DB provider 'SQLOLEDB' reported an error.
The provider ran out of memory. [SQLSTATE 42000] (Error
7399) Could not relay results of procedure 'xxx' from
remote server 'server01'.
[SQLSTATE 42000] (Error 7221) Associated statement is not
prepared
[SQLSTATE HY007] (Error 0) OLE DB provider 'SQLOLEDB'
reported an error.
The provider ran out of memory. [SQLSTATE 42000] (Error
7399)
Could not relay results of procedure 'xxx' from remote
server 'server01'.
[SQLSTATE 42000] (Error 7221). The step failed.
not sure if it's a memory cache problem or what. at my
wits endThe problem is more than likely on Server 3 not 1. You say Server 1 has 2GB
with a 1.5GB max setting, what about Server 3? Linked Servers and OLEDB
type activity is usually taken from the memory to leave portion and not the
memory pool. Memory to leave can be adjusted by using the -g statup
parameter for sql server. I also suggest you set a mx memory on Server 3 if
not already.
--
Andrew J. Kelly
SQL Server MVP
"Paul" <anonymous@.discussions.microsoft.com> wrote in message
news:c33101c3ee91$64e3dfb0$a101280a@.phx.gbl...
> I run 2 sql servers same nt4 sp5 and server 1 has 2G
> memory, server 1 is linked to server 3 and vice versa.
> server 1 has a limit of 1.5G max memory setting for sql
> server and I recently ran into this error when initiating
> job from server03
> OLE DB provider 'SQLOLEDB' reported an error.
> The provider ran out of memory. [SQLSTATE 42000] (Error
> 7399) Could not relay results of procedure 'xxx' from
> remote server 'server01'.
> [SQLSTATE 42000] (Error 7221) Associated statement is not
> prepared
> [SQLSTATE HY007] (Error 0) OLE DB provider 'SQLOLEDB'
> reported an error.
> The provider ran out of memory. [SQLSTATE 42000] (Error
> 7399)
> Could not relay results of procedure 'xxx' from remote
> server 'server01'.
> [SQLSTATE 42000] (Error 7221). The step failed.
> not sure if it's a memory cache problem or what. at my
> wits end
>

Old SQL Cluster to Join a New Domain?

Hi. In general terms, what would be the steps to have my
SQL2000 (on W2K OS) 2 node-clusters join a new domain?
They are member servers authenticating with a W2K DC on
their subnet, but we would like to install W2003 on that
DC (bare-metal NO upgrade, due to past history of AD
replication issues on that W2K DC. It's now the only DC
on it's own subnet, with very old AD info it. We figure
a clean install of W2003 with new clean domain would be
better).
Thanks.
Last time I did this, I just went into Windows, ignored the message that
popped up, and changed the domain name for each machine. (I stopped the
entire cluster first.)
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||Look at the following article:
HOW TO: Change Domains for a SQL Server 2000 Failover Cluster
http://support.microsoft.com/?id=319016
Rand
This posting is provided "as is" with no warranties and confers no rights.