Is it possible to have the .rds file in reports folder

Since i have 5 different projects all has the same kind of reports., but calling via 5 different sites all sites on same webserver.

The problem i have is the .rds file name is same in all 5 report projects and it is a shared datasource., now when i compile the report project it will not load or overwrite the .rds file since the name is same, for that reason i tried to have the .rds file in reports folder as a datasource not a shared datasource. but i tried to add it, after i create the datasource, it is automatically going into the shared datasource folder, how can i create a datasource not shared under reports folder.

Thank you very much for all your help and information.

Hello,

From the Project menu, select 'Properties'. In the TargetDataSourceFolder, type the path of where you want the data source to go. From Books Online:

TargetDataSourceFolder

Type the name of the destination folder for publishing the shared data sources that are contained within the project. This value is optional. If you do not specify a folder, the data source is published to the same folder as the report. If the folder does not exist on the report server, Report Designer creates the folder when the reports are published. If a folder is located within another folder, include the path to the folder, starting at the root, for example, Folder1/Folder2/Folder3.

Hope this helps.

Jarret

|||Thank you very much Jarret.....

Is it necessary to exclude the \data folder when using NetBackup?

I am not a big fan of paying 3rd party backup vendors for
agents, but I need to make sure that we are not risking
corrupting the database files. I have setup maintenance
plans to do the fulls and log backups to disk. We are just
beginning to roll out NetBackup 5.0 in production, and
without the SQL agent installed, it appears as though it
can backup all the data files without error. Should I
exclude the "hot files" in NetBackup, and rely on the bak
and trn files if I need to restore the whole server?
Meaning, if my prod server died, and I needed to restore
from tape to a hotspare, is it possible to restore the
database(s) if the mssql\data\*.mdf and ldf files are not
restored?
If this is a lame question, I apologize, as I am not a
DBA, but a storage guy, and we have no official SQL DBA's
in house yet.
Thanks for any and all help!
DaveYes, you want to avoid trying to back up the mdf and ldf files and instead
just back up the native SQL backup files (trn/bak) to tape. You would use
these to restore the database. BOL has plenty of detail on backup and
restore in the Administering SQL Server>Backing Up and Restoring Databases
section
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
> I am not a big fan of paying 3rd party backup vendors for
> agents, but I need to make sure that we are not risking
> corrupting the database files. I have setup maintenance
> plans to do the fulls and log backups to disk. We are just
> beginning to roll out NetBackup 5.0 in production, and
> without the SQL agent installed, it appears as though it
> can backup all the data files without error. Should I
> exclude the "hot files" in NetBackup, and rely on the bak
> and trn files if I need to restore the whole server?
> Meaning, if my prod server died, and I needed to restore
> from tape to a hotspare, is it possible to restore the
> database(s) if the mssql\data\*.mdf and ldf files are not
> restored?
> If this is a lame question, I apologize, as I am not a
> DBA, but a storage guy, and we have no official SQL DBA's
> in house yet.
> Thanks for any and all help!
> Dave
>
>|||Yes, I was planning on keeping the maintenance plan. I was
not sure if it is possible to restore the trn\bak files if
real SQL server datafiles were not restored (ie excluding
the \data\*.* in NetBackup policy). Is there some command
line you can run to start SQL enough to restore the files?
I've looked in the online help, but I must be missing the
obvious. What is BOL?
thanks!

>--Original Message--
>Yes, you want to avoid trying to back up the mdf and ldf
files and instead
>just back up the native SQL backup files (trn/bak) to
tape. You would use
>these to restore the database. BOL has plenty of detail
on backup and
>restore in the Administering SQL Server>Backing Up and
Restoring Databases
>section
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Dave" <anonymous@.discussions.microsoft.com> wrote in
message
>news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
for
just
bak
not
DBA's
>
>.
>|||> Is there some command
> line you can run to start SQL enough to restore the files?
?
When you do a RESTORE in SQL Server, the database is created, if it doesn't
exists. If a system database is broken, you need to use REBUILDM.EXE to
create new system databases so that you can start SQL Server and then do the
restore. If the whole installation is toast, you need to install SQL Server
first instead. :-)
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:2ad501c3fcb0$61c267c0$a001280a@.phx.gbl...
> Yes, I was planning on keeping the maintenance plan. I was
> not sure if it is possible to restore the trn\bak files if
> real SQL server datafiles were not restored (ie excluding
> the \data\*.* in NetBackup policy). Is there some command
> line you can run to start SQL enough to restore the files?
> I've looked in the online help, but I must be missing the
> obvious. What is BOL?
> thanks!
>
> files and instead
> tape. You would use
> on backup and
> Restoring Databases
> message
> for
> just
> bak
> not
> DBA's

Is it necessary to exclude the \data folder when using NetBackup?

I am not a big fan of paying 3rd party backup vendors for
agents, but I need to make sure that we are not risking
corrupting the database files. I have setup maintenance
plans to do the fulls and log backups to disk. We are just
beginning to roll out NetBackup 5.0 in production, and
without the SQL agent installed, it appears as though it
can backup all the data files without error. Should I
exclude the "hot files" in NetBackup, and rely on the bak
and trn files if I need to restore the whole server?
Meaning, if my prod server died, and I needed to restore
from tape to a hotspare, is it possible to restore the
database(s) if the mssql\data\*.mdf and ldf files are not
restored?
If this is a lame question, I apologize, as I am not a
DBA, but a storage guy, and we have no official SQL DBA's
in house yet.
Thanks for any and all help!
DaveYou must do sql backups using maintenance plan or using
SQL Agent. Make sure to backup bak and trn files on tape
if you use maintenance plan. You should not rely on "hot
files" backup in NebBackup because it doesn't always work
in case of sql files. SQL backups (through a maintenance
plan or NetBackup sql agent) is the only reliable way to
restore sql databases.
I would advise against doing backup of \data folder,
specially if backup window is limited.
hth.
>--Original Message--
>I am not a big fan of paying 3rd party backup vendors for
>agents, but I need to make sure that we are not risking
>corrupting the database files. I have setup maintenance
>plans to do the fulls and log backups to disk. We are
just
>beginning to roll out NetBackup 5.0 in production, and
>without the SQL agent installed, it appears as though it
>can backup all the data files without error. Should I
>exclude the "hot files" in NetBackup, and rely on the bak
>and trn files if I need to restore the whole server?
>Meaning, if my prod server died, and I needed to restore
>from tape to a hotspare, is it possible to restore the
>database(s) if the mssql\data\*.mdf and ldf files are not
>restored?
>If this is a lame question, I apologize, as I am not a
>DBA, but a storage guy, and we have no official SQL DBA's
>in house yet.
>Thanks for any and all help!
>Dave
>
>.
>|||Yes, you want to avoid trying to back up the mdf and ldf files and instead
just back up the native SQL backup files (trn/bak) to tape. You would use
these to restore the database. BOL has plenty of detail on backup and
restore in the Administering SQL Server>Backing Up and Restoring Databases
section
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
> I am not a big fan of paying 3rd party backup vendors for
> agents, but I need to make sure that we are not risking
> corrupting the database files. I have setup maintenance
> plans to do the fulls and log backups to disk. We are just
> beginning to roll out NetBackup 5.0 in production, and
> without the SQL agent installed, it appears as though it
> can backup all the data files without error. Should I
> exclude the "hot files" in NetBackup, and rely on the bak
> and trn files if I need to restore the whole server?
> Meaning, if my prod server died, and I needed to restore
> from tape to a hotspare, is it possible to restore the
> database(s) if the mssql\data\*.mdf and ldf files are not
> restored?
> If this is a lame question, I apologize, as I am not a
> DBA, but a storage guy, and we have no official SQL DBA's
> in house yet.
> Thanks for any and all help!
> Dave
>
>|||Yes, I was planning on keeping the maintenance plan. I was
not sure if it is possible to restore the trn\bak files if
real SQL server datafiles were not restored (ie excluding
the \data\*.* in NetBackup policy). Is there some command
line you can run to start SQL enough to restore the files?
I've looked in the online help, but I must be missing the
obvious. What is BOL?
thanks!
>--Original Message--
>Yes, you want to avoid trying to back up the mdf and ldf
files and instead
>just back up the native SQL backup files (trn/bak) to
tape. You would use
>these to restore the database. BOL has plenty of detail
on backup and
>restore in the Administering SQL Server>Backing Up and
Restoring Databases
>section
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Dave" <anonymous@.discussions.microsoft.com> wrote in
message
>news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
>> I am not a big fan of paying 3rd party backup vendors
for
>> agents, but I need to make sure that we are not risking
>> corrupting the database files. I have setup maintenance
>> plans to do the fulls and log backups to disk. We are
just
>> beginning to roll out NetBackup 5.0 in production, and
>> without the SQL agent installed, it appears as though it
>> can backup all the data files without error. Should I
>> exclude the "hot files" in NetBackup, and rely on the
bak
>> and trn files if I need to restore the whole server?
>> Meaning, if my prod server died, and I needed to restore
>> from tape to a hotspare, is it possible to restore the
>> database(s) if the mssql\data\*.mdf and ldf files are
not
>> restored?
>> If this is a lame question, I apologize, as I am not a
>> DBA, but a storage guy, and we have no official SQL
DBA's
>> in house yet.
>> Thanks for any and all help!
>> Dave
>>
>
>.
>|||> Is there some command
> line you can run to start SQL enough to restore the files?
?
When you do a RESTORE in SQL Server, the database is created, if it doesn't
exists. If a system database is broken, you need to use REBUILDM.EXE to
create new system databases so that you can start SQL Server and then do the
restore. If the whole installation is toast, you need to install SQL Server
first instead. :-)
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:2ad501c3fcb0$61c267c0$a001280a@.phx.gbl...
> Yes, I was planning on keeping the maintenance plan. I was
> not sure if it is possible to restore the trn\bak files if
> real SQL server datafiles were not restored (ie excluding
> the \data\*.* in NetBackup policy). Is there some command
> line you can run to start SQL enough to restore the files?
> I've looked in the online help, but I must be missing the
> obvious. What is BOL?
> thanks!
> >--Original Message--
> >Yes, you want to avoid trying to back up the mdf and ldf
> files and instead
> >just back up the native SQL backup files (trn/bak) to
> tape. You would use
> >these to restore the database. BOL has plenty of detail
> on backup and
> >restore in the Administering SQL Server>Backing Up and
> Restoring Databases
> >section
> >
> >--
> >HTH
> >
> >Jasper Smith (SQL Server MVP)
> >
> >I support PASS - the definitive, global
> >community for SQL Server professionals -
> >http://www.sqlpass.org
> >
> >
> >"Dave" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
> >> I am not a big fan of paying 3rd party backup vendors
> for
> >> agents, but I need to make sure that we are not risking
> >> corrupting the database files. I have setup maintenance
> >> plans to do the fulls and log backups to disk. We are
> just
> >> beginning to roll out NetBackup 5.0 in production, and
> >> without the SQL agent installed, it appears as though it
> >> can backup all the data files without error. Should I
> >> exclude the "hot files" in NetBackup, and rely on the
> bak
> >> and trn files if I need to restore the whole server?
> >> Meaning, if my prod server died, and I needed to restore
> >> from tape to a hotspare, is it possible to restore the
> >> database(s) if the mssql\data\*.mdf and ldf files are
> not
> >> restored?
> >> If this is a lame question, I apologize, as I am not a
> >> DBA, but a storage guy, and we have no official SQL
> DBA's
> >> in house yet.
> >> Thanks for any and all help!
> >>
> >> Dave
> >>
> >>
> >>
> >
> >
> >.
> >

Is is it advisable for SQL installation folder to be on the same drive as Windows?

Hey Community,

What are the guidelines for installing the SQL Software? Is it bottleneck if both Windows and SQL software are installed on the same drive ( I have all the database .mdfs and and .ldfs on a seperate RAID array)?

thanks,
Saptagiri Tangudu
PNT Marketing Services

Under normal situations, that is not a problem, and is often done that way.

is folder App_data uses to store database by .net 2.0 hosting companies?

I am workin on a website for me and my friend. I want to host it at a hosting company. In asp.net 2.0 projects are build with the App_data folder, which can stores data source such as a SQL Server 2005 database. But when i want to host the site at a hosting company, will the database goed into this folder?

I also have a hosting company and dealing with the same problem.

The company has a SQL server that is different than the web server so; you have to create the database in the SQL server and then have your asp codes connect to that server by a connection string. You have to have the IP address of the server, your username and password to make that work.

Hope this helps.