Rebuildm Error

i use Win AD Server 2000 and SQL server 2000

My Master DB crashed and i run Rebuildm to rebuild
After setting CD-Rom path runing rebuildm

it show error -1
and i check OS event log

17207 :
udopen: Operation system error 5(access deny)during the creation/opening of physical device d:\sqldata\mssql\data\master.mdf

FCB::Open failed: Could not open device d:\sqldata\mssql\data\master.mdf
for virtual device number (VDN) 1.

what's the problem ?

thxOriginally posted by mmmaya
i use Win AD Server 2000 and SQL server 2000

My Master DB crashed and i run Rebuildm to rebuild
After setting CD-Rom path runing rebuildm

it show error -1
and i check OS event log

17207 :
udopen: Operation system error 5(access deny)during the creation/opening of physical device d:\sqldata\mssql\data\master.mdf

FCB::Open failed: Could not open device d:\sqldata\mssql\data\master.mdf
for virtual device number (VDN) 1.

what's the problem ?

thx

rebuildm needs to be able to write to the path that you specified as the source directory. If fails or hangs because it cannot write to your CD-ROM drive. So you'll need to copy the contents of the data directory to a writable device (eg. C:). See http://support.microsoft.com/default.aspx?scid=kb;en-us;273572|||Originally posted by cbatwillis
rebuildm needs to be able to write to the path that you specified as the source directory. If fails or hangs because it cannot write to your CD-ROM drive. So you'll need to copy the contents of the data directory to a writable device (eg. C:). See http://support.microsoft.com/default.aspx?scid=kb;en-us;273572

Yes!! It's problem with Read-Only !
thank you ^_^

RebuildLog

hi friends,

one of my database corrupted , after setting that database into emergency mode , dbcc Rebuildlog was not working in sql server 2005, so how to proceed further?Hello yasodhakalimuthu. I must tell you that you have mistakenly posted in the Articles section of the SQL Server Group. The SQL Server help forum is here.

Thanks for joining. I hope that you find your way around the site.

Rebuilding the Master Database

Hi
I thought that I had this procedure down pat, but just got
hit. What I am trying to do is change the collation
setting for the entire database. These settings only have
to apply to NEW databases, so the old ones I am dettaching
and then reattaching them after the rebuild.
The problem lies in that there are users and DTS packages
that are saved in the old MASTER and MSDB databases, and
when I restore them from old backups, the following
happens.
1) I cannot seem to recover the DTS packages.
2) The collation settings for these two databases revert
to the previous setting.
Any help please or is there a fool proof method of doing
this.
Cheers
PaulIt is not supported to have different collations between the system databases, so rebuild and then
restore a system database is not the way to go (because as you have noticed, you get the old
collation when you restore). So, do a rebuild and then re-create the stuff in master and msdb. You
can script jobs etc for msdb in EM. As for master, most important is probably logins, see KB's
listed below. But don't forget that there are other things to consider as well (sysconfigures,
sysservers etc).
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Paul Blackler" <pblackler@.themis.co.uk> wrote in message
news:084001c3adcd$e5b65aa0$a501280a@.phx.gbl...
> Hi
> I thought that I had this procedure down pat, but just got
> hit. What I am trying to do is change the collation
> setting for the entire database. These settings only have
> to apply to NEW databases, so the old ones I am dettaching
> and then reattaching them after the rebuild.
> The problem lies in that there are users and DTS packages
> that are saved in the old MASTER and MSDB databases, and
> when I restore them from old backups, the following
> happens.
> 1) I cannot seem to recover the DTS packages.
> 2) The collation settings for these two databases revert
> to the previous setting.
> Any help please or is there a fool proof method of doing
> this.
> Cheers
> Paulsql

Real Time ROLAP different then ROLAP

What is the benefit of setting the proactive cache to Real Time ROLAP. Wouldn't this be the same as ROLAP. Confused on why there is such an option.

Books online doesn't seem to answer it clearly.

Proactive caching adds the ability to automatically detect changes in source data and update Analysis Services objects appropriately. In the case of Real-Time ROLAP (which was also an option in AS 2000), the AS server can detect data changes (via events, polling or client-initiated notification) and invalidate its in-memory cache - without proactive caching, explicit processing would be needed to drop the cache.

http://msdn2.microsoft.com/en-us/library/ms175646.aspx

>>

Real Time ROLAP

OLAP is in real time. Detail data and aggregations are stored in relational format. The server listens for notifications when data changes and all queries reflect the current state of the data (zero latency). This setting would typically be used for a data source with very frequent and continuous updates when the very latest data is always required by users.

>>

|||

Thanks. I'm getting closer to understanding.

How can the latency be zero? If in the Real Time ROLAP case, reprocessing of the cube is required to modify aggregations (assuming non 0% aggregation). This would imply not zero latency, but the latency it takes to reprocess the cube. To me it seems like Real Time MOLAP is more likely to have the latest data over Real Time ROLAP. What am I missing?

|||

I don't believe that there is a standard setting such as Real Time MOLAP - with pure MOLAP, there will be some latency while the cache is rebuilt. However, proactive caching policy can cause queries to be directed to the fact table (ROLAP mode) while the MOLAP cache is being rebuilt - but this would no longer be pure MOLAP.

According to BOL below, no aggregations are stored for Real Time OLAP, so there is probably no significant reprocessing time involved when data is updated - [MS] folks could provide more detailed info:

http://msdn2.microsoft.com/en-us/library/ms174915(SQL.90).aspx

>>

Partition Storage (SSAS)

...

Real-time ROLAP is typically used when clients want to see changes immediately. No aggregations are stored with real-time ROLAP.

>>

|||

Hi Deepak

Could you please send me some code sample and "how to " for send client notification to Analysis Server?

Thanks alot.
Regards;
Rakesh

Real Time ROLAP different then ROLAP

What is the benefit of setting the proactive cache to Real Time ROLAP. Wouldn't this be the same as ROLAP. Confused on why there is such an option.

Books online doesn't seem to answer it clearly.

Proactive caching adds the ability to automatically detect changes in source data and update Analysis Services objects appropriately. In the case of Real-Time ROLAP (which was also an option in AS 2000), the AS server can detect data changes (via events, polling or client-initiated notification) and invalidate its in-memory cache - without proactive caching, explicit processing would be needed to drop the cache.

http://msdn2.microsoft.com/en-us/library/ms175646.aspx

>>

Real Time ROLAP

OLAP is in real time. Detail data and aggregations are stored in relational format. The server listens for notifications when data changes and all queries reflect the current state of the data (zero latency). This setting would typically be used for a data source with very frequent and continuous updates when the very latest data is always required by users.

>>

|||

Thanks. I'm getting closer to understanding.

How can the latency be zero? If in the Real Time ROLAP case, reprocessing of the cube is required to modify aggregations (assuming non 0% aggregation). This would imply not zero latency, but the latency it takes to reprocess the cube. To me it seems like Real Time MOLAP is more likely to have the latest data over Real Time ROLAP. What am I missing?

|||

I don't believe that there is a standard setting such as Real Time MOLAP - with pure MOLAP, there will be some latency while the cache is rebuilt. However, proactive caching policy can cause queries to be directed to the fact table (ROLAP mode) while the MOLAP cache is being rebuilt - but this would no longer be pure MOLAP.

According to BOL below, no aggregations are stored for Real Time OLAP, so there is probably no significant reprocessing time involved when data is updated - [MS] folks could provide more detailed info:

http://msdn2.microsoft.com/en-us/library/ms174915(SQL.90).aspx

>>

Partition Storage (SSAS)

...

Real-time ROLAP is typically used when clients want to see changes immediately. No aggregations are stored with real-time ROLAP.

>>

|||

Hi Deepak

Could you please send me some code sample and "how to " for send client notification to Analysis Server?

Thanks alot.
Regards;
Rakesh