I think I am trying to do the impossible.
We have a customer who would like to run an application and the MSDE
directly from a CD. Does anyone know how to get the tempdb to work as CD's
are read only?
Any advice would be appreciated."John Kaye" <John Kaye@.discussions.microsoft.com> wrote in message
news:A5B872EF-B2E1-4C29-9016-5B952E3990F3@.microsoft.com...
> I think I am trying to do the impossible.
> We have a customer who would like to run an application and the MSDE
> directly from a CD. Does anyone know how to get the tempdb to work as CD's
> are read only?
Really not sure HOW or WHY yuo'd do this.. but hack it so the tempdb is on a
physical drive or worse a RAM drive.
I can pretty much guarantee MS won't support this though if you call in with
problems.
What's their real goal?
> Any advice would be appreciated.|||The aim is to be able to inset a CD into a machine and run an application
accessing data in the database. They do not want to have any installation
done. The data is read only but can be cut and diced in many ways and there
is a large quantity of it.
We are trying to see if they will let us run an install. The problem is not
all machines allow access to the C drive for writing with normal user
permissions and not all machines have a D drive. It all depends on how peopl
e
inmplement XP and user profiles.
Some machines will be still running older operating systems as old as
Windows 95.
Trying to make this universal is a bit of a headache.
In the past where I have known the target coinfiguration the install writes
the tempdb to to a known location on the hard drive configured into the
database.
This worked because we had control of the image ont the target machines.
"Greg D. Moore (Strider)" wrote:
> "John Kaye" <John Kaye@.discussions.microsoft.com> wrote in message
> news:A5B872EF-B2E1-4C29-9016-5B952E3990F3@.microsoft.com...
> Really not sure HOW or WHY yuo'd do this.. but hack it so the tempdb is on
a
> physical drive or worse a RAM drive.
> I can pretty much guarantee MS won't support this though if you call in wi
th
> problems.
> What's their real goal?
>
>
>|||SQL Server cannot just be "executed", you need to install, get registry keys
, errorlog files, tempdb
files and all that jazz. You might want to look at some other storage and re
trieval product for
this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Kaye" <helpneeded@.mailinator.com> wrote in message
news:510D5C9C-187E-4E9B-A28F-094FD5AC14AD@.microsoft.com...[vbcol=seagreen]
> The aim is to be able to inset a CD into a machine and run an application
> accessing data in the database. They do not want to have any installation
> done. The data is read only but can be cut and diced in many ways and ther
e
> is a large quantity of it.
> We are trying to see if they will let us run an install. The problem is no
t
> all machines allow access to the C drive for writing with normal user
> permissions and not all machines have a D drive. It all depends on how peo
ple
> inmplement XP and user profiles.
> Some machines will be still running older operating systems as old as
> Windows 95.
> Trying to make this universal is a bit of a headache.
> In the past where I have known the target coinfiguration the install write
s
> the tempdb to to a known location on the hard drive configured into the
> database.
> This worked because we had control of the image ont the target machines.
>
>
> "Greg D. Moore (Strider)" wrote:
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment