Rendering report: network

Showing posts with label network. Show all posts

Friday, March 23, 2012

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!

Monday, March 12, 2012

Repeated 'Starting up database' messages

Hi,
Our network monitoring software reported the following message :
The database "MSCRM" in the instance "MSSQLSERVER" is in a critical state.
The state is: Suspect
After looking at SQL Enterprise Manager, the database appears to be fine and
I can browse tables, views, stored procedures and query the database as
normal. However when I looked at the SQL Server Error Log I found many
messages reporting 'Starting up database 'MSCRM'.
Any ideas?
Jonathan
Here is a sample log from this morning :
2004-07-02 09:29:53.76 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:54.48 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:59.17 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:59.43 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:59.67 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:59.93 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:00.24 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:00.48 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:00.82 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:01.06 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:01.46 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:01.74 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:02.03 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:02.32 spid89 Starting up database 'MSCRM'.
2004-07-02 09:32:19.81 spid89 Starting up database 'MSCRM'.
2004-07-02 09:45:00.48 spid72 Starting up database 'MSCRM'.
2004-07-02 09:45:01.06 spid72 Starting up database 'MSCRM'.
2004-07-02 10:00:00.23 spid91 Starting up database 'MSCRM'.
2004-07-02 10:00:00.65 spid91 Starting up database 'MSCRM'.
2004-07-02 10:00:00.89 spid101 Starting up database 'MSCRM'.
2004-07-02 10:00:01.60 spid101 Starting up database 'MSCRM'.
2004-07-02 10:00:06.99 spid91 Starting up database 'MSCRM'.Turn off autoclose for the database. What probably happened is that you have autoclose, some other
process (like anti-virus) got hold of the file while SQL Server didn't have it opened, SQL server
tried to access the file, ouch!, suspect database. Next restart, file weren't open by other process,
SQL Server turned off the autoclose option.
Autoclose is not designed for production databases!
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jonathan Wareham" <JonathanW@.CooperParry.com> wrote in message
news:OHdeeaBYEHA.644@.tk2msftngp13.phx.gbl...
> Hi,
> Our network monitoring software reported the following message :
> The database "MSCRM" in the instance "MSSQLSERVER" is in a critical state.
> The state is: Suspect
> After looking at SQL Enterprise Manager, the database appears to be fine and
> I can browse tables, views, stored procedures and query the database as
> normal. However when I looked at the SQL Server Error Log I found many
> messages reporting 'Starting up database 'MSCRM'.
> Any ideas?
> Jonathan
> Here is a sample log from this morning :
>
> 2004-07-02 09:29:53.76 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:54.48 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:59.17 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:59.43 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:59.67 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:59.93 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:00.24 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:00.48 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:00.82 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:01.06 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:01.46 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:01.74 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:02.03 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:02.32 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:32:19.81 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:45:00.48 spid72 Starting up database 'MSCRM'.
> 2004-07-02 09:45:01.06 spid72 Starting up database 'MSCRM'.
> 2004-07-02 10:00:00.23 spid91 Starting up database 'MSCRM'.
> 2004-07-02 10:00:00.65 spid91 Starting up database 'MSCRM'.
> 2004-07-02 10:00:00.89 spid101 Starting up database 'MSCRM'.
> 2004-07-02 10:00:01.60 spid101 Starting up database 'MSCRM'.
> 2004-07-02 10:00:06.99 spid91 Starting up database 'MSCRM'.
>|||Many thanks Tibor!
Jonathan
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23U0H0dBYEHA.3156@.TK2MSFTNGP12.phx.gbl...
> Turn off autoclose for the database. What probably happened is that you
have autoclose, some other
> process (like anti-virus) got hold of the file while SQL Server didn't
have it opened, SQL server
> tried to access the file, ouch!, suspect database. Next restart, file
weren't open by other process,
> SQL Server turned off the autoclose option.
> Autoclose is not designed for production databases!
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Jonathan Wareham" <JonathanW@.CooperParry.com> wrote in message
> news:OHdeeaBYEHA.644@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > Our network monitoring software reported the following message :
> >
> > The database "MSCRM" in the instance "MSSQLSERVER" is in a critical
state.
> > The state is: Suspect
> >
> > After looking at SQL Enterprise Manager, the database appears to be fine
and
> > I can browse tables, views, stored procedures and query the database as
> > normal. However when I looked at the SQL Server Error Log I found many
> > messages reporting 'Starting up database 'MSCRM'.
> >
> > Any ideas?
> >
> > Jonathan
> >
> > Here is a sample log from this morning :
> >
> >
> > 2004-07-02 09:29:53.76 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:54.48 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:59.17 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:59.43 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:59.67 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:59.93 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:00.24 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:00.48 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:00.82 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:01.06 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:01.46 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:01.74 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:02.03 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:02.32 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:32:19.81 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:45:00.48 spid72 Starting up database 'MSCRM'.
> > 2004-07-02 09:45:01.06 spid72 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:00.23 spid91 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:00.65 spid91 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:00.89 spid101 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:01.60 spid101 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:06.99 spid91 Starting up database 'MSCRM'.
> >
> >
>|||I just noticed a typo in my last post. I wrote:
" Next restart, file weren't open by other process, SQL Server turned off the autoclose option."
Should have been:
"...SQL Server turned off the suspect status."
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jonathan Wareham" <JonathanW@.CooperParry.com> wrote in message
news:%23R%23QHwBYEHA.2016@.TK2MSFTNGP11.phx.gbl...
> Many thanks Tibor!
> Jonathan
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23U0H0dBYEHA.3156@.TK2MSFTNGP12.phx.gbl...
> > Turn off autoclose for the database. What probably happened is that you
> have autoclose, some other
> > process (like anti-virus) got hold of the file while SQL Server didn't
> have it opened, SQL server
> > tried to access the file, ouch!, suspect database. Next restart, file
> weren't open by other process,
> > SQL Server turned off the autoclose option.
> >
> > Autoclose is not designed for production databases!
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Jonathan Wareham" <JonathanW@.CooperParry.com> wrote in message
> > news:OHdeeaBYEHA.644@.tk2msftngp13.phx.gbl...
> > > Hi,
> > >
> > > Our network monitoring software reported the following message :
> > >
> > > The database "MSCRM" in the instance "MSSQLSERVER" is in a critical
> state.
> > > The state is: Suspect
> > >
> > > After looking at SQL Enterprise Manager, the database appears to be fine
> and
> > > I can browse tables, views, stored procedures and query the database as
> > > normal. However when I looked at the SQL Server Error Log I found many
> > > messages reporting 'Starting up database 'MSCRM'.
> > >
> > > Any ideas?
> > >
> > > Jonathan
> > >
> > > Here is a sample log from this morning :
> > >
> > >
> > > 2004-07-02 09:29:53.76 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:54.48 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:59.17 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:59.43 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:59.67 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:59.93 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:00.24 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:00.48 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:00.82 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:01.06 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:01.46 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:01.74 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:02.03 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:02.32 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:32:19.81 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:45:00.48 spid72 Starting up database 'MSCRM'.
> > > 2004-07-02 09:45:01.06 spid72 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:00.23 spid91 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:00.65 spid91 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:00.89 spid101 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:01.60 spid101 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:06.99 spid91 Starting up database 'MSCRM'.
> > >
> > >
> >
> >
>

Monday, February 20, 2012

Rendering Reports to Web Application Interactive Features

I installed RS on a Windows 2003 Server: [Unicube] (inside our network, not
available to internet users).
(Windows Authentication now but can be change to Form authentication)
To let outside users to view the report through internet, I create a asp.net
page to render the report: [Product Line Sales]
You can see here:
http://207.14.208.161/UnicareReport/frmImage.aspx
There is a linked report [Employee Sales Summary]: when click the [Employee
Name], ie [Jang, Stephen] in the above report, it should go to the linked
report: [Employee Sales Summary].
The problem is:
(1) How to also render the linked report in asp.net pages to allow internet
users click the [Employee Name] in the above report to go to the linked
report?
(2) The real problem is: How to pass the parameter value in the report
[Product Line Sales] (ie, enp id=20, etc) in the asp.net page to go to the
linked report [Employee Sales Summary].
(it's easy to do in the report designer in VS 2003: jump to URL or Report:
but the linked report in the report server [Unicube] is not availablre to
internet users).I found the solution:
http://207.14.208.161/UnicareReport/frmImage.aspx
You can click the Employee Name such as [Caro, Fernando],[Ito, Shu] to view
the linked report.
My solution is:
(1) First render the first report [Product Line Sales] on the web use render
method:
(You can see the code on RS BOOK ONLINE: ReportingService.Render Method
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_ref_soapapi_service_lz_6x0z.asp )
For my example, the report rendered on The ASP.Net page frmImage.aspx
(2) Change the [jumpe to report] to [Jump to URL] in report [Product Line
Sales]
then deploy the report on Report Server:
For my example, the [jump to URL] Code is:
="http://207.14.208.161/UnicareReport/ESS.aspx?EmpID="&Fields!EmployeeID.Value
&""
(You need to change it to your web site domain/directory setting)
(3)Render the linked report [Product Line Sales] on the web use render
method
You have to render the 2 linked report [Employee Sales Summary] on webpage:
My ASP.net page is ESS.aspx:
Note:
To pass the parameter you can use request.querystring method, for example,
' Prepare report parameter.
Dim parameters(2) As ParameterValue
Dim EMPIDV As String
EMPIDV = Request.QueryString("EmpID")
parameters(0) = New ParameterValue
parameters(0).Name = "EmpID"
parameters(0).Value = EMPIDV
parameters(1) = New ParameterValue
parameters(1).Name = "ReportMonth"
parameters(1).Value = "6" ' June
parameters(2) = New ParameterValue
parameters(2).Name = "ReportYear"
parameters(2).Value = "2004"
"John Chen" <jchen@.uneriercarecorp.com> wrote in message
news:ewjry75tEHA.2072@.tk2msftngp13.phx.gbl...
>I installed RS on a Windows 2003 Server: [Unicube] (inside our network, not
>available to internet users).
> (Windows Authentication now but can be change to Form authentication)
> To let outside users to view the report through internet, I create a
> asp.net page to render the report: [Product Line Sales]
> You can see here:
> http://207.14.208.161/UnicareReport/frmImage.aspx
> There is a linked report [Employee Sales Summary]: when click the
> [Employee Name], ie [Jang, Stephen] in the above report, it should go to
> the linked report: [Employee Sales Summary].
> The problem is:
> (1) How to also render the linked report in asp.net pages to allow
> internet users click the [Employee Name] in the above report to go to the
> linked report?
> (2) The real problem is: How to pass the parameter value in the report
> [Product Line Sales] (ie, enp id=20, etc) in the asp.net page to go to the
> linked report [Employee Sales Summary].
> (it's easy to do in the report designer in VS 2003: jump to URL or Report:
> but the linked report in the report server [Unicube] is not availablre to
> internet users).
>
>|||Correct:
(3)Render the linked report [Employee Sales Summary] on another webpage:
My ASP.net page is ESS.aspx:
Note:
To pass the parameter you can use request.querystring method, for example,
' Prepare report parameter.
Dim parameters(2) As ParameterValue
Dim EMPIDV As String
EMPIDV = Request.QueryString("EmpID")
parameters(0) = New ParameterValue
parameters(0).Name = "EmpID"
parameters(0).Value = EMPIDV
parameters(1) = New ParameterValue
parameters(1).Name = "ReportMonth"
parameters(1).Value = "6" ' June
parameters(2) = New ParameterValue
parameters(2).Name = "ReportYear"
parameters(2).Value = "2004"
"John Chen" <jchen@.uneriercarecorp.com> wrote in message
news:eJWU8JEuEHA.348@.tk2msftngp13.phx.gbl...
>I found the solution:
> http://207.14.208.161/UnicareReport/frmImage.aspx
> You can click the Employee Name such as [Caro, Fernando],[Ito, Shu] to
> view the linked report.
> My solution is:
> (1) First render the first report [Product Line Sales] on the web use
> render method:
> (You can see the code on RS BOOK ONLINE: ReportingService.Render Method
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_ref_soapapi_service_lz_6x0z.asp )
> For my example, the report rendered on The ASP.Net page frmImage.aspx
> (2) Change the [jumpe to report] to [Jump to URL] in report [Product Line
> Sales]
> then deploy the report on Report Server:
> For my example, the [jump to URL] Code is:
> ="http://207.14.208.161/UnicareReport/ESS.aspx?EmpID="&Fields!EmployeeID.Value
> &""
> (You need to change it to your web site domain/directory setting)
> (3)Render the linked report [Product Line Sales] on the web use render
> method
> You have to render the 2 linked report [Employee Sales Summary] on
> webpage:
> My ASP.net page is ESS.aspx:
> Note:
> To pass the parameter you can use request.querystring method, for example,
> ' Prepare report parameter.
> Dim parameters(2) As ParameterValue
> Dim EMPIDV As String
> EMPIDV = Request.QueryString("EmpID")
> parameters(0) = New ParameterValue
> parameters(0).Name = "EmpID"
> parameters(0).Value = EMPIDV
> parameters(1) = New ParameterValue
> parameters(1).Name = "ReportMonth"
> parameters(1).Value = "6" ' June
> parameters(2) = New ParameterValue
> parameters(2).Name = "ReportYear"
> parameters(2).Value = "2004"
>
> "John Chen" <jchen@.uneriercarecorp.com> wrote in message
> news:ewjry75tEHA.2072@.tk2msftngp13.phx.gbl...
>>I installed RS on a Windows 2003 Server: [Unicube] (inside our network,
>>not available to internet users).
>> (Windows Authentication now but can be change to Form authentication)
>> To let outside users to view the report through internet, I create a
>> asp.net page to render the report: [Product Line Sales]
>> You can see here:
>> http://207.14.208.161/UnicareReport/frmImage.aspx
>> There is a linked report [Employee Sales Summary]: when click the
>> [Employee Name], ie [Jang, Stephen] in the above report, it should go to
>> the linked report: [Employee Sales Summary].
>> The problem is:
>> (1) How to also render the linked report in asp.net pages to allow
>> internet users click the [Employee Name] in the above report to go to the
>> linked report?
>> (2) The real problem is: How to pass the parameter value in the report
>> [Product Line Sales] (ie, enp id=20, etc) in the asp.net page to go to
>> the linked report [Employee Sales Summary].
>> (it's easy to do in the report designer in VS 2003: jump to URL or
>> Report: but the linked report in the report server [Unicube] is not
>> availablre to internet users).
>>
>>
>

Friday, March 23, 2012

Replace SQL server in multiple server network

Monday, March 12, 2012

Repeated 'Starting up database' messages

Repeated 'Starting up database' messages

Repeated 'Starting up database' messages

Monday, February 20, 2012

Rendering Reports to Web Application Interactive Features

Rendering report

Blog Archive

About Me