Not a valid Report Server Database?

I had to reinstall RS. While reinstalling Reporting Services I received an
error. I am at the point of specifying the report server database and I
tried to use the default, "ReportServer", which is the same as I used before.
The error = "A database with the specified name(ReportServer) already exists
and is not a valid Report Server Database. You must either remove the
existing database or specify a new database name.
According to my documentation I should be able to use the existing name and
the reinstall will not lose my existing reports.
Any idea why I would get this message?
--
DonI'm getting the same message. Anybody got any ideas?|||Are you connected to a database that was created by report server setup?
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
<butter-ball@.usa.net> wrote in message
news:1106160275.812278.14380@.z14g2000cwz.googlegroups.com...
> I'm getting the same message. Anybody got any ideas?
>

Non-ANSI Outer Join in MSSQL2K5

Hi,
When we ran upgrade advisor for 2005 against our existing database, we
received the following error message.
The query uses non-ANSI outer join operators ("*="or "=*"). to run this
query without modification, please set the compatiblity level for current
database to 80 or lower, using stored procedure SP_dbcmptlevel. it is
strongly recommended to rewrite the query using ANSI outer join operators
(LEFT OUTER JOIN, RIGTH OUTER JOIN). in the future versions of SQL server,
non-ANSI join operators will not be supported even in backward compatibility
modes.
We have quite a few files/objects where we have the non-ANSI standard outer
join syntax that we would have to convert to use the ANSI outer join. Does
anyone know of any tool that will automatically convert out non-ANSI outer
join to the ANSI one? This would definitely save us a lot of time during our
migration to SQL Server 2005. Any help is appreciated.
Thanks,
DeeI dont know of such a tool. One of the reasons why the old syntax is
deprecated is because of its inherent ambiguity. There has never been a
formal, standard definition of how to interpret queries that contain both
inner and outer style predicates in the WHERE clause. For that reason any
automated method of conversion to the new syntax probably couldn't be 100%
reliable.
--
David Portas
SQL Server MVP
--

non paged pool is empty error

I have received the following error
The server was unable to allocate from the system nonpaged pool because the
pool was empty.
Any idea on how to trap which process is causing the memory to leak or be
used up. This has caused SQL Server to be unavailable. I had to reboot as a
fix
I would like to trap it before it happens again. Any way to do so ?
Using Win2K3 and SQL 2KHi Hassan
I would expect this to be a gradual therefore monitoring the memory usage
over time would possibly indicate which process is not releasing memory.
Check out
http://www.microsoft.com/technet/prodtechnol/exchange/Guides/TrblshtE2k3Perf/7a44b064-8872-4edf-aac7-36b2a17f662a.mspx?mfr=true
and the perfmon counters in http://ask.support.microsoft.com/kb/133384
Also see if this applies:
http://support.microsoft.com/default.aspx?scid=kb;en-us;272568&sd=ee
John
"Hassan" wrote:
> I have received the following error
> The server was unable to allocate from the system nonpaged pool because the
> pool was empty.
> Any idea on how to trap which process is causing the memory to leak or be
> used up. This has caused SQL Server to be unavailable. I had to reboot as a
> fix
> I would like to trap it before it happens again. Any way to do so ?
>
> Using Win2K3 and SQL 2K
>
>
>

non paged pool is empty error

I have received the following error
The server was unable to allocate from the system nonpaged pool because the
pool was empty.
Any idea on how to trap which process is causing the memory to leak or be
used up. This has caused SQL Server to be unavailable. I had to reboot as a
fix
I would like to trap it before it happens again. Any way to do so ?
Using Win2K3 and SQL 2KHi Hassan
I would expect this to be a gradual therefore monitoring the memory usage
over time would possibly indicate which process is not releasing memory.
Check out
http://www.microsoft.com/technet/pr...a.mspx?mfr=true
and the perfmon counters in http://ask.support.microsoft.com/kb/133384
Also see if this applies:
http://support.microsoft.com/defaul...us;272568&sd=ee
John
"Hassan" wrote:

> I have received the following error
> The server was unable to allocate from the system nonpaged pool because th
e
> pool was empty.
> Any idea on how to trap which process is causing the memory to leak or be
> used up. This has caused SQL Server to be unavailable. I had to reboot as
a
> fix
> I would like to trap it before it happens again. Any way to do so ?
>
> Using Win2K3 and SQL 2K
>
>
>

non paged pool is empty error

I have received the following error
The server was unable to allocate from the system nonpaged pool because the
pool was empty.
Any idea on how to trap which process is causing the memory to leak or be
used up. This has caused SQL Server to be unavailable. I had to reboot as a
fix
I would like to trap it before it happens again. Any way to do so ?
Using Win2K3 and SQL 2K
Hi Hassan
I would expect this to be a gradual therefore monitoring the memory usage
over time would possibly indicate which process is not releasing memory.
Check out
http://www.microsoft.com/technet/prodtechnol/exchange/Guides/TrblshtE2k3Perf/7a44b064-8872-4edf-aac7-36b2a17f662a.mspx?mfr=true
and the perfmon counters in http://ask.support.microsoft.com/kb/133384
Also see if this applies:
http://support.microsoft.com/default.aspx?scid=kb;en-us;272568&sd=ee
John
"Hassan" wrote:

> I have received the following error
> The server was unable to allocate from the system nonpaged pool because the
> pool was empty.
> Any idea on how to trap which process is causing the memory to leak or be
> used up. This has caused SQL Server to be unavailable. I had to reboot as a
> fix
> I would like to trap it before it happens again. Any way to do so ?
>
> Using Win2K3 and SQL 2K
>
>
>