Hello,
I am running an active-active cluster on SQL 2000 SP3a over a Windows 2003
Enterprise server. We have two production instances running (SQL1 and SQL2).
Each was setup on a different node originally. When the two instances are
running on the same node, the instance that was not setup on that node
experiences locked files and failed backups.
Here is an example:
SQL1 was setup on Node1 and SQL2 was setup on Node2. When SQL1 and SQL2 are
both running on Node1, our backup job fails because it sees that a couple of
the database backup files are locked. Even after I clear the locks and re-ru
n
the backup script, the job still fails for the same reason. Now when I run
the same job when SQL2 is back on Node2, the job completes successfully. Not
all of the database backups fail, just the ones that are over 2Gb.
Has anyone experienced this or heard about this before? I've checked posting
s
here as well as TechNet, but haven't found anything.
Thanks for your assistance.
Michael
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1> both running on Node1, our backup job fails
By 'our backup job', I assume you meant the SQL Server database backup job.
The problem should not have anything to do with how the two instances were
originally set up. Nor should it necessarily have anything to do with the
fact that the two instances were running on the same node. It was a
coincident that it did happen when the two instances were running on the sam
e
node.
To resolve the problem, you need to first determine what process(es) or
programs are locking the backup files. My hunch is that they are most likely
locked either by an anti-virus program or a network file backup job. In othe
r
words, the anti-virus or the network file backup job happened to collide wit
h
the database backup on this particular node.
One way to be sure about what is locking the backup file is to add another
step immediately before the SQL Server backup to dump out all the NT handles
or just the handles on the backup file. You can use the sysinternals tool
handle.exe for this purpose.
Linchi
"michaelg via droptable.com" wrote:
> Hello,
> I am running an active-active cluster on SQL 2000 SP3a over a Windows 2003
> Enterprise server. We have two production instances running (SQL1 and SQL2
).
> Each was setup on a different node originally. When the two instances are
> running on the same node, the instance that was not setup on that node
> experiences locked files and failed backups.
> Here is an example:
> SQL1 was setup on Node1 and SQL2 was setup on Node2. When SQL1 and SQL2 ar
e
> both running on Node1, our backup job fails because it sees that a couple
of
> the database backup files are locked. Even after I clear the locks and re-
run
> the backup script, the job still fails for the same reason. Now when I run
> the same job when SQL2 is back on Node2, the job completes successfully. N
ot
> all of the database backups fail, just the ones that are over 2Gb.
> Has anyone experienced this or heard about this before? I've checked posti
ngs
> here as well as TechNet, but haven't found anything.
> Thanks for your assistance.
> Michael
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200609/1
>|||Yes, I meant the SQL Server database backup jobs.
This is not a one-time event. No matter what time I run the database backup
job on Node1, the job fails. This makes me think that it is not a tape backu
p
or any scheduled event. When I moved back to Node2 this morning, the job ran
fine multiple times.
I am not familiar with the handle.exe. Is this a 3rd party tool or is it
included in Microsoft?
Thanks!
Linchi Shea wrote:[vbcol=seagreen]
>By 'our backup job', I assume you meant the SQL Server database backup job.
>The problem should not have anything to do with how the two instances were
>originally set up. Nor should it necessarily have anything to do with the
>fact that the two instances were running on the same node. It was a
>coincident that it did happen when the two instances were running on the sa
me
>node.
>To resolve the problem, you need to first determine what process(es) or
>programs are locking the backup files. My hunch is that they are most likel
y
>locked either by an anti-virus program or a network file backup job. In oth
er
>words, the anti-virus or the network file backup job happened to collide wi
th
>the database backup on this particular node.
>One way to be sure about what is locking the backup file is to add another
>step immediately before the SQL Server backup to dump out all the NT handle
s
>or just the handles on the backup file. You can use the sysinternals tool
>handle.exe for this purpose.
>Linchi
>
>[quoted text clipped - 18 lines]
Message posted via http://www.droptable.com|||This is a sysinternals tool available from www.sysinternals.com.
Linchi
"michaelg via droptable.com" wrote:
> Yes, I meant the SQL Server database backup jobs.
> This is not a one-time event. No matter what time I run the database backu
p
> job on Node1, the job fails. This makes me think that it is not a tape bac
kup
> or any scheduled event. When I moved back to Node2 this morning, the job r
an
> fine multiple times.
> I am not familiar with the handle.exe. Is this a 3rd party tool or is it
> included in Microsoft?
> Thanks!
> Linchi Shea wrote:
> --
> Message posted via http://www.droptable.com
>
Showing posts with label files. Show all posts
Showing posts with label files. Show all posts
Friday, March 30, 2012
Locked files during backups on a cluster
Hello,
I am running an active-active cluster on SQL 2000 SP3a over a Windows 2003
Enterprise server. We have two production instances running (SQL1 and SQL2).
Each was setup on a different node originally. When the two instances are
running on the same node, the instance that was not setup on that node
experiences locked files and failed backups.
Here is an example:
SQL1 was setup on Node1 and SQL2 was setup on Node2. When SQL1 and SQL2 are
both running on Node1, our backup job fails because it sees that a couple of
the database backup files are locked. Even after I clear the locks and re-run
the backup script, the job still fails for the same reason. Now when I run
the same job when SQL2 is back on Node2, the job completes successfully. Not
all of the database backups fail, just the ones that are over 2Gb.
Has anyone experienced this or heard about this before? I've checked postings
here as well as TechNet, but haven't found anything.
Thanks for your assistance.
Michael
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200609/1> both running on Node1, our backup job fails
By 'our backup job', I assume you meant the SQL Server database backup job.
The problem should not have anything to do with how the two instances were
originally set up. Nor should it necessarily have anything to do with the
fact that the two instances were running on the same node. It was a
coincident that it did happen when the two instances were running on the same
node.
To resolve the problem, you need to first determine what process(es) or
programs are locking the backup files. My hunch is that they are most likely
locked either by an anti-virus program or a network file backup job. In other
words, the anti-virus or the network file backup job happened to collide with
the database backup on this particular node.
One way to be sure about what is locking the backup file is to add another
step immediately before the SQL Server backup to dump out all the NT handles
or just the handles on the backup file. You can use the sysinternals tool
handle.exe for this purpose.
Linchi
"michaelg via SQLMonster.com" wrote:
> Hello,
> I am running an active-active cluster on SQL 2000 SP3a over a Windows 2003
> Enterprise server. We have two production instances running (SQL1 and SQL2).
> Each was setup on a different node originally. When the two instances are
> running on the same node, the instance that was not setup on that node
> experiences locked files and failed backups.
> Here is an example:
> SQL1 was setup on Node1 and SQL2 was setup on Node2. When SQL1 and SQL2 are
> both running on Node1, our backup job fails because it sees that a couple of
> the database backup files are locked. Even after I clear the locks and re-run
> the backup script, the job still fails for the same reason. Now when I run
> the same job when SQL2 is back on Node2, the job completes successfully. Not
> all of the database backups fail, just the ones that are over 2Gb.
> Has anyone experienced this or heard about this before? I've checked postings
> here as well as TechNet, but haven't found anything.
> Thanks for your assistance.
> Michael
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200609/1
>|||Yes, I meant the SQL Server database backup jobs.
This is not a one-time event. No matter what time I run the database backup
job on Node1, the job fails. This makes me think that it is not a tape backup
or any scheduled event. When I moved back to Node2 this morning, the job ran
fine multiple times.
I am not familiar with the handle.exe. Is this a 3rd party tool or is it
included in Microsoft?
Thanks!
Linchi Shea wrote:
>> both running on Node1, our backup job fails
>By 'our backup job', I assume you meant the SQL Server database backup job.
>The problem should not have anything to do with how the two instances were
>originally set up. Nor should it necessarily have anything to do with the
>fact that the two instances were running on the same node. It was a
>coincident that it did happen when the two instances were running on the same
>node.
>To resolve the problem, you need to first determine what process(es) or
>programs are locking the backup files. My hunch is that they are most likely
>locked either by an anti-virus program or a network file backup job. In other
>words, the anti-virus or the network file backup job happened to collide with
>the database backup on this particular node.
>One way to be sure about what is locking the backup file is to add another
>step immediately before the SQL Server backup to dump out all the NT handles
>or just the handles on the backup file. You can use the sysinternals tool
>handle.exe for this purpose.
>Linchi
>> Hello,
>[quoted text clipped - 18 lines]
>> Thanks for your assistance.
>> Michael
--
Message posted via http://www.sqlmonster.com|||This is a sysinternals tool available from www.sysinternals.com.
Linchi
"michaelg via SQLMonster.com" wrote:
> Yes, I meant the SQL Server database backup jobs.
> This is not a one-time event. No matter what time I run the database backup
> job on Node1, the job fails. This makes me think that it is not a tape backup
> or any scheduled event. When I moved back to Node2 this morning, the job ran
> fine multiple times.
> I am not familiar with the handle.exe. Is this a 3rd party tool or is it
> included in Microsoft?
> Thanks!
> Linchi Shea wrote:
> >> both running on Node1, our backup job fails
> >
> >By 'our backup job', I assume you meant the SQL Server database backup job.
> >
> >The problem should not have anything to do with how the two instances were
> >originally set up. Nor should it necessarily have anything to do with the
> >fact that the two instances were running on the same node. It was a
> >coincident that it did happen when the two instances were running on the same
> >node.
> >
> >To resolve the problem, you need to first determine what process(es) or
> >programs are locking the backup files. My hunch is that they are most likely
> >locked either by an anti-virus program or a network file backup job. In other
> >words, the anti-virus or the network file backup job happened to collide with
> >the database backup on this particular node.
> >
> >One way to be sure about what is locking the backup file is to add another
> >step immediately before the SQL Server backup to dump out all the NT handles
> >or just the handles on the backup file. You can use the sysinternals tool
> >handle.exe for this purpose.
> >
> >Linchi
> >
> >> Hello,
> >>
> >[quoted text clipped - 18 lines]
> >> Thanks for your assistance.
> >> Michael
> --
> Message posted via http://www.sqlmonster.com
>
I am running an active-active cluster on SQL 2000 SP3a over a Windows 2003
Enterprise server. We have two production instances running (SQL1 and SQL2).
Each was setup on a different node originally. When the two instances are
running on the same node, the instance that was not setup on that node
experiences locked files and failed backups.
Here is an example:
SQL1 was setup on Node1 and SQL2 was setup on Node2. When SQL1 and SQL2 are
both running on Node1, our backup job fails because it sees that a couple of
the database backup files are locked. Even after I clear the locks and re-run
the backup script, the job still fails for the same reason. Now when I run
the same job when SQL2 is back on Node2, the job completes successfully. Not
all of the database backups fail, just the ones that are over 2Gb.
Has anyone experienced this or heard about this before? I've checked postings
here as well as TechNet, but haven't found anything.
Thanks for your assistance.
Michael
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200609/1> both running on Node1, our backup job fails
By 'our backup job', I assume you meant the SQL Server database backup job.
The problem should not have anything to do with how the two instances were
originally set up. Nor should it necessarily have anything to do with the
fact that the two instances were running on the same node. It was a
coincident that it did happen when the two instances were running on the same
node.
To resolve the problem, you need to first determine what process(es) or
programs are locking the backup files. My hunch is that they are most likely
locked either by an anti-virus program or a network file backup job. In other
words, the anti-virus or the network file backup job happened to collide with
the database backup on this particular node.
One way to be sure about what is locking the backup file is to add another
step immediately before the SQL Server backup to dump out all the NT handles
or just the handles on the backup file. You can use the sysinternals tool
handle.exe for this purpose.
Linchi
"michaelg via SQLMonster.com" wrote:
> Hello,
> I am running an active-active cluster on SQL 2000 SP3a over a Windows 2003
> Enterprise server. We have two production instances running (SQL1 and SQL2).
> Each was setup on a different node originally. When the two instances are
> running on the same node, the instance that was not setup on that node
> experiences locked files and failed backups.
> Here is an example:
> SQL1 was setup on Node1 and SQL2 was setup on Node2. When SQL1 and SQL2 are
> both running on Node1, our backup job fails because it sees that a couple of
> the database backup files are locked. Even after I clear the locks and re-run
> the backup script, the job still fails for the same reason. Now when I run
> the same job when SQL2 is back on Node2, the job completes successfully. Not
> all of the database backups fail, just the ones that are over 2Gb.
> Has anyone experienced this or heard about this before? I've checked postings
> here as well as TechNet, but haven't found anything.
> Thanks for your assistance.
> Michael
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200609/1
>|||Yes, I meant the SQL Server database backup jobs.
This is not a one-time event. No matter what time I run the database backup
job on Node1, the job fails. This makes me think that it is not a tape backup
or any scheduled event. When I moved back to Node2 this morning, the job ran
fine multiple times.
I am not familiar with the handle.exe. Is this a 3rd party tool or is it
included in Microsoft?
Thanks!
Linchi Shea wrote:
>> both running on Node1, our backup job fails
>By 'our backup job', I assume you meant the SQL Server database backup job.
>The problem should not have anything to do with how the two instances were
>originally set up. Nor should it necessarily have anything to do with the
>fact that the two instances were running on the same node. It was a
>coincident that it did happen when the two instances were running on the same
>node.
>To resolve the problem, you need to first determine what process(es) or
>programs are locking the backup files. My hunch is that they are most likely
>locked either by an anti-virus program or a network file backup job. In other
>words, the anti-virus or the network file backup job happened to collide with
>the database backup on this particular node.
>One way to be sure about what is locking the backup file is to add another
>step immediately before the SQL Server backup to dump out all the NT handles
>or just the handles on the backup file. You can use the sysinternals tool
>handle.exe for this purpose.
>Linchi
>> Hello,
>[quoted text clipped - 18 lines]
>> Thanks for your assistance.
>> Michael
--
Message posted via http://www.sqlmonster.com|||This is a sysinternals tool available from www.sysinternals.com.
Linchi
"michaelg via SQLMonster.com" wrote:
> Yes, I meant the SQL Server database backup jobs.
> This is not a one-time event. No matter what time I run the database backup
> job on Node1, the job fails. This makes me think that it is not a tape backup
> or any scheduled event. When I moved back to Node2 this morning, the job ran
> fine multiple times.
> I am not familiar with the handle.exe. Is this a 3rd party tool or is it
> included in Microsoft?
> Thanks!
> Linchi Shea wrote:
> >> both running on Node1, our backup job fails
> >
> >By 'our backup job', I assume you meant the SQL Server database backup job.
> >
> >The problem should not have anything to do with how the two instances were
> >originally set up. Nor should it necessarily have anything to do with the
> >fact that the two instances were running on the same node. It was a
> >coincident that it did happen when the two instances were running on the same
> >node.
> >
> >To resolve the problem, you need to first determine what process(es) or
> >programs are locking the backup files. My hunch is that they are most likely
> >locked either by an anti-virus program or a network file backup job. In other
> >words, the anti-virus or the network file backup job happened to collide with
> >the database backup on this particular node.
> >
> >One way to be sure about what is locking the backup file is to add another
> >step immediately before the SQL Server backup to dump out all the NT handles
> >or just the handles on the backup file. You can use the sysinternals tool
> >handle.exe for this purpose.
> >
> >Linchi
> >
> >> Hello,
> >>
> >[quoted text clipped - 18 lines]
> >> Thanks for your assistance.
> >> Michael
> --
> Message posted via http://www.sqlmonster.com
>
Monday, March 26, 2012
lock pdf export
Hi
i just create a report in c#. The user can export this report in .pdf format. Now i want to lock the content of this .pdf files. How can i do this in crystal report 10?
Thank'sSet the EnableExportButton to False
Add a command button to the Viewer and customize the allowed export options...
But remember, that the user could have a PDFPrinter
i just create a report in c#. The user can export this report in .pdf format. Now i want to lock the content of this .pdf files. How can i do this in crystal report 10?
Thank'sSet the EnableExportButton to False
Add a command button to the Viewer and customize the allowed export options...
But remember, that the user could have a PDFPrinter
Wednesday, March 21, 2012
Location of Report Files on Server
Does anyone know which directory contains the report (.rdl) files on the SQL
Server Reporting Services server? I'd like to access these files on the
server.
Thank you.There are no rdl files on the server. The process of deploying causes the
rdl to be stored in the database. If you need to retrieve the rdl that was
deployed you can do to report manager, click on the report, properties, edit
and give it a file name to put the rdl into.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Brian P" <BrianP@.discussions.microsoft.com> wrote in message
news:606DD94C-C004-4E30-BD72-DDBB0056C908@.microsoft.com...
> Does anyone know which directory contains the report (.rdl) files on the
> SQL
> Server Reporting Services server? I'd like to access these files on the
> server.
> Thank you.|||Bruce,
Understood. Thanks for the reply.
Brian
"Bruce L-C [MVP]" wrote:
> There are no rdl files on the server. The process of deploying causes the
> rdl to be stored in the database. If you need to retrieve the rdl that was
> deployed you can do to report manager, click on the report, properties, edit
> and give it a file name to put the rdl into.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Brian P" <BrianP@.discussions.microsoft.com> wrote in message
> news:606DD94C-C004-4E30-BD72-DDBB0056C908@.microsoft.com...
> > Does anyone know which directory contains the report (.rdl) files on the
> > SQL
> > Server Reporting Services server? I'd like to access these files on the
> > server.
> >
> > Thank you.
>
>
Server Reporting Services server? I'd like to access these files on the
server.
Thank you.There are no rdl files on the server. The process of deploying causes the
rdl to be stored in the database. If you need to retrieve the rdl that was
deployed you can do to report manager, click on the report, properties, edit
and give it a file name to put the rdl into.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Brian P" <BrianP@.discussions.microsoft.com> wrote in message
news:606DD94C-C004-4E30-BD72-DDBB0056C908@.microsoft.com...
> Does anyone know which directory contains the report (.rdl) files on the
> SQL
> Server Reporting Services server? I'd like to access these files on the
> server.
> Thank you.|||Bruce,
Understood. Thanks for the reply.
Brian
"Bruce L-C [MVP]" wrote:
> There are no rdl files on the server. The process of deploying causes the
> rdl to be stored in the database. If you need to retrieve the rdl that was
> deployed you can do to report manager, click on the report, properties, edit
> and give it a file name to put the rdl into.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Brian P" <BrianP@.discussions.microsoft.com> wrote in message
> news:606DD94C-C004-4E30-BD72-DDBB0056C908@.microsoft.com...
> > Does anyone know which directory contains the report (.rdl) files on the
> > SQL
> > Server Reporting Services server? I'd like to access these files on the
> > server.
> >
> > Thank you.
>
>
Location of RDL files?
I'm unable to deploy using Visual Studio and would like to upload my files
manually. I've searched the web server for the existing files and can't find
them. I also searched books online. Any ideas?
ThanksNo rdl files exist on the server. They are all stored in the database.
Deploying a report is more than the report being copied over. To deploy from
outside of VS requires using scripting. Search Books Online for the work
scripting and then open up the samples link.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Leslie" <Leslie@.discussions.microsoft.com> wrote in message
news:58086A07-F1DD-40BE-B0D5-80D3F34891A8@.microsoft.com...
> I'm unable to deploy using Visual Studio and would like to upload my files
> manually. I've searched the web server for the existing files and can't
> find
> them. I also searched books online. Any ideas?
> Thanks|||Thanks for the response. I ftp'd the files over to my server and then
uploaded them using the Report Manager. A little easier than using scripting.
"Bruce L-C [MVP]" wrote:
> No rdl files exist on the server. They are all stored in the database.
> Deploying a report is more than the report being copied over. To deploy from
> outside of VS requires using scripting. Search Books Online for the work
> scripting and then open up the samples link.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Leslie" <Leslie@.discussions.microsoft.com> wrote in message
> news:58086A07-F1DD-40BE-B0D5-80D3F34891A8@.microsoft.com...
> > I'm unable to deploy using Visual Studio and would like to upload my files
> > manually. I've searched the web server for the existing files and can't
> > find
> > them. I also searched books online. Any ideas?
> >
> > Thanks
>
>|||Just an FYI, you can also use the Report Manager to retrieve the rdl if you
ever need to.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Leslie" <Leslie@.discussions.microsoft.com> wrote in message
news:434F327E-9286-47BA-8B6E-6DB079E58461@.microsoft.com...
> Thanks for the response. I ftp'd the files over to my server and then
> uploaded them using the Report Manager. A little easier than using
> scripting.
> "Bruce L-C [MVP]" wrote:
>> No rdl files exist on the server. They are all stored in the database.
>> Deploying a report is more than the report being copied over. To deploy
>> from
>> outside of VS requires using scripting. Search Books Online for the work
>> scripting and then open up the samples link.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Leslie" <Leslie@.discussions.microsoft.com> wrote in message
>> news:58086A07-F1DD-40BE-B0D5-80D3F34891A8@.microsoft.com...
>> > I'm unable to deploy using Visual Studio and would like to upload my
>> > files
>> > manually. I've searched the web server for the existing files and can't
>> > find
>> > them. I also searched books online. Any ideas?
>> >
>> > Thanks
>>
manually. I've searched the web server for the existing files and can't find
them. I also searched books online. Any ideas?
ThanksNo rdl files exist on the server. They are all stored in the database.
Deploying a report is more than the report being copied over. To deploy from
outside of VS requires using scripting. Search Books Online for the work
scripting and then open up the samples link.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Leslie" <Leslie@.discussions.microsoft.com> wrote in message
news:58086A07-F1DD-40BE-B0D5-80D3F34891A8@.microsoft.com...
> I'm unable to deploy using Visual Studio and would like to upload my files
> manually. I've searched the web server for the existing files and can't
> find
> them. I also searched books online. Any ideas?
> Thanks|||Thanks for the response. I ftp'd the files over to my server and then
uploaded them using the Report Manager. A little easier than using scripting.
"Bruce L-C [MVP]" wrote:
> No rdl files exist on the server. They are all stored in the database.
> Deploying a report is more than the report being copied over. To deploy from
> outside of VS requires using scripting. Search Books Online for the work
> scripting and then open up the samples link.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Leslie" <Leslie@.discussions.microsoft.com> wrote in message
> news:58086A07-F1DD-40BE-B0D5-80D3F34891A8@.microsoft.com...
> > I'm unable to deploy using Visual Studio and would like to upload my files
> > manually. I've searched the web server for the existing files and can't
> > find
> > them. I also searched books online. Any ideas?
> >
> > Thanks
>
>|||Just an FYI, you can also use the Report Manager to retrieve the rdl if you
ever need to.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Leslie" <Leslie@.discussions.microsoft.com> wrote in message
news:434F327E-9286-47BA-8B6E-6DB079E58461@.microsoft.com...
> Thanks for the response. I ftp'd the files over to my server and then
> uploaded them using the Report Manager. A little easier than using
> scripting.
> "Bruce L-C [MVP]" wrote:
>> No rdl files exist on the server. They are all stored in the database.
>> Deploying a report is more than the report being copied over. To deploy
>> from
>> outside of VS requires using scripting. Search Books Online for the work
>> scripting and then open up the samples link.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Leslie" <Leslie@.discussions.microsoft.com> wrote in message
>> news:58086A07-F1DD-40BE-B0D5-80D3F34891A8@.microsoft.com...
>> > I'm unable to deploy using Visual Studio and would like to upload my
>> > files
>> > manually. I've searched the web server for the existing files and can't
>> > find
>> > them. I also searched books online. Any ideas?
>> >
>> > Thanks
>>
location of rdl files on server
Hi there ,
I am working on SSRS and I just wanted to know where
are the .rdl file stored on the server.I came along this problem as i
was searching a way to make the report content dynamic rather make the
report content customizable .I just wanted to know is there a way to
change rdl files to make them customizable.
thanks.AFAIK, the files are not stored anywhere. When you upload a report, the definition (contents of the
RDL file) is inserted into one or more tables in the report database. I'm not RS expert, though, so
you might want to verify this in an RS forum.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"unixbf" <bondfranco@.gmail.com> wrote in message
news:d2323315-9f7f-44a1-9d32-49795ad3efc2@.v46g2000hsv.googlegroups.com...
> Hi there ,
> I am working on SSRS and I just wanted to know where
> are the .rdl file stored on the server.I came along this problem as i
> was searching a way to make the report content dynamic rather make the
> report content customizable .I just wanted to know is there a way to
> change rdl files to make them customizable.
> thanks.|||Tibor Karaszi wrote:
> AFAIK, the files are not stored anywhere. When you upload a report, the definition (contents of the
> RDL file) is inserted into one or more tables in the report database. I'm not RS expert, though, so
> you might want to verify this in an RS forum.
>
true!
I am working on SSRS and I just wanted to know where
are the .rdl file stored on the server.I came along this problem as i
was searching a way to make the report content dynamic rather make the
report content customizable .I just wanted to know is there a way to
change rdl files to make them customizable.
thanks.AFAIK, the files are not stored anywhere. When you upload a report, the definition (contents of the
RDL file) is inserted into one or more tables in the report database. I'm not RS expert, though, so
you might want to verify this in an RS forum.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"unixbf" <bondfranco@.gmail.com> wrote in message
news:d2323315-9f7f-44a1-9d32-49795ad3efc2@.v46g2000hsv.googlegroups.com...
> Hi there ,
> I am working on SSRS and I just wanted to know where
> are the .rdl file stored on the server.I came along this problem as i
> was searching a way to make the report content dynamic rather make the
> report content customizable .I just wanted to know is there a way to
> change rdl files to make them customizable.
> thanks.|||Tibor Karaszi wrote:
> AFAIK, the files are not stored anywhere. When you upload a report, the definition (contents of the
> RDL file) is inserted into one or more tables in the report database. I'm not RS expert, though, so
> you might want to verify this in an RS forum.
>
true!
location of rdl files on report server
Hi there ,
I am working on SSRS and I just wanted to know where
are the .rdl file stored on the server.I came along this problem as i
was searching a way to make the report content dynamic rather make the
report content customizable .I just wanted to know is there a way to
change rdl files to make them customizable.
thanks.RDL files are not stored as files on the server. They are stored in the
database. Essentially you have to redeploy the rdl file which you can do by
using webservices. However, you cannot do this for a specific user.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"unixbf" <bondfranco@.gmail.com> wrote in message
news:448b5c16-8146-48b0-a412-8e38d873955d@.v67g2000hse.googlegroups.com...
> Hi there ,
> I am working on SSRS and I just wanted to know where
> are the .rdl file stored on the server.I came along this problem as i
> was searching a way to make the report content dynamic rather make the
> report content customizable .I just wanted to know is there a way to
> change rdl files to make them customizable.
> thanks.
I am working on SSRS and I just wanted to know where
are the .rdl file stored on the server.I came along this problem as i
was searching a way to make the report content dynamic rather make the
report content customizable .I just wanted to know is there a way to
change rdl files to make them customizable.
thanks.RDL files are not stored as files on the server. They are stored in the
database. Essentially you have to redeploy the rdl file which you can do by
using webservices. However, you cannot do this for a specific user.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"unixbf" <bondfranco@.gmail.com> wrote in message
news:448b5c16-8146-48b0-a412-8e38d873955d@.v67g2000hse.googlegroups.com...
> Hi there ,
> I am working on SSRS and I just wanted to know where
> are the .rdl file stored on the server.I came along this problem as i
> was searching a way to make the report content dynamic rather make the
> report content customizable .I just wanted to know is there a way to
> change rdl files to make them customizable.
> thanks.
Location of Logs and data files
Do the logs and data files of a database have to be on the same server as the
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this?
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this?
>
|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this?
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/default...b;en-us;304261
Regards
Steen
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this?
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this?
>
|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this?
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/default...b;en-us;304261
Regards
Steen
Location of Logs and data files
Do the logs and data files of a database have to be on the same server as th
e
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this'> Do the logs and data files of a database have to be on the same server as theen">
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as
the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However
I
> am expecting a new one to grow quite fast, and would like to place the dat
a
> and log files on a separate server. However, when I create a new DB and tr
y
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as
the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However
I
> am expecting a new one to grow quite fast, and would like to place the dat
a
> and log files on a separate server. However, when I create a new DB and tr
y
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/defaul...kb;en-us;304261
Regards
Steen
e
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this'> Do the logs and data files of a database have to be on the same server as theen">
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as
the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However
I
> am expecting a new one to grow quite fast, and would like to place the dat
a
> and log files on a separate server. However, when I create a new DB and tr
y
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as
the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However
I
> am expecting a new one to grow quite fast, and would like to place the dat
a
> and log files on a separate server. However, when I create a new DB and tr
y
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/defaul...kb;en-us;304261
Regards
Steen
Location of Logs and data files
Do the logs and data files of a database have to be on the same server as the
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this'> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
Regards
Steen
SQL Server software?
I am running SQL Server 2000, and have several DBs on the server. However I
am expecting a new one to grow quite fast, and would like to place the data
and log files on a separate server. However, when I create a new DB and try
to locate the data and log files elsewhere, it only appears to allow me to
place them on the same server. Is there any way round this'> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
Yes. They can be on a SAN, though, as a SAN is seen as locally attached..
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Petet Tickler" <Petet Tickler@.discussions.microsoft.com> wrote in message
news:60DF8C3F-8C66-4FB9-9731-569DE8B3F832@.microsoft.com...
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>|||Petet Tickler wrote:
> Do the logs and data files of a database have to be on the same server as the
> SQL Server software?
> I am running SQL Server 2000, and have several DBs on the server. However I
> am expecting a new one to grow quite fast, and would like to place the data
> and log files on a separate server. However, when I create a new DB and try
> to locate the data and log files elsewhere, it only appears to allow me to
> place them on the same server. Is there any way round this'
>
Having you database files on another server, is not enabled in SQL Server.
If you have a NAS, you can have your files on this, but it's not
recommended.
http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
Regards
Steen
Location of error log?
Hopefully this will be a simple question.
Where is the error log located? I am looking in
program files\microsoft sql server\mssql\reporting services\LogFile
at a file called ReportServer__09_27_2005_11_38_23.log inside that file is a
message:
e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., ;
Where can I fine the error log it refers to? Everything has been installed
to default locations.
ThanksYou are looking at the error log. The log contains the text that is
displayed to users so it is a little misleading when seeing it in the log
itself. Can you include the entire call stack?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
news:83BFFE98-BBF5-4CD6-9D71-CAC85D4E3228@.microsoft.com...
> Hopefully this will be a simple question.
> Where is the error log located? I am looking in
> program files\microsoft sql server\mssql\reporting services\LogFile
> at a file called ReportServer__09_27_2005_11_38_23.log inside that file is
> a
> message:
> e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more
> details., ;
> Where can I fine the error log it refers to? Everything has been
> installed
> to default locations.
> Thanks|||Thanks for that. I am getting different errors in the log at different times
from the same problem. The problem in detailed in my post "Login Prompt
after ~3min timeout".
I am reguarly getting out memory errors, but I have looked at the machine
and it is only using ~1/3 of available memory and CPU so I think that is a
red herring.
The report runs fine if the data allows it to complete before 2.5 - 3mins -
this seems to be 2.5mins on the test server I am using and 3mins on the live
environment.
The following messages are the only consistant ones I am seeing in the log:
w3wp!runningjobs!1568!28/09/2005-09:46:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!1568!28/09/2005-09:46:45:: w WARN:
RunningJobContext.Cancel; failed
w3wp!runningjobs!1568!28/09/2005-09:47:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:48:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:49:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:50:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!fe4!28/09/2005-09:51:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:52:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
Any thoughts, pointers or suggestions will be gratefully received.
"Daniel Reib [MSFT]" wrote:
> You are looking at the error log. The log contains the text that is
> displayed to users so it is a little misleading when seeing it in the log
> itself. Can you include the entire call stack?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
> news:83BFFE98-BBF5-4CD6-9D71-CAC85D4E3228@.microsoft.com...
> > Hopefully this will be a simple question.
> >
> > Where is the error log located? I am looking in
> >
> > program files\microsoft sql server\mssql\reporting services\LogFile
> >
> > at a file called ReportServer__09_27_2005_11_38_23.log inside that file is
> > a
> > message:
> >
> > e ERROR: Throwing
> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > An internal error occurred on the report server. See the error log for
> > more
> > details., ;
> >
> > Where can I fine the error log it refers to? Everything has been
> > installed
> > to default locations.
> >
> > Thanks
>
>|||The orphaned requests means that the client is disconnected from the server.
In this case RS will stop processing the job.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
news:E2F9A42E-C173-4B35-8BA3-749239454E90@.microsoft.com...
> Thanks for that. I am getting different errors in the log at different
> times
> from the same problem. The problem in detailed in my post "Login Prompt
> after ~3min timeout".
> I am reguarly getting out memory errors, but I have looked at the machine
> and it is only using ~1/3 of available memory and CPU so I think that is a
> red herring.
> The report runs fine if the data allows it to complete before 2.5 -
> 3mins -
> this seems to be 2.5mins on the test server I am using and 3mins on the
> live
> environment.
> The following messages are the only consistant ones I am seeing in the
> log:
> w3wp!runningjobs!1568!28/09/2005-09:46:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!1568!28/09/2005-09:46:45:: w WARN:
> RunningJobContext.Cancel; failed
> w3wp!runningjobs!1568!28/09/2005-09:47:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:48:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:49:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:50:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!fe4!28/09/2005-09:51:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:52:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> Any thoughts, pointers or suggestions will be gratefully received.
> "Daniel Reib [MSFT]" wrote:
>> You are looking at the error log. The log contains the text that is
>> displayed to users so it is a little misleading when seeing it in the log
>> itself. Can you include the entire call stack?
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
>> news:83BFFE98-BBF5-4CD6-9D71-CAC85D4E3228@.microsoft.com...
>> > Hopefully this will be a simple question.
>> >
>> > Where is the error log located? I am looking in
>> >
>> > program files\microsoft sql server\mssql\reporting services\LogFile
>> >
>> > at a file called ReportServer__09_27_2005_11_38_23.log inside that file
>> > is
>> > a
>> > message:
>> >
>> > e ERROR: Throwing
>> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> > An internal error occurred on the report server. See the error log for
>> > more
>> > details., ;
>> >
>> > Where can I fine the error log it refers to? Everything has been
>> > installed
>> > to default locations.
>> >
>> > Thanks
>>
Where is the error log located? I am looking in
program files\microsoft sql server\mssql\reporting services\LogFile
at a file called ReportServer__09_27_2005_11_38_23.log inside that file is a
message:
e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., ;
Where can I fine the error log it refers to? Everything has been installed
to default locations.
ThanksYou are looking at the error log. The log contains the text that is
displayed to users so it is a little misleading when seeing it in the log
itself. Can you include the entire call stack?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
news:83BFFE98-BBF5-4CD6-9D71-CAC85D4E3228@.microsoft.com...
> Hopefully this will be a simple question.
> Where is the error log located? I am looking in
> program files\microsoft sql server\mssql\reporting services\LogFile
> at a file called ReportServer__09_27_2005_11_38_23.log inside that file is
> a
> message:
> e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more
> details., ;
> Where can I fine the error log it refers to? Everything has been
> installed
> to default locations.
> Thanks|||Thanks for that. I am getting different errors in the log at different times
from the same problem. The problem in detailed in my post "Login Prompt
after ~3min timeout".
I am reguarly getting out memory errors, but I have looked at the machine
and it is only using ~1/3 of available memory and CPU so I think that is a
red herring.
The report runs fine if the data allows it to complete before 2.5 - 3mins -
this seems to be 2.5mins on the test server I am using and 3mins on the live
environment.
The following messages are the only consistant ones I am seeing in the log:
w3wp!runningjobs!1568!28/09/2005-09:46:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!1568!28/09/2005-09:46:45:: w WARN:
RunningJobContext.Cancel; failed
w3wp!runningjobs!1568!28/09/2005-09:47:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:48:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:49:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:50:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!fe4!28/09/2005-09:51:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:52:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
Any thoughts, pointers or suggestions will be gratefully received.
"Daniel Reib [MSFT]" wrote:
> You are looking at the error log. The log contains the text that is
> displayed to users so it is a little misleading when seeing it in the log
> itself. Can you include the entire call stack?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
> news:83BFFE98-BBF5-4CD6-9D71-CAC85D4E3228@.microsoft.com...
> > Hopefully this will be a simple question.
> >
> > Where is the error log located? I am looking in
> >
> > program files\microsoft sql server\mssql\reporting services\LogFile
> >
> > at a file called ReportServer__09_27_2005_11_38_23.log inside that file is
> > a
> > message:
> >
> > e ERROR: Throwing
> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > An internal error occurred on the report server. See the error log for
> > more
> > details., ;
> >
> > Where can I fine the error log it refers to? Everything has been
> > installed
> > to default locations.
> >
> > Thanks
>
>|||The orphaned requests means that the client is disconnected from the server.
In this case RS will stop processing the job.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
news:E2F9A42E-C173-4B35-8BA3-749239454E90@.microsoft.com...
> Thanks for that. I am getting different errors in the log at different
> times
> from the same problem. The problem in detailed in my post "Login Prompt
> after ~3min timeout".
> I am reguarly getting out memory errors, but I have looked at the machine
> and it is only using ~1/3 of available memory and CPU so I think that is a
> red herring.
> The report runs fine if the data allows it to complete before 2.5 -
> 3mins -
> this seems to be 2.5mins on the test server I am using and 3mins on the
> live
> environment.
> The following messages are the only consistant ones I am seeing in the
> log:
> w3wp!runningjobs!1568!28/09/2005-09:46:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!1568!28/09/2005-09:46:45:: w WARN:
> RunningJobContext.Cancel; failed
> w3wp!runningjobs!1568!28/09/2005-09:47:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:48:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:49:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:50:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!fe4!28/09/2005-09:51:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:52:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> Any thoughts, pointers or suggestions will be gratefully received.
> "Daniel Reib [MSFT]" wrote:
>> You are looking at the error log. The log contains the text that is
>> displayed to users so it is a little misleading when seeing it in the log
>> itself. Can you include the entire call stack?
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
>> news:83BFFE98-BBF5-4CD6-9D71-CAC85D4E3228@.microsoft.com...
>> > Hopefully this will be a simple question.
>> >
>> > Where is the error log located? I am looking in
>> >
>> > program files\microsoft sql server\mssql\reporting services\LogFile
>> >
>> > at a file called ReportServer__09_27_2005_11_38_23.log inside that file
>> > is
>> > a
>> > message:
>> >
>> > e ERROR: Throwing
>> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> > An internal error occurred on the report server. See the error log for
>> > more
>> > details., ;
>> >
>> > Where can I fine the error log it refers to? Everything has been
>> > installed
>> > to default locations.
>> >
>> > Thanks
>>
Location of deployed rdl file on the ReportingServer
Hi all,
I have a reporting server on which My rdl files are deployed from my
development machine.
Can any one tell me where is the physical location of those rdl files on
the reporting server where the files get deployed.
I did a search for rdl files on the Reportingserver but I could not found any.
Also is it possible to add a .rdl file from the ReportServer machine to my
VS.NET project IDE on a remote development machine
Any suggestions will be highly appreciated.
Thanks in advance,
siajThe RDL files are stored in the report server database. They are not stored
on disk.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"siaj" <siaj@.discussions.microsoft.com> wrote in message
news:DABA9613-D421-4F10-AE66-5BB0D46BFBCD@.microsoft.com...
> Hi all,
> I have a reporting server on which My rdl files are deployed from my
> development machine.
> Can any one tell me where is the physical location of those rdl files on
> the reporting server where the files get deployed.
> I did a search for rdl files on the Reportingserver but I could not found
> any.
> Also is it possible to add a .rdl file from the ReportServer machine to my
> VS.NET project IDE on a remote development machine
> Any suggestions will be highly appreciated.
> Thanks in advance,
> siaj|||On Mon, 24 Jan 2005 15:13:02 -0800, "siaj"
<siaj@.discussions.microsoft.com> wrote:
>Hi all,
>I have a reporting server on which My rdl files are deployed from my
>development machine.
>Can any one tell me where is the physical location of those rdl files on
>the reporting server where the files get deployed.
>I did a search for rdl files on the Reportingserver but I could not found any.
>Also is it possible to add a .rdl file from the ReportServer machine to my
>VS.NET project IDE on a remote development machine
>Any suggestions will be highly appreciated.
>Thanks in advance,
>siaj
The deployed reports are stored in the RS database (default name -
ReportServer), not in physical files. The table name is "Catalog".
If you need to change a deployed report, you can download it from the
Report Server web page and use it in your VS project. Open the list of
reports (http://<servername>/Reports/Pages/Folder.aspx), click "Show
Details" on the toolbar. Now click the Edit icon preceeding the report
you need, this will open the properties page for the report. There are
2 links under "Report Definition": Edit and Update. "Edit" downloads
the RDL file for you, and "Update" allows you to upload the file back.|||Thanks Lukasz/Usenet
siaj
"Usenet User" wrote:
> On Mon, 24 Jan 2005 15:13:02 -0800, "siaj"
> <siaj@.discussions.microsoft.com> wrote:
> >Hi all,
> >I have a reporting server on which My rdl files are deployed from my
> >development machine.
> >Can any one tell me where is the physical location of those rdl files on
> >the reporting server where the files get deployed.
> >I did a search for rdl files on the Reportingserver but I could not found any.
> >
> >Also is it possible to add a .rdl file from the ReportServer machine to my
> >VS.NET project IDE on a remote development machine
> >
> >Any suggestions will be highly appreciated.
> >
> >Thanks in advance,
> >siaj
>
> The deployed reports are stored in the RS database (default name -
> ReportServer), not in physical files. The table name is "Catalog".
> If you need to change a deployed report, you can download it from the
> Report Server web page and use it in your VS project. Open the list of
> reports (http://<servername>/Reports/Pages/Folder.aspx), click "Show
> Details" on the toolbar. Now click the Edit icon preceeding the report
> you need, this will open the properties page for the report. There are
> 2 links under "Report Definition": Edit and Update. "Edit" downloads
> the RDL file for you, and "Update" allows you to upload the file back.
>
I have a reporting server on which My rdl files are deployed from my
development machine.
Can any one tell me where is the physical location of those rdl files on
the reporting server where the files get deployed.
I did a search for rdl files on the Reportingserver but I could not found any.
Also is it possible to add a .rdl file from the ReportServer machine to my
VS.NET project IDE on a remote development machine
Any suggestions will be highly appreciated.
Thanks in advance,
siajThe RDL files are stored in the report server database. They are not stored
on disk.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"siaj" <siaj@.discussions.microsoft.com> wrote in message
news:DABA9613-D421-4F10-AE66-5BB0D46BFBCD@.microsoft.com...
> Hi all,
> I have a reporting server on which My rdl files are deployed from my
> development machine.
> Can any one tell me where is the physical location of those rdl files on
> the reporting server where the files get deployed.
> I did a search for rdl files on the Reportingserver but I could not found
> any.
> Also is it possible to add a .rdl file from the ReportServer machine to my
> VS.NET project IDE on a remote development machine
> Any suggestions will be highly appreciated.
> Thanks in advance,
> siaj|||On Mon, 24 Jan 2005 15:13:02 -0800, "siaj"
<siaj@.discussions.microsoft.com> wrote:
>Hi all,
>I have a reporting server on which My rdl files are deployed from my
>development machine.
>Can any one tell me where is the physical location of those rdl files on
>the reporting server where the files get deployed.
>I did a search for rdl files on the Reportingserver but I could not found any.
>Also is it possible to add a .rdl file from the ReportServer machine to my
>VS.NET project IDE on a remote development machine
>Any suggestions will be highly appreciated.
>Thanks in advance,
>siaj
The deployed reports are stored in the RS database (default name -
ReportServer), not in physical files. The table name is "Catalog".
If you need to change a deployed report, you can download it from the
Report Server web page and use it in your VS project. Open the list of
reports (http://<servername>/Reports/Pages/Folder.aspx), click "Show
Details" on the toolbar. Now click the Edit icon preceeding the report
you need, this will open the properties page for the report. There are
2 links under "Report Definition": Edit and Update. "Edit" downloads
the RDL file for you, and "Update" allows you to upload the file back.|||Thanks Lukasz/Usenet
siaj
"Usenet User" wrote:
> On Mon, 24 Jan 2005 15:13:02 -0800, "siaj"
> <siaj@.discussions.microsoft.com> wrote:
> >Hi all,
> >I have a reporting server on which My rdl files are deployed from my
> >development machine.
> >Can any one tell me where is the physical location of those rdl files on
> >the reporting server where the files get deployed.
> >I did a search for rdl files on the Reportingserver but I could not found any.
> >
> >Also is it possible to add a .rdl file from the ReportServer machine to my
> >VS.NET project IDE on a remote development machine
> >
> >Any suggestions will be highly appreciated.
> >
> >Thanks in advance,
> >siaj
>
> The deployed reports are stored in the RS database (default name -
> ReportServer), not in physical files. The table name is "Catalog".
> If you need to change a deployed report, you can download it from the
> Report Server web page and use it in your VS project. Open the list of
> reports (http://<servername>/Reports/Pages/Folder.aspx), click "Show
> Details" on the toolbar. Now click the Edit icon preceeding the report
> you need, this will open the properties page for the report. There are
> 2 links under "Report Definition": Edit and Update. "Edit" downloads
> the RDL file for you, and "Update" allows you to upload the file back.
>
Location of default instance SQL server 2005 files
I have just installed SQL Server 2005. I was not given a choice during installation (that I remember seeing anyway) about which drive I wanted to place the default SQL instance on.
It ended up on C: and I needed it on D:.
So my questions are:
Is there a way to move it to D: that is easier than the way you had to go about it in SQL 2000?
Is there a way to do it during setup so I can avoid this in the future?
There is a file called template.ini located at the same folder as setup.exe. In this file, all related command line parameters are discussed when SQL Server 2005 is installed under unattended mode, i.e., command line. You can specify paths to install SQL Server 2005 components.
Under attended mode, i.e., GUI mode, during selecting components to install, clicking the Advanced button will prompt to change paths to install SQL Server 2005 components.
|||
Jiongxiong,
There is no file "template.ini" with the SQL setup program (cd or installed location).
The SQL readme points to a generic windows deployment info page - which is unhelpful.
|||If you're installing SQL Server Express edition you are running an executable called SQLEXPR.EXE. This is a compressed package that when run expands the contents to a temporary folder, runs the installation and then deletes the temporary folder. You can persist the uncompressed contents by running sqlexpr.exe /x - this will prompt you for a folder to save the uncompressed files. Once uncompressed you'll find the template.ini file in this folder (same folder as setup.exe). The parameters that can be passed to setup.exe can also be passed to sqlexpr.exe - the compression tool will pass the parameters to setup.exe when it runs it.
If you're installing an edition other than Express you will find template.ini in the same folder as setup.exe.
Cheers,
Dan
Jiongxiong, you are right! Sorry, I missed the template.ini file somehow. I will see if it works for my clean install tests.
It is simply amazing that M$ can not do simple file management for installation. There are files, they have versions, they need to be copied to a folder from the CD, and some settings stored - how complicated is that? Well if you are M$ you make SQL05 installation into a mass of gobble-gook. SQL Server 05 is not ready for production use until its installation abomination is fixed!
Most people think that SQL Server setup is just about copying files and writing some reg keys. While it's true it's only a small fraction of what setup does. Here is a small sampling of the other things SQL Server setup does.
SQL Server setup checks the configuration of the machine to determine if the machine is in a valid state - which improves the chances of a good installation. Windows Installer doesn't support this.
SQL Server is a multi-instance product. Windows Installer doesn't support this.
SQL Server requires configuration to happen as part of the setup process. Windows Installer doesn't support this. If you've ever performed a MySQL installation a separate tool is launched post setup to do the configuration - although at the end of setup you don't have a working server.
SQL Server cluster install is extremely robust. Every other product I've seen requires you to rerun setup on every node and make sure the configurations are the same. SQL does this for you. Windows Installer doesn't support cluster installs.
SQL Server requires a secure installation. This means that every file/directory/service/reg key is ACL'd to the appropriate service account. Windows Installer doesn't support this.
SQL Server setup supports version and edition upgrade. Windows Installer doesn't support this.
Windows Installer handles very well the copying of files and the writing of reg keys, but it doesn't handle any of the other complexities associated with SQL Server setup. Everywhere I mentioned that Windows Installer doesn't support something it means we've had to build it. I'm not using this as an excuse, but merely highlighting the fact that setup is much more than just copying files and writing reg keys. Anyone who's worked on the setup of a complex product (such as SQL or Visual Studio) will attest to this.
Is our setup perfect? No. But I certainly don't believe it deserves the criticism. There are millions of ways a user can hose their machine and it would be impossible for us to test for every single case. I'm sure you'll be tempted to compare SQL with other products - don't. There are very few products that come to mind that have the same level of complexity that SQL Server does. Again, this is not an excuse for any particular bug that remains in setup. The complexity of SQL Server has grown tremendously from SQL Server 7.0. The setup has had to embrace the increased complexity and deliver a stable and consistent experience. I believe this was achieved.
Cheers,
Dan
Dan:
This is critical tidbit that surely belongs in Embedding SQL Server Express in Custom Applications. That's a 32-page article (from November 2005) at the Microsoft SQL Server Developer Centre, and while it obviously spends time on template.ini, it doesn't tell you how to find it. Luckily for me, I found your reply on this forum.
Please pass this on to Robert Walters, who wrote the article.
Regards
Josh Korn
Location of default instance SQL server 2005 files
I have just installed SQL Server 2005. I was not given a choice during installation (that I remember seeing anyway) about which drive I wanted to place the default SQL instance on.
It ended up on C: and I needed it on D:.
So my questions are:
- Is there a way to move it to D: that is easier than the way you had to go about it in SQL 2000? Is there a way to do it during setup so I can avoid this in the future?
There is a file called template.ini located at the same folder as setup.exe. In this file, all related command line parameters are discussed when SQL Server 2005 is installed under unattended mode, i.e., command line. You can specify paths to install SQL Server 2005 components.
Under attended mode, i.e., GUI mode, during selecting components to install, clicking the Advanced button will prompt to change paths to install SQL Server 2005 components.
|||
Jiongxiong,
There is no file "template.ini" with the SQL setup program (cd or installed location).
The SQL readme points to a generic windows deployment info page - which is unhelpful.
|||If you're installing SQL Server Express edition you are running an executable called SQLEXPR.EXE. This is a compressed package that when run expands the contents to a temporary folder, runs the installation and then deletes the temporary folder. You can persist the uncompressed contents by running sqlexpr.exe /x - this will prompt you for a folder to save the uncompressed files. Once uncompressed you'll find the template.ini file in this folder (same folder as setup.exe). The parameters that can be passed to setup.exe can also be passed to sqlexpr.exe - the compression tool will pass the parameters to setup.exe when it runs it.
If you're installing an edition other than Express you will find template.ini in the same folder as setup.exe.
Cheers,
Dan
Jiongxiong, you are right! Sorry, I missed the template.ini file somehow. I will see if it works for my clean install tests.
It is simply amazing that M$ can not do simple file management for installation. There are files, they have versions, they need to be copied to a folder from the CD, and some settings stored - how complicated is that? Well if you are M$ you make SQL05 installation into a mass of gobble-gook. SQL Server 05 is not ready for production use until its installation abomination is fixed!
Most people think that SQL Server setup is just about copying files and writing some reg keys. While it's true it's only a small fraction of what setup does. Here is a small sampling of the other things SQL Server setup does.
SQL Server setup checks the configuration of the machine to determine if the machine is in a valid state - which improves the chances of a good installation. Windows Installer doesn't support this.
SQL Server is a multi-instance product. Windows Installer doesn't support this.
SQL Server requires configuration to happen as part of the setup process. Windows Installer doesn't support this. If you've ever performed a MySQL installation a separate tool is launched post setup to do the configuration - although at the end of setup you don't have a working server.
SQL Server cluster install is extremely robust. Every other product I've seen requires you to rerun setup on every node and make sure the configurations are the same. SQL does this for you. Windows Installer doesn't support cluster installs.
SQL Server requires a secure installation. This means that every file/directory/service/reg key is ACL'd to the appropriate service account. Windows Installer doesn't support this.
SQL Server setup supports version and edition upgrade. Windows Installer doesn't support this.
Windows Installer handles very well the copying of files and the writing of reg keys, but it doesn't handle any of the other complexities associated with SQL Server setup. Everywhere I mentioned that Windows Installer doesn't support something it means we've had to build it. I'm not using this as an excuse, but merely highlighting the fact that setup is much more than just copying files and writing reg keys. Anyone who's worked on the setup of a complex product (such as SQL or Visual Studio) will attest to this.
Is our setup perfect? No. But I certainly don't believe it deserves the criticism. There are millions of ways a user can hose their machine and it would be impossible for us to test for every single case. I'm sure you'll be tempted to compare SQL with other products - don't. There are very few products that come to mind that have the same level of complexity that SQL Server does. Again, this is not an excuse for any particular bug that remains in setup. The complexity of SQL Server has grown tremendously from SQL Server 7.0. The setup has had to embrace the increased complexity and deliver a stable and consistent experience. I believe this was achieved.
Cheers,
Dan
Dan:
This is critical tidbit that surely belongs in Embedding SQL Server Express in Custom Applications. That's a 32-page article (from November 2005) at the Microsoft SQL Server Developer Centre, and while it obviously spends time on template.ini, it doesn't tell you how to find it. Luckily for me, I found your reply on this forum.
Please pass this on to Robert Walters, who wrote the article.
Regards
Josh Korn
Location of default instance SQL server 2005 files
I have just installed SQL Server 2005. I was not given a choice during installation (that I remember seeing anyway) about which drive I wanted to place the default SQL instance on.
It ended up on C: and I needed it on D:.
So my questions are:
- Is there a way to move it to D: that is easier than the way you had to go about it in SQL 2000? Is there a way to do it during setup so I can avoid this in the future?
There is a file called template.ini located at the same folder as setup.exe. In this file, all related command line parameters are discussed when SQL Server 2005 is installed under unattended mode, i.e., command line. You can specify paths to install SQL Server 2005 components.
Under attended mode, i.e., GUI mode, during selecting components to install, clicking the Advanced button will prompt to change paths to install SQL Server 2005 components.
|||
Jiongxiong,
There is no file "template.ini" with the SQL setup program (cd or installed location).
The SQL readme points to a generic windows deployment info page - which is unhelpful.
|||If you're installing SQL Server Express edition you are running an executable called SQLEXPR.EXE. This is a compressed package that when run expands the contents to a temporary folder, runs the installation and then deletes the temporary folder. You can persist the uncompressed contents by running sqlexpr.exe /x - this will prompt you for a folder to save the uncompressed files. Once uncompressed you'll find the template.ini file in this folder (same folder as setup.exe). The parameters that can be passed to setup.exe can also be passed to sqlexpr.exe - the compression tool will pass the parameters to setup.exe when it runs it.
If you're installing an edition other than Express you will find template.ini in the same folder as setup.exe.
Cheers,
Dan
Jiongxiong, you are right! Sorry, I missed the template.ini file somehow. I will see if it works for my clean install tests.
It is simply amazing that M$ can not do simple file management for installation. There are files, they have versions, they need to be copied to a folder from the CD, and some settings stored - how complicated is that? Well if you are M$ you make SQL05 installation into a mass of gobble-gook. SQL Server 05 is not ready for production use until its installation abomination is fixed!
Most people think that SQL Server setup is just about copying files and writing some reg keys. While it's true it's only a small fraction of what setup does. Here is a small sampling of the other things SQL Server setup does.
SQL Server setup checks the configuration of the machine to determine if the machine is in a valid state - which improves the chances of a good installation. Windows Installer doesn't support this.
SQL Server is a multi-instance product. Windows Installer doesn't support this.
SQL Server requires configuration to happen as part of the setup process. Windows Installer doesn't support this. If you've ever performed a MySQL installation a separate tool is launched post setup to do the configuration - although at the end of setup you don't have a working server.
SQL Server cluster install is extremely robust. Every other product I've seen requires you to rerun setup on every node and make sure the configurations are the same. SQL does this for you. Windows Installer doesn't support cluster installs.
SQL Server requires a secure installation. This means that every file/directory/service/reg key is ACL'd to the appropriate service account. Windows Installer doesn't support this.
SQL Server setup supports version and edition upgrade. Windows Installer doesn't support this.
Windows Installer handles very well the copying of files and the writing of reg keys, but it doesn't handle any of the other complexities associated with SQL Server setup. Everywhere I mentioned that Windows Installer doesn't support something it means we've had to build it. I'm not using this as an excuse, but merely highlighting the fact that setup is much more than just copying files and writing reg keys. Anyone who's worked on the setup of a complex product (such as SQL or Visual Studio) will attest to this.
Is our setup perfect? No. But I certainly don't believe it deserves the criticism. There are millions of ways a user can hose their machine and it would be impossible for us to test for every single case. I'm sure you'll be tempted to compare SQL with other products - don't. There are very few products that come to mind that have the same level of complexity that SQL Server does. Again, this is not an excuse for any particular bug that remains in setup. The complexity of SQL Server has grown tremendously from SQL Server 7.0. The setup has had to embrace the increased complexity and deliver a stable and consistent experience. I believe this was achieved.
Cheers,
Dan
Dan:
This is critical tidbit that surely belongs in Embedding SQL Server Express in Custom Applications. That's a 32-page article (from November 2005) at the Microsoft SQL Server Developer Centre, and while it obviously spends time on template.ini, it doesn't tell you how to find it. Luckily for me, I found your reply on this forum.
Please pass this on to Robert Walters, who wrote the article.
Regards
Josh Korn
Location of dbases.
Hi!
When I'm looking at the properties of my dbases I see there are at c:\program files\ms sql server\ etc..
But I want to put ALL my current and future databases to E:\.
Can somebody tell me how to achieve that?
You should use alter Database command to move the files to the new location.
When you create your database you can specfic the location that you want the files create as part of the create Database command.
Michelle
|||
I've found out how to place new databases.
But can't I igive up a default location? Cause people that don't know about it maybe put it in the wrong place.
And the alter command? I tried to change it true the GUI but the location properties where grey.
Location of database and log files
We are beginning a new implemenation of SQL2000 and considering the locations
of the database and log files. Am I correct that the Log files must reside on
the same server as SQL? Is performance effected at all if the database file
resides on another server?
Well - think what would happen if you lost the other server or even if you
lost network connection.
It's not a good idea.
"SeaBob" <SeaBob@.discussions.microsoft.com> wrote in message
news:B5C2383C-D301-4096-8C74-9247CBEE6F75@.microsoft.com...
> We are beginning a new implemenation of SQL2000 and considering the
locations
> of the database and log files. Am I correct that the Log files must reside
on
> the same server as SQL? Is performance effected at all if the database
file
> resides on another server?
|||Data and log files can and should be split across multiple volumes or
devices on a server (either direct-attached or SAN storage) but those
devices must be attached to the server that is running SQL.
In certain very restricted circumstances and on certain hardware only NAS
storage is supported but this is definitely not recommended other than in
exceptional cases.
Installation of databases on a remote server is not supported, nor would it
be a desriable or sensible thing to do from the point of view of
architecture, performance, resilience or data-integrity.
David Portas
SQL Server MVP
of the database and log files. Am I correct that the Log files must reside on
the same server as SQL? Is performance effected at all if the database file
resides on another server?
Well - think what would happen if you lost the other server or even if you
lost network connection.
It's not a good idea.
"SeaBob" <SeaBob@.discussions.microsoft.com> wrote in message
news:B5C2383C-D301-4096-8C74-9247CBEE6F75@.microsoft.com...
> We are beginning a new implemenation of SQL2000 and considering the
locations
> of the database and log files. Am I correct that the Log files must reside
on
> the same server as SQL? Is performance effected at all if the database
file
> resides on another server?
|||Data and log files can and should be split across multiple volumes or
devices on a server (either direct-attached or SAN storage) but those
devices must be attached to the server that is running SQL.
In certain very restricted circumstances and on certain hardware only NAS
storage is supported but this is definitely not recommended other than in
exceptional cases.
Installation of databases on a remote server is not supported, nor would it
be a desriable or sensible thing to do from the point of view of
architecture, performance, resilience or data-integrity.
David Portas
SQL Server MVP
Location of database and log files
We are beginning a new implemenation of SQL2000 and considering the locations
of the database and log files. Am I correct that the Log files must reside on
the same server as SQL? Is performance effected at all if the database file
resides on another server?Well - think what would happen if you lost the other server or even if you
lost network connection.
It's not a good idea. :(
"SeaBob" <SeaBob@.discussions.microsoft.com> wrote in message
news:B5C2383C-D301-4096-8C74-9247CBEE6F75@.microsoft.com...
> We are beginning a new implemenation of SQL2000 and considering the
locations
> of the database and log files. Am I correct that the Log files must reside
on
> the same server as SQL? Is performance effected at all if the database
file
> resides on another server?|||Data and log files can and should be split across multiple volumes or
devices on a server (either direct-attached or SAN storage) but those
devices must be attached to the server that is running SQL.
In certain very restricted circumstances and on certain hardware only NAS
storage is supported but this is definitely not recommended other than in
exceptional cases.
Installation of databases on a remote server is not supported, nor would it
be a desriable or sensible thing to do from the point of view of
architecture, performance, resilience or data-integrity.
--
David Portas
SQL Server MVP
--
of the database and log files. Am I correct that the Log files must reside on
the same server as SQL? Is performance effected at all if the database file
resides on another server?Well - think what would happen if you lost the other server or even if you
lost network connection.
It's not a good idea. :(
"SeaBob" <SeaBob@.discussions.microsoft.com> wrote in message
news:B5C2383C-D301-4096-8C74-9247CBEE6F75@.microsoft.com...
> We are beginning a new implemenation of SQL2000 and considering the
locations
> of the database and log files. Am I correct that the Log files must reside
on
> the same server as SQL? Is performance effected at all if the database
file
> resides on another server?|||Data and log files can and should be split across multiple volumes or
devices on a server (either direct-attached or SAN storage) but those
devices must be attached to the server that is running SQL.
In certain very restricted circumstances and on certain hardware only NAS
storage is supported but this is definitely not recommended other than in
exceptional cases.
Installation of databases on a remote server is not supported, nor would it
be a desriable or sensible thing to do from the point of view of
architecture, performance, resilience or data-integrity.
--
David Portas
SQL Server MVP
--
Location of Data Files
I have installed SQL Server 2000 with Master / Model /
MSDB databases in C Drive.
Since the size of C Drive is not sufficient, is it
possible for me to restore a database backup from another
SQL Server to D:\MSSQL\Data ?
ThanksThis article may help you
http://support.microsoft.com/?kbid=224071
--
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Roger Lee" <rogerlee@.nospam.com> wrote in message
news:06b101c36553$fd1b6db0$a101280a@.phx.gbl...
> I have installed SQL Server 2000 with Master / Model /
> MSDB databases in C Drive.
> Since the size of C Drive is not sufficient, is it
> possible for me to restore a database backup from another
> SQL Server to D:\MSSQL\Data ?
> Thankssql
MSDB databases in C Drive.
Since the size of C Drive is not sufficient, is it
possible for me to restore a database backup from another
SQL Server to D:\MSSQL\Data ?
ThanksThis article may help you
http://support.microsoft.com/?kbid=224071
--
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Roger Lee" <rogerlee@.nospam.com> wrote in message
news:06b101c36553$fd1b6db0$a101280a@.phx.gbl...
> I have installed SQL Server 2000 with Master / Model /
> MSDB databases in C Drive.
> Since the size of C Drive is not sufficient, is it
> possible for me to restore a database backup from another
> SQL Server to D:\MSSQL\Data ?
> Thankssql
Location of .MDF and .LDF files
Does anyone know where a good article pertaining to where you should locate your Data and Log files (in SQL Server 2005)?
I read an article several years ago stating that Log files should be on a seperate RAID 1 and Data on a seperate RAID 5.
Anyway, any help is appreciated.
Look at http://www.sql-server-performance.com/faq/sqlviewfaq.aspx?faqid=62
Subscribe to:
Posts (Atom)