Estimating Disk Space

Thanks for your replies Tibor / John.
Is there any script/tool available to estimate the size of
the target database. I have the table structures and
estimated rows.
Thanks,
HariI believe that the book "Inside SQL Server 2000" from MS Press comes with such a tool. The book is a
"must" IMO for any intermediate/advanced SQL Server person anyhow, IMO... :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hari Shankar" <anonymous@.discussions.microsoft.com> wrote in message
news:2429f01c45f3c$1f2b89c0$a401280a@.phx.gbl...
> Thanks for your replies Tibor / John.
> Is there any script/tool available to estimate the size of
> the target database. I have the table structures and
> estimated rows.
> Thanks,
> Harisql

Errors Copying Data Base

I'm trying to copy a data base from one server to another. Both servers are running 2005 MSDE, on Win 2k3, the target server is 64 bit.

I'm using the Copy Database function, and ultimately it fails with the error in the event viewer in the targe machine:

Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a, faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug? 0, fault address 0x0000000000027d0d.

I have tried both the Attach/Detach & the SMO method, and they both give me the same error. I have 'Repaired' the .NET framework on the target machine, with the same result.

Does anyone have any Suggestions? I really only need at this time to make one copy of the database.

Thanks

Phil

When you say "2005 MSDE", do you mean "2005 Express Edition"? You mentioned the target server is 64bit, is it IA64 or AMD64? My best guess is that you installed x86 version of SQL Server Express on AMD64 platform with WOW option.

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I have the x64 version of the Developer Edition of MS Sql Server 2005 installed on an AMD64 platform.

|||

More completely, the source server is a 32 bit machine, with MS Sql Server Developer Edition 2005, the target machine is the x64 configuration.

I have tried to initiate the transfer from both ends, i.e. the from the platform with the database pushing it to the platform without the DB, and from the platform without the DB, pulling it from the platform with the db

|||

Move the thread to the right alias. SSIS experts should be able to help out on your problem.

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||the ssis transfer database task should help: http://msdn2.microsoft.com/en-us/library/ms141204.aspx

Error-14262

I did rename my server and followed the steps.
sp_dropserver sp_addserver etc
But cannot make this server a target server
Error-14262 The specified msx does not exist 'any ideas
great people?.The other servers see the master server Ok
Thanks Michael>
> I did rename my server and followed the steps.
> sp_dropserver sp_addserver etc
> But cannot make this server a target server
> Error-14262 The specified msx does not exist 'any ideas
> great people?.The other servers see the master server Ok
>
> Thanks Michael
--
This could be a permissions problem. Start the SQL Server service on the
target server using a domain administrator account and see how you go.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:ZFXu9dFTEHA.2160@.cpmsftngxa10.phx.gbl...
> --
> This could be a permissions problem. Start the SQL Server service on the
> target server using a domain administrator account and see how you go.
> Hope this helps,
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>|||seen this issue before . Its because the originating_server field in the
msdb..sysjobs table stores the computername / instance of the server. So
when you renamed then it is now wrong
I would just update the column to reflect the new computername (After
backing up msdb)
cheers,
Andy Ball
"dimitris" <dantoniades@.mshf.com.au> wrote in message
news:OT9x3zFTEHA.2944@.tk2msftngp13.phx.gbl...
> "Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in messag
e
> news:ZFXu9dFTEHA.2160@.cpmsftngxa10.phx.gbl...
> rights.
>

Error-14262

I did rename my server and followed the steps.
sp_dropserver sp_addserver etc
But cannot make this server a target server
Error-14262 The specified msx does not exist 'any ideas
great people?.The other servers see the master server Ok
Thanks Michael>
> I did rename my server and followed the steps.
> sp_dropserver sp_addserver etc
> But cannot make this server a target server
> Error-14262 The specified msx does not exist 'any ideas
> great people?.The other servers see the master server Ok
>
> Thanks Michael
--
This could be a permissions problem. Start the SQL Server service on the
target server using a domain administrator account and see how you go.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||"Eric Cárdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:ZFXu9dFTEHA.2160@.cpmsftngxa10.phx.gbl...
> >
> > I did rename my server and followed the steps.
> > sp_dropserver sp_addserver etc
> >
> > But cannot make this server a target server
> >
> > Error-14262 The specified msx does not exist 'any ideas
> > great people?.The other servers see the master server Ok
> >
> >
> > Thanks Michael
> --
> This could be a permissions problem. Start the SQL Server service on the
> target server using a domain administrator account and see how you go.
> Hope this helps,
> --
> Eric Cárdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>|||seen this issue before . Its because the originating_server field in the
msdb..sysjobs table stores the computername / instance of the server. So
when you renamed then it is now wrong
I would just update the column to reflect the new computername (After
backing up msdb)
cheers,
Andy Ball
"dimitris" <dantoniades@.mshf.com.au> wrote in message
news:OT9x3zFTEHA.2944@.tk2msftngp13.phx.gbl...
> "Eric Cárdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
> news:ZFXu9dFTEHA.2160@.cpmsftngxa10.phx.gbl...
> > >
> > > I did rename my server and followed the steps.
> > > sp_dropserver sp_addserver etc
> > >
> > > But cannot make this server a target server
> > >
> > > Error-14262 The specified msx does not exist 'any ideas
> > > great people?.The other servers see the master server Ok
> > >
> > >
> > > Thanks Michael
> > --
> > This could be a permissions problem. Start the SQL Server service on the
> > target server using a domain administrator account and see how you go.
> >
> > Hope this helps,
> >
> > --
> > Eric Cárdenas
> > Senior support professional
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
>

Error-14262

I did rename my server and followed the steps.
sp_dropserver sp_addserver etc
But cannot make this server a target server
Error-14262 The specified msx does not exist 'any ideas
great people?.The other servers see the master server Ok
Thanks Michael
>
> I did rename my server and followed the steps.
> sp_dropserver sp_addserver etc
> But cannot make this server a target server
> Error-14262 The specified msx does not exist 'any ideas
> great people?.The other servers see the master server Ok
>
> Thanks Michael
This could be a permissions problem. Start the SQL Server service on the
target server using a domain administrator account and see how you go.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:ZFXu9dFTEHA.2160@.cpmsftngxa10.phx.gbl...
> --
> This could be a permissions problem. Start the SQL Server service on the
> target server using a domain administrator account and see how you go.
> Hope this helps,
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||seen this issue before . Its because the originating_server field in the
msdb..sysjobs table stores the computername / instance of the server. So
when you renamed then it is now wrong
I would just update the column to reflect the new computername (After
backing up msdb)
cheers,
Andy Ball
"dimitris" <dantoniades@.mshf.com.au> wrote in message
news:OT9x3zFTEHA.2944@.tk2msftngp13.phx.gbl...
> "Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
> news:ZFXu9dFTEHA.2160@.cpmsftngxa10.phx.gbl...
> rights.
>