Data File in a Different machine on the network.

Hi All,

I have a requirement to create the database with data and log files in
a different machine on the network.

Googling, I got a link which said Mapped drives do not work but UNC paths
work. However in my case, both are failing.

Any advices or links on net will be highly useful.

Thanks and Regards,
Chandra MohanDon't do this. It's not supported by Microsoft, you will lose all the
benefits of a client-server database and you risk corrupting your data.

Read this article:

http://www.mssqlserver.com/faq/gene...tworkdrives.asp

--
David Portas
----
Please reply only to the newsgroup
--|||bschandramohan@.yahoo.com (Chandra Mohan) wrote in message news:<bb0ef6.0309282105.59f0d698@.posting.google.com>...
> Hi All,
> I have a requirement to create the database with data and log files in
> a different machine on the network.
> Googling, I got a link which said Mapped drives do not work but UNC paths
> work. However in my case, both are failing.
> Any advices or links on net will be highly useful.
> Thanks and Regards,
> Chandra Mohan

Check this KB article:

http://support.microsoft.com/defaul...1&Product=sql2k

You can put database files on network drives by setting trace flag
1807, but it is not supported unless the files are on a NAS which is
specifically certified for SQL Server. Often, the NAS will make the
network drive appear like a local one, so you won't need to set the
trace flag on anyway.

Putting a database on a normal UNC share is a very bad idea - you
won't be able to guarantee data integrity and performance will suffer.

Simon|||David Portas (REMOVE_BEFORE_REPLYING_dportas@.acm.org) writes:
> Don't do this. It's not supported by Microsoft, you will lose all the
> benefits of a client-server database and you risk corrupting your data.

I agree that putting a database on a network drive is an extremely bad
idea, but I don't see where the client-server issue comes in. You can
still connect a lots of clients to that database, as if the database
had been a drive local to the database server. (Well, lots and lots.
If there are lots, corruption might appear within the hour.)

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||What I had in mind was that you lose the performance advantage (compared to
a desktop database running on a network) of server-based processing. And you
sacrifice much of the resilience of transaction management and logging.

--
David Portas
----
Please reply only to the newsgroup
--

"Erland Sommarskog" <sommar@.algonet.se> wrote in message
news:Xns9405EBB63563DYazorman@.127.0.0.1...
> David Portas (REMOVE_BEFORE_REPLYING_dportas@.acm.org) writes:
> > Don't do this. It's not supported by Microsoft, you will lose all the
> > benefits of a client-server database and you risk corrupting your data.
> I agree that putting a database on a network drive is an extremely bad
> idea, but I don't see where the client-server issue comes in. You can
> still connect a lots of clients to that database, as if the database
> had been a drive local to the database server. (Well, lots and lots.
> If there are lots, corruption might appear within the hour.)
>
> --
> Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||David Portas (REMOVE_BEFORE_REPLYING_dportas@.acm.org) writes:
> What I had in mind was that you lose the performance advantage (compared
> to a desktop database running on a network) of server-based processing.
> And you sacrifice much of the resilience of transaction management and
> logging.

You mean that rather running client on machine A and server on machine B,
we're running both server and client on A, and only have the database files
on B.

Yes, this is killing the client-server concept. (Ever heard of Visual
SourceSafe? That's an example of this architecture.)

I don't know why people want to put databases on network devices, but
my assumption is that the most common reason is simply space constraint
on the server, so they try to rent space somewhere else in the network.
In this case, I guess clients still connect from somewhere else.

But rather than renting the space, it's better to rent the entire disk
and move into cabinet. Or see your local hardware dealer...

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

daily backup and log shipping

Hi,
I am in the process of setting up log shipping for a large database ~ 1GB over VPN and slow WAN link.
I intend to setup and sync the servers on main office and ship after that, the warm standby db to remote site.
My question is how the daily full backups of database will afect my log shipping.
To keep this servers in sync I intend to use only daily transaction logs backups/restores. I do not want to copy a full backup of 1GB daily over the WAN. However at local site I still want to perform a daily full backup.
As I know when a full backup run it will also truncate the transaction logs, so if these large daily full backups will not be copied and restored over the WAN, the warm standby server will run out of sync. This is because a part of transaction log that will be truncated when full backup is done will not be restored to remote site.
Is there any way to do full backups after initial sync without truncating the transaction logs? Has anyone an answer to my problem?
Thank you,
Zorba
Zorba,
A full database backup does not truncate the transaction log. When you start log shipping, you can make as many full backups of the primary database as you want - it will not affect log shipping. However, you cannot make both a full database backup and a transaction log backup of the same database at the same time.
Hope this helps,
Ron
Ron Talmage
SQL Server MVP
"Zorba" <nospam@.nonexistent> wrote in message news:OX0Z6LemEHA.3336@.TK2MSFTNGP10.phx.gbl...
Hi,
I am in the process of setting up log shipping for a large database ~ 1GB over VPN and slow WAN link.
I intend to setup and sync the servers on main office and ship after that, the warm standby db to remote site.
My question is how the daily full backups of database will afect my log shipping.
To keep this servers in sync I intend to use only daily transaction logs backups/restores. I do not want to copy a full backup of 1GB daily over the WAN. However at local site I still want to perform a daily full backup.
As I know when a full backup run it will also truncate the transaction logs, so if these large daily full backups will not be copied and restored over the WAN, the warm standby server will run out of sync. This is because a part of transaction log that will be truncated when full backup is done will not be restored to remote site.
Is there any way to do full backups after initial sync without truncating the transaction logs? Has anyone an answer to my problem?
Thank you,
Zorba

CVS Export in ASCII format

For the CSV export problem, where excel opens data into one column, I
had to add a report link using the below code to fix the problem. Is
there a way to change the underlying export encoding in reporting
services?
="javascript:void(window.open(top.frames[0].frames[1].location.href.replace('Format=HTML4.0','Format=CSV&rc%3aEncoding=ASCII'),'_blank'))"There is for RS 2005. Not for RS 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<slov1@.hotmail.com> wrote in message
news:1135297330.158158.120010@.g49g2000cwa.googlegroups.com...
> For the CSV export problem, where excel opens data into one column, I
> had to add a report link using the below code to fix the problem. Is
> there a way to change the underlying export encoding in reporting
> services?
> ="javascript:void(window.open(top.frames[0].frames[1].location.href.replace('Format=HTML4.0','Format=CSV&rc%3aEncoding=ASCII'),'_blank'))"
>

Customizing the Home Page

Hi,
Anyone have a link to any instructions on how to customize the RS Home page?
I'd like the change the bolded 'Home' text with our company's name.
Thanks
JerryAccording to the Hitchhiker's Guide to SQL Server 2000 Reporting
Services, you should be able to do that by accessing and editing the
ReportingServices.css file on the box where ReportServer resides. They
list the path as C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\Report Manager\Styles. They warn several times to back up the
original CSS file and try your changes on your test server. I don't
have access to our report server box so I've never tried this. Good
luck!!