Replace SQL server in multiple server network

Hello all DBAs
what is the best methodolgy to replace a server with a new server in a
multiple sql server environment.. Is is using back up/restore to
another/bridge type server then rename servers or is it to bring in new
server then tranfer the datafiles. Does tranfering the data files
include logins and jobs ?? Or is ther a better way that I have not
realised?

Bill

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!"William Logan" <kwiso@.msn.com> wrote in message
news:4152f0c3$0$26150$c397aba@.news.newsgroups.ws.. .
> Hello all DBAs
> what is the best methodolgy to replace a server with a new server in a
> multiple sql server environment.. Is is using back up/restore to
> another/bridge type server then rename servers or is it to bring in new
> server then tranfer the datafiles. Does tranfering the data files
> include logins and jobs ?? Or is ther a better way that I have not
> realised?

Funny you should ask that.

I'm doing that right now. The complication is one of our larger databases
has file corruption that is preventing me from doing backups.

So... for all but one user database the plan will be to do a full backup
from the source machine and then restore to the new machine.

Then, at the proper time, shut down the source machine, perform a
transaction backup, then restore that to the destination machine.

As for user logins, jobs, etc. There are DTS packages that will help.
(though the DTS job to move logins does NOT move the sid, so you either have
to script that by hand or you have to do a sp_change_users_login for each
user in each database.

MS has several KB articles you can search for that outline some of the
steps.

So far the transfer looks to be fairly straightforward (other than that one
DB I've got to do by hand.)

> Bill
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Thanx that is what I thought and told my cio I was told to do it another
way like copying the files over by some else I like my way better thanx
Bill

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||If you can afford the downtime a simple detach and reattach should do
the trick pretty quickly with minimal overhead. You just have to wait
for the files to copy from one server to the next.

Its usually much faster than a backup and restore.

Then run some scripts to re-permission the users, You can then use DTS
packages to move your jobs and DTS packages to the new server.

Either way you need to figure out how to repermission and move jobs...
why spend the extra time on a backup and restore?|||"Bill" <nospam@.devdex.com> wrote in message
news:4154423e$0$26123$c397aba@.news.newsgroups.ws.. .
> Thanx that is what I thought and told my cio I was told to do it another
> way like copying the files over by some else I like my way better thanx

Well, it depends.

If I could afford the downtime, I'd probably detach the databases from the
primary server and copy them to the secondary and then re-attach them. Much
simpler.

But I can't afford the downtime that would require in my case.

> Bill
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

repairing damaged sql server MDF and LDF files

Hi All,
My SQL server's data files all corrupted during a severe power failure, we manage to get back the data files and reinstall the sql server. but unforunately we failed to attaching the database back to the server. The error message indicating it is caused b
y corrupted MDF or LDF files.
Is there a way to perform a file level repair before we can attach it back to sql server again ?
Any help is very much appreciated.
Bernard Gh
Hi,
Can you post the error you are getting while attaching the database.
If the MDF file is corrupted you have to either contact Microsoft product
support or restore from a valid full backup and restore the subsequent
transaction log backups in sequence.
Note:
During this situation even if you recover the database data integrity will
be lost. I recommend you to restore from full backup.
Thanks
Hari
MCDBA
"SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> Hi All,
> My SQL server's data files all corrupted during a severe power failure, we
manage to get back the data files and reinstall the sql server. but
unforunately we failed to attaching the database back to the server. The
error message indicating it is caused by corrupted MDF or LDF files.
> Is there a way to perform a file level repair before we can attach it back
to sql server again ?
> Any help is very much appreciated.
> Bernard Gh
|||I have been in the same situation with customers before. This is why you
have a fault tolerant RAID set(5, 1, 10, or 0+1), use Log Shipping and have
good backup plans. Sometimes things break and you don't get to piece them
together.
We often use a secondary IDE drive that the SCSI drives only dump
transaction backups to every 2-5 minutes. Hence, if the power goes out 1.)
the controller should have an onboard battery to complete the write or fail
it, 2.) we are never more than 2 minutes from the last 'good' state.
Plan for failure, because it will come:wether hardware, software or
intrusion.
Sorry,
Tim
"SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> Hi All,
> My SQL server's data files all corrupted during a severe power failure, we
manage to get back the data files and reinstall the sql server. but
unforunately we failed to attaching the database back to the server. The
error message indicating it is caused by corrupted MDF or LDF files.
> Is there a way to perform a file level repair before we can attach it back
to sql server again ?
> Any help is very much appreciated.
> Bernard Gh
|||with
EXEC sp_attach_db @.dbname = N'IMISWEB_OTHER',
@.filename1 = N'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHER_Data.MDF',
@.filename2 = N'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHER_LOG.LDF'
I got following:
Server: Msg 5172, Level 16, State 15, Line 1
The header for file 'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHER_LOG.LDF' is not a valid database file header. The PageAudit property is incorrect.
With
EXEC sp_attach_single_file_db @.dbname = 'IMISWEB_OTHER',
@.physname = 'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHER_Data.MDF'
I got the following:
Server: Msg 5172, Level 16, State 15, Line 1
The header for file 'K:\Program Files\Microsoft SQL Server\MSSQL\data\IMISWEB_OTHER_Log.LDF' is not a valid database file header. The PageAudit property is incorrect.
Server: Msg 5170, Level 16, State 1, Line 1
Cannot create file 'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHER_log.LDF' because it already exists.
Server: Msg 1813, Level 16, State 1, Line 1
Could not open new database 'IMISWEB_OTHER'. CREATE DATABASE is aborted.
Device activation error. The physical file name 'K:\Program Files\Microsoft SQL Server\MSSQL\data\IMISWEB_OTHER_Log.LDF' may be incorrect.
Bernard goh
"Hari Prasad" wrote:

> Hi,
> Can you post the error you are getting while attaching the database.
> If the MDF file is corrupted you have to either contact Microsoft product
> support or restore from a valid full backup and restore the subsequent
> transaction log backups in sequence.
>
> Note:
> During this situation even if you recover the database data integrity will
> be lost. I recommend you to restore from full backup.
> Thanks
> Hari
> MCDBA
>
> "SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
> news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> manage to get back the data files and reinstall the sql server. but
> unforunately we failed to attaching the database back to the server. The
> error message indicating it is caused by corrupted MDF or LDF files.
> to sql server again ?
>
>

repairing damaged sql server MDF and LDF files

Hi All,
My SQL server's data files all corrupted during a severe power failure, we m
anage to get back the data files and reinstall the sql server. but unforunat
ely we failed to attaching the database back to the server. The error messag
e indicating it is caused b
y corrupted MDF or LDF files.
Is there a way to perform a file level repair before we can attach it back t
o sql server again ?
Any help is very much appreciated.
Bernard GhHi,
Can you post the error you are getting while attaching the database.
If the MDF file is corrupted you have to either contact Microsoft product
support or restore from a valid full backup and restore the subsequent
transaction log backups in sequence.
Note:
During this situation even if you recover the database data integrity will
be lost. I recommend you to restore from full backup.
Thanks
Hari
MCDBA
"SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> Hi All,
> My SQL server's data files all corrupted during a severe power failure, we
manage to get back the data files and reinstall the sql server. but
unforunately we failed to attaching the database back to the server. The
error message indicating it is caused by corrupted MDF or LDF files.
> Is there a way to perform a file level repair before we can attach it back
to sql server again ?
> Any help is very much appreciated.
> Bernard Gh|||I have been in the same situation with customers before. This is why you
have a fault tolerant RAID set(5, 1, 10, or 0+1), use Log Shipping and have
good backup plans. Sometimes things break and you don't get to piece them
together.
We often use a secondary IDE drive that the SCSI drives only dump
transaction backups to every 2-5 minutes. Hence, if the power goes out 1.)
the controller should have an onboard battery to complete the write or fail
it, 2.) we are never more than 2 minutes from the last 'good' state.
Plan for failure, because it will come:wether hardware, software or
intrusion.
Sorry,
Tim
"SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> Hi All,
> My SQL server's data files all corrupted during a severe power failure, we
manage to get back the data files and reinstall the sql server. but
unforunately we failed to attaching the database back to the server. The
error message indicating it is caused by corrupted MDF or LDF files.
> Is there a way to perform a file level repair before we can attach it back
to sql server again ?
> Any help is very much appreciated.
> Bernard Gh|||with
EXEC sp_attach_db @.dbname = N'IMISWEB_OTHER',
@.filename1 = N'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHE
R_Data.MDF',
@.filename2 = N'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHE
R_LOG.LDF'
I got following:
Server: Msg 5172, Level 16, State 15, Line 1
The header for file 'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWE
B_OTHER_LOG.LDF' is not a valid database file header. The PageAudit property
is incorrect.
With
EXEC sp_attach_single_file_db @.dbname = 'IMISWEB_OTHER',
@.physname = 'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHER_
Data.MDF'
I got the following:
Server: Msg 5172, Level 16, State 15, Line 1
The header for file 'K:\Program Files\Microsoft SQL Server\MSSQL\data\IMISWE
B_OTHER_Log.LDF' is not a valid database file header. The PageAudit property
is incorrect.
Server: Msg 5170, Level 16, State 1, Line 1
Cannot create file 'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB
_OTHER_log.LDF' because it already exists.
Server: Msg 1813, Level 16, State 1, Line 1
Could not open new database 'IMISWEB_OTHER'. CREATE DATABASE is aborted.
Device activation error. The physical file name 'K:\Program Files\Microsoft
SQL Server\MSSQL\data\IMISWEB_OTHER_Log.LDF' may be incorrect.
Bernard goh
"Hari Prasad" wrote:

> Hi,
> Can you post the error you are getting while attaching the database.
> If the MDF file is corrupted you have to either contact Microsoft product
> support or restore from a valid full backup and restore the subsequent
> transaction log backups in sequence.
>
> Note:
> During this situation even if you recover the database data integrity will
> be lost. I recommend you to restore from full backup.
> Thanks
> Hari
> MCDBA
>
> "SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
> news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> manage to get back the data files and reinstall the sql server. but
> unforunately we failed to attaching the database back to the server. The
> error message indicating it is caused by corrupted MDF or LDF files.
> to sql server again ?
>
>

repairing damaged sql server MDF and LDF files

Hi All,
My SQL server's data files all corrupted during a severe power failure, we manage to get back the data files and reinstall the sql server. but unforunately we failed to attaching the database back to the server. The error message indicating it is caused by corrupted MDF or LDF files.
Is there a way to perform a file level repair before we can attach it back to sql server again ?
Any help is very much appreciated.
Bernard GhHi,
Can you post the error you are getting while attaching the database.
If the MDF file is corrupted you have to either contact Microsoft product
support or restore from a valid full backup and restore the subsequent
transaction log backups in sequence.
Note:
During this situation even if you recover the database data integrity will
be lost. I recommend you to restore from full backup.
Thanks
Hari
MCDBA
"SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> Hi All,
> My SQL server's data files all corrupted during a severe power failure, we
manage to get back the data files and reinstall the sql server. but
unforunately we failed to attaching the database back to the server. The
error message indicating it is caused by corrupted MDF or LDF files.
> Is there a way to perform a file level repair before we can attach it back
to sql server again ?
> Any help is very much appreciated.
> Bernard Gh|||I have been in the same situation with customers before. This is why you
have a fault tolerant RAID set(5, 1, 10, or 0+1), use Log Shipping and have
good backup plans. Sometimes things break and you don't get to piece them
together.
We often use a secondary IDE drive that the SCSI drives only dump
transaction backups to every 2-5 minutes. Hence, if the power goes out 1.)
the controller should have an onboard battery to complete the write or fail
it, 2.) we are never more than 2 minutes from the last 'good' state.
Plan for failure, because it will come:wether hardware, software or
intrusion.
Sorry,
Tim
"SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> Hi All,
> My SQL server's data files all corrupted during a severe power failure, we
manage to get back the data files and reinstall the sql server. but
unforunately we failed to attaching the database back to the server. The
error message indicating it is caused by corrupted MDF or LDF files.
> Is there a way to perform a file level repair before we can attach it back
to sql server again ?
> Any help is very much appreciated.
> Bernard Gh|||I found this program on the web...we just had the same
thing happen and I wondered if anyone has used it (I
posted this as a topic)...it's called MSSQLRECOVERY 2.0
and can be found at www.mssqlrecovery.com
Kevin
>--Original Message--
>Hi All,
>My SQL server's data files all corrupted during a severe
power failure, we manage to get back the data files and
reinstall the sql server. but unforunately we failed to
attaching the database back to the server. The error
message indicating it is caused by corrupted MDF or LDF
files.
>Is there a way to perform a file level repair before we
can attach it back to sql server again ?
>Any help is very much appreciated.
>Bernard Gh
>.
>|||Hi there,
We have tried that, but the result isn't impressive for us (2 tables out of 20+), perhaps the corruption is too servere for our case. but you can try your luck.
what other program have you tried ?
--
Bernard goh
"Kevin" wrote:
> I found this program on the web...we just had the same
> thing happen and I wondered if anyone has used it (I
> posted this as a topic)...it's called MSSQLRECOVERY 2.0
> and can be found at www.mssqlrecovery.com
> Kevin
>
> >--Original Message--
> >Hi All,
> >
> >My SQL server's data files all corrupted during a severe
> power failure, we manage to get back the data files and
> reinstall the sql server. but unforunately we failed to
> attaching the database back to the server. The error
> message indicating it is caused by corrupted MDF or LDF
> files.
> >
> >Is there a way to perform a file level repair before we
> can attach it back to sql server again ?
> >
> >Any help is very much appreciated.
> >
> >Bernard Gh
> >.
> >
>

Rendering true Excel

My users are complaining that the Excel files they are getting back from
the web application's rendering of reports in Excel mode are not true
Excel, but rather still retain HTML. Has anyone else experienced this?
I have included my rendering code snippet below:
--
try
{
data = render.RunReport(ConfigurationSettings.AppSettings[ePledgeConstants.REPORT_SERVER_URL_PROPERTY],
fullReportName, reportParameters, format, out
encoding,
out mimeType, out parametersUsed, out warnings,
out streamIds);
Response.Clear();
Response.ContentType = mimeType;
string fileName = report.Name +
GetFileExtension(mimeType);
if (mimeType != "text/html")
{
Response.AddHeader("Content-Disposition",
"attachment; filename=" + fileName);
}
switch(encoding)
{
case "Unicode (UTF-8)":
Response.ContentEncoding = new UTF8Encoding();
break;
case "Unicode (UTF-7)":
Response.ContentEncoding = new UTF7Encoding();
break;
default:
Response.ContentEncoding = new UTF8Encoding();
break;
}
Response.BinaryWrite(data);
}
catch (Exception exception)
{
Console.Out.Write(exception.ToString());
}
---
The run report method in turn is like this:
---
public byte[] RunReport(string ServerUrl, string ReportName,
ParameterValue[] parameters, string Format, out string encoding, out
string mimeType, out ParameterValue[] parametersUsed, out Warning[]
warnings, out string[] streamIds)
{
ReportingService rs = new ReportingService();
rs.Timeout = -1;
rs.Url = ServerUrl;
rs.Credentials = new NetworkCredential(UserName, Password);
return rs.Render(ReportName, Format, null, null, parameters, null,
null, out encoding, out mimeType, out parametersUsed, out warnings,
out streamIds);
}Have you deployed Reporting Services SP1. In SP1, we output native XLS.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bryon" <blape@.whittmanhart.com> wrote in message
news:OVl$MrGGFHA.2932@.TK2MSFTNGP15.phx.gbl...
> My users are complaining that the Excel files they are getting back from
> the web application's rendering of reports in Excel mode are not true
> Excel, but rather still retain HTML. Has anyone else experienced this? I
> have included my rendering code snippet below:
> --
> try
> {
> data => render.RunReport(ConfigurationSettings.AppSettings[ePledgeConstants.REPORT_SERVER_URL_PROPERTY],
> fullReportName, reportParameters, format, out
> encoding,
> out mimeType, out parametersUsed, out warnings, out
> streamIds);
> Response.Clear();
> Response.ContentType = mimeType;
> string fileName = report.Name +
> GetFileExtension(mimeType);
> if (mimeType != "text/html")
> {
> Response.AddHeader("Content-Disposition",
> "attachment; filename=" + fileName);
> }
> switch(encoding)
> {
> case "Unicode (UTF-8)":
> Response.ContentEncoding = new UTF8Encoding();
> break;
> case "Unicode (UTF-7)":
> Response.ContentEncoding = new UTF7Encoding();
> break;
> default:
> Response.ContentEncoding = new UTF8Encoding();
> break;
> }
> Response.BinaryWrite(data);
> }
> catch (Exception exception)
> {
> Console.Out.Write(exception.ToString());
> }
> ---
> The run report method in turn is like this:
> ---
> public byte[] RunReport(string ServerUrl, string ReportName,
> ParameterValue[] parameters, string Format, out string encoding, out
> string mimeType, out ParameterValue[] parametersUsed, out Warning[]
> warnings, out string[] streamIds)
> {
> ReportingService rs = new ReportingService();
> rs.Timeout = -1;
> rs.Url = ServerUrl;
> rs.Credentials = new NetworkCredential(UserName, Password);
> return rs.Render(ReportName, Format, null, null, parameters, null,
> null, out encoding, out mimeType, out parametersUsed, out warnings, out
> streamIds);
> }|||Lukasz Pawlowski [MSFT] wrote:
> Have you deployed Reporting Services SP1. In SP1, we output native XLS.
> -Lukasz
>
Yes I have.
An interesting side note to this problem is that on a Mac, it only sees
the HTML, never the Excel information. In Windows, the file looks like
Excel, but does not save as Excel.
Also, is there a way to display gridlines? The Excel comes back as
Excel for the web and does not have gridlines by default.|||Grid lines are based on how you designed your report. If you created for
example a table with inner boarders, you should see grid lines.
Are you supplying any device info parameters to your excel rendering?
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bryon" <blape@.whittmanhart.com> wrote in message
news:%23ynRKTHGFHA.128@.TK2MSFTNGP14.phx.gbl...
> Lukasz Pawlowski [MSFT] wrote:
>> Have you deployed Reporting Services SP1. In SP1, we output native XLS.
>> -Lukasz
>>
> Yes I have.
> An interesting side note to this problem is that on a Mac, it only sees
> the HTML, never the Excel information. In Windows, the file looks like
> Excel, but does not save as Excel.
> Also, is there a way to display gridlines? The Excel comes back as Excel
> for the web and does not have gridlines by default.|||Lukasz Pawlowski [MSFT] wrote:
> Grid lines are based on how you designed your report. If you created for
> example a table with inner boarders, you should see grid lines.
> Are you supplying any device info parameters to your excel rendering?
> -Lukasz
>
I'm not sure what you mean by device parameters.

Rendering to Excel - Crash - Server Application Unavailable - Out of RAM

I have a very simple report which generates a large amount or rows -
63,000. When I run the report all goes to plan and the data it
brought back and I can page through its 1336 returned pages. But I
need to be able to export all of this data ro excel, but when I try it
works away for a bit before eventually "crashing" and returning -
"
Server Application Unavailable
The web application you are attempting to access on this web server is
currently unavailable. Please hit the "Refresh" button in your web
browser to retry your request.
Administrator Note: An error message detailing the cause of this
specific request failure can be found in the application event log of
the web server. Please review this log entry to discover what caused
this error to occur.
"
In the loogs it says -
aspnet_wp.exe (PID: 2352) was recycled because memory consumption
exceeded the 306 MB (60 percent of available RAM).
yet I can go to Excel and go Data - Import External Data - New
Database Query and run the sql from there and export it to excel and
it works fine, and pretty quickly.
Is there anyway around this' I need to find someway to be able to
render my report from my reporting application in Excel for clients...
ThanksUnfortunately Reporting Services was designed to handle very big reports
since it renders 'in memory'. As you've seen from your error the server is
running out of memory. You could try to redesign the report into smaller
reports or try adding more memory on the server.
--
Adrian M.
MCP
"Gearoid" <gearoid_healy@.yahoo.com> wrote in message
news:3d6ebe80.0503300120.1b92ac6f@.posting.google.com...
>I have a very simple report which generates a large amount or rows -
> 63,000. When I run the report all goes to plan and the data it
> brought back and I can page through its 1336 returned pages. But I
> need to be able to export all of this data ro excel, but when I try it
> works away for a bit before eventually "crashing" and returning -
> "
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web
> browser to retry your request.
> Administrator Note: An error message detailing the cause of this
> specific request failure can be found in the application event log of
> the web server. Please review this log entry to discover what caused
> this error to occur.
> "
> In the loogs it says -
> aspnet_wp.exe (PID: 2352) was recycled because memory consumption
> exceeded the 306 MB (60 percent of available RAM).
> yet I can go to Excel and go Data - Import External Data - New
> Database Query and run the sql from there and export it to excel and
> it works fine, and pretty quickly.
> Is there anyway around this' I need to find someway to be able to
> render my report from my reporting application in Excel for clients...
> Thanks|||> Unfortunately Reporting Services wasn't designed to handle very big
> reports since it renders 'in memory'.
--
Adrian M.
MCP
"Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
news:uClX4mSNFHA.2468@.tk2msftngp13.phx.gbl...
> Unfortunately Reporting Services was designed to handle very big reports
> since it renders 'in memory'. As you've seen from your error the server
> is running out of memory. You could try to redesign the report into
> smaller reports or try adding more memory on the server.
> --
> Adrian M.
> MCP
> "Gearoid" <gearoid_healy@.yahoo.com> wrote in message
> news:3d6ebe80.0503300120.1b92ac6f@.posting.google.com...
>>I have a very simple report which generates a large amount or rows -
>> 63,000. When I run the report all goes to plan and the data it
>> brought back and I can page through its 1336 returned pages. But I
>> need to be able to export all of this data ro excel, but when I try it
>> works away for a bit before eventually "crashing" and returning -
>> "
>> Server Application Unavailable
>> The web application you are attempting to access on this web server is
>> currently unavailable. Please hit the "Refresh" button in your web
>> browser to retry your request.
>> Administrator Note: An error message detailing the cause of this
>> specific request failure can be found in the application event log of
>> the web server. Please review this log entry to discover what caused
>> this error to occur.
>> "
>> In the loogs it says -
>> aspnet_wp.exe (PID: 2352) was recycled because memory consumption
>> exceeded the 306 MB (60 percent of available RAM).
>> yet I can go to Excel and go Data - Import External Data - New
>> Database Query and run the sql from there and export it to excel and
>> it works fine, and pretty quickly.
>> Is there anyway around this' I need to find someway to be able to
>> render my report from my reporting application in Excel for clients...
>> Thanks
>|||Adrian M. wrote:
> Unfortunately Reporting Services was designed to handle very big reports
> since it renders 'in memory'. As you've seen from your error the server is
> running out of memory. You could try to redesign the report into smaller
> reports or try adding more memory on the server.
>
"try adding more memory on the server" - COOL! Worst recomendation ever
seen! How about to redesign RS? Why I don't have such problems in "old
fashion" developing (pre-dotnet)?
For example, I have some data. If I'll export this data as CSV then it
tools 10 MB. But then I'm truing to export same data as Excel - server
dies and tooks 400MB of RAM. My personal "reporter" tooks much less
resources! I this normal? Is this problem with my server?
I think - not. This is problem of R$ and M$.
How I can use RS for ENTERPRISE reporting if it cannot work with large
amounts of data? Only with tiny data (1000 records or less).
Also RS has huge memory management issues. How about to give away unused
memory back to system? Where is magical GC?|||I actually have some suggestions for you to try, but after your rant I have
decided not to share them with you.
--
Adrian M.
MCP
"Alexey Pavlov" <alexey_pavlov@.navigator.lv> wrote in message
news:umsEHynNFHA.3728@.TK2MSFTNGP10.phx.gbl...
> Adrian M. wrote:
>> Unfortunately Reporting Services was designed to handle very big reports
>> since it renders 'in memory'. As you've seen from your error the server
>> is running out of memory. You could try to redesign the report into
>> smaller reports or try adding more memory on the server.
> "try adding more memory on the server" - COOL! Worst recomendation ever
> seen! How about to redesign RS? Why I don't have such problems in "old
> fashion" developing (pre-dotnet)?
> For example, I have some data. If I'll export this data as CSV then it
> tools 10 MB. But then I'm truing to export same data as Excel - server
> dies and tooks 400MB of RAM. My personal "reporter" tooks much less
> resources! I this normal? Is this problem with my server?
> I think - not. This is problem of R$ and M$.
> How I can use RS for ENTERPRISE reporting if it cannot work with large
> amounts of data? Only with tiny data (1000 records or less).
> Also RS has huge memory management issues. How about to give away unused
> memory back to system? Where is magical GC?|||Adrian,
I have encountered the same issues with Reporting Services when over 90,000
records are being returned to a report. I am using a dedicated server with
2gb of RAM. We are currently getting an extra 2gb to assist in the load, but
I was wondering what your other options were other than reducing the criteria
of the report.
Any help you may be able to provide would be greatly appreciated.
"Adrian M." wrote:
> I actually have some suggestions for you to try, but after your rant I have
> decided not to share them with you.
> --
> Adrian M.
> MCP
>
> "Alexey Pavlov" <alexey_pavlov@.navigator.lv> wrote in message
> news:umsEHynNFHA.3728@.TK2MSFTNGP10.phx.gbl...
> > Adrian M. wrote:
> >> Unfortunately Reporting Services was designed to handle very big reports
> >> since it renders 'in memory'. As you've seen from your error the server
> >> is running out of memory. You could try to redesign the report into
> >> smaller reports or try adding more memory on the server.
> >>
> >
> > "try adding more memory on the server" - COOL! Worst recomendation ever
> > seen! How about to redesign RS? Why I don't have such problems in "old
> > fashion" developing (pre-dotnet)?
> >
> > For example, I have some data. If I'll export this data as CSV then it
> > tools 10 MB. But then I'm truing to export same data as Excel - server
> > dies and tooks 400MB of RAM. My personal "reporter" tooks much less
> > resources! I this normal? Is this problem with my server?
> > I think - not. This is problem of R$ and M$.
> >
> > How I can use RS for ENTERPRISE reporting if it cannot work with large
> > amounts of data? Only with tiny data (1000 records or less).
> >
> > Also RS has huge memory management issues. How about to give away unused
> > memory back to system? Where is magical GC?
>
>|||See my response to your other post.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"William Foster" <WilliamFoster@.discussions.microsoft.com> wrote in message
news:63F7E982-CCE1-43E7-A077-DB8B4240D35C@.microsoft.com...
> Adrian,
> I have encountered the same issues with Reporting Services when over
90,000
> records are being returned to a report. I am using a dedicated server
with
> 2gb of RAM. We are currently getting an extra 2gb to assist in the load,
but
> I was wondering what your other options were other than reducing the
criteria
> of the report.
> Any help you may be able to provide would be greatly appreciated.
> "Adrian M." wrote:
> > I actually have some suggestions for you to try, but after your rant I
have
> > decided not to share them with you.
> >
> > --
> > Adrian M.
> > MCP
> >
> >
> > "Alexey Pavlov" <alexey_pavlov@.navigator.lv> wrote in message
> > news:umsEHynNFHA.3728@.TK2MSFTNGP10.phx.gbl...
> > > Adrian M. wrote:
> > >> Unfortunately Reporting Services was designed to handle very big
reports
> > >> since it renders 'in memory'. As you've seen from your error the
server
> > >> is running out of memory. You could try to redesign the report into
> > >> smaller reports or try adding more memory on the server.
> > >>
> > >
> > > "try adding more memory on the server" - COOL! Worst recomendation
ever
> > > seen! How about to redesign RS? Why I don't have such problems in "old
> > > fashion" developing (pre-dotnet)?
> > >
> > > For example, I have some data. If I'll export this data as CSV then it
> > > tools 10 MB. But then I'm truing to export same data as Excel - server
> > > dies and tooks 400MB of RAM. My personal "reporter" tooks much less
> > > resources! I this normal? Is this problem with my server?
> > > I think - not. This is problem of R$ and M$.
> > >
> > > How I can use RS for ENTERPRISE reporting if it cannot work with large
> > > amounts of data? Only with tiny data (1000 records or less).
> > >
> > > Also RS has huge memory management issues. How about to give away
unused
> > > memory back to system? Where is magical GC?
> >
> >
> >