Showing posts with label backup. Show all posts
Showing posts with label backup. Show all posts

Wednesday, March 28, 2012

Migrating beta 2 AS to beta 3 AS?

Hi,
Is there any suggestion to migrate beta 2 AS db to beta 3 AS db?
I tried to use backup and restore, and it did not work.
I have lots of MDX. I do not want to recreate AS in beta 3. U know, it is
lots of work from scratch.
Thanks,
Guangming
Strictly speaking there is no Beta 3.
I suspect you are out of luck but you might be better asking your
question on the microsoft.private.sqlserver2005.analysisservices.o lap
newsgroup.
Login information is located at
http://communities.microsoft.com/new...lcomePage.htm.
Andrew Watt
MVP - InfoPath
On Thu, 6 Oct 2005 10:42:01 -0700, Word 2003 memory Leakage
<Word2003memoryLeakage@.discussions.microsoft.com > wrote:

>Hi,
>Is there any suggestion to migrate beta 2 AS db to beta 3 AS db?
>I tried to use backup and restore, and it did not work.
>I have lots of MDX. I do not want to recreate AS in beta 3. U know, it is
>lots of work from scratch.
>Thanks,
>Guangming
|||I solved this problem by generating AS script in beta 2 and rerun it in beta 3.
THere is a beta 3. Not sure what you mean.
"Andrew Watt [MVP - InfoPath]" wrote:

> Strictly speaking there is no Beta 3.
> I suspect you are out of luck but you might be better asking your
> question on the microsoft.private.sqlserver2005.analysisservices.o lap
> newsgroup.
> Login information is located at
> http://communities.microsoft.com/new...lcomePage.htm.
> Andrew Watt
> MVP - InfoPath
> On Thu, 6 Oct 2005 10:42:01 -0700, Word 2003 memory Leakage
> <Word2003memoryLeakage@.discussions.microsoft.com > wrote:
>
>

Migrating beta 2 AS to beta 3 AS?

Hi,
Is there any suggestion to migrate beta 2 AS db to beta 3 AS db?
I tried to use backup and restore, and it did not work.
I have lots of MDX. I do not want to recreate AS in beta 3. U know, it is
lots of work from scratch.
Thanks,
GuangmingStrictly speaking there is no Beta 3.
I suspect you are out of luck but you might be better asking your
question on the microsoft.private.sqlserver2005.analysisservices.olap
newsgroup.
Login information is located at
[url]http://communities.microsoft.com/newsgroups/ICP/sqlserver2005/us/welcomePage.htm.[
/url]
Andrew Watt
MVP - InfoPath
On Thu, 6 Oct 2005 10:42:01 -0700, Word 2003 memory Leakage
<Word2003memoryLeakage@.discussions.microsoft.com> wrote:

>Hi,
>Is there any suggestion to migrate beta 2 AS db to beta 3 AS db?
>I tried to use backup and restore, and it did not work.
>I have lots of MDX. I do not want to recreate AS in beta 3. U know, it is
>lots of work from scratch.
>Thanks,
>Guangming|||I solved this problem by generating AS script in beta 2 and rerun it in beta
3.
THere is a beta 3. Not sure what you mean.
"Andrew Watt [MVP - InfoPath]" wrote:

> Strictly speaking there is no Beta 3.
> I suspect you are out of luck but you might be better asking your
> question on the microsoft.private.sqlserver2005.analysisservices.olap
> newsgroup.
> Login information is located at
> http://communities.microsoft.com/ne...ge.htm
.
> Andrew Watt
> MVP - InfoPath
> On Thu, 6 Oct 2005 10:42:01 -0700, Word 2003 memory Leakage
> <Word2003memoryLeakage@.discussions.microsoft.com> wrote:
>
>sql

Wednesday, March 21, 2012

migrate sql 2000 to a new sql 2000 server

Does anyone have some simple steps I can follow, I did some reading and
discovered that database backup and recovery is the best way, also recoving
the master, msdb, and the model then the rest of the databases is a good
solution? Please help from a sql2000 server to a another sql2000 serverPerhaps below?
http://vyaskn.tripod.com/moving_sql_server.htm
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mac54" <u43153@.uwe> wrote in message news:832c32f8c50df@.uwe...
> Does anyone have some simple steps I can follow, I did some reading and
> discovered that database backup and recovery is the best way, also recoving
> the master, msdb, and the model then the rest of the databases is a good
> solution? Please help from a sql2000 server to a another sql2000 server
>|||On Apr 25, 1:58=A0am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Perhaps below?
> http://vyaskn.tripod.com/moving_sql_server.htm
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph=
ttp://sqlblog.com/blogs/tibor_karaszi
>
> "mac54" <u43153@.uwe> wrote in messagenews:832c32f8c50df@.uwe...
> > Does anyone have some simple steps I can follow, I did some reading and
> > discovered that database backup and recovery is the best way, also recov=ing
> > the master, msdb, and the model then the rest of the databases is a good=
> > solution? Please help from a sql2000 server to a another sql2000 server-= Hide quoted text -
> - Show quoted text -
You can also refer belo link
http://support.microsoft.com/kb/224071
Thanks
Ajay Rengunthwar
MCTS,MCDBA,MCAD|||maybe this can help you...
http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
bye
"Tibor Karaszi" wrote:
> Perhaps below?
> http://vyaskn.tripod.com/moving_sql_server.htm
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "mac54" <u43153@.uwe> wrote in message news:832c32f8c50df@.uwe...
> > Does anyone have some simple steps I can follow, I did some reading and
> > discovered that database backup and recovery is the best way, also recoving
> > the master, msdb, and the model then the rest of the databases is a good
> > solution? Please help from a sql2000 server to a another sql2000 server
> >
>

Migrate jobs from production to backup

The backup server is using the agent to run log shipping. If I were to
migrate jobs prior to a disaster, the agent would run them. Assuming I can
turn them off so that having them run is not an issue, migrating them one at
a time is tedious.
Is there a way to mass migrate the jobs from one server to the other?
(packages are already migrated)
If such a thing as a mass import of the jobs is available, will the job
migration automatically schedule the packages or will it be necessary to
reschedule them (assuming a disaster event occurs and log-shipping is the
backup solution).
Regards,
Jamie
Hi
"thejamie" wrote:

> The backup server is using the agent to run log shipping. If I were to
> migrate jobs prior to a disaster, the agent would run them. Assuming I can
> turn them off so that having them run is not an issue, migrating them one at
> a time is tedious.
> Is there a way to mass migrate the jobs from one server to the other?
> (packages are already migrated)
>
As described in http://support.microsoft.com/kb/314546 you can script all
jobs.

> If such a thing as a mass import of the jobs is available, will the job
> migration automatically schedule the packages or will it be necessary to
> reschedule them (assuming a disaster event occurs and log-shipping is the
> backup solution).
>
Scripting will re-create the same schedules. The jobs should be enabled when
you are scripting them if you don't want to change them on the destination
server.

> --
> Regards,
> Jamie
John
|||I hadn't noticed before, but there appears to be a wizard in SQL 2005 for
this. We have our production running on 2000 and with disk space at a
premium and backup time stretched to the limit, we needed to start
compressing backups and decided to buy a package. It works great. I am
impressed to see that the 2005 version already does this. Elated actually.
Regards,
Jamie
"John Bell" wrote:

> Hi
> "thejamie" wrote:
> As described in http://support.microsoft.com/kb/314546 you can script all
> jobs.
>
> Scripting will re-create the same schedules. The jobs should be enabled when
> you are scripting them if you don't want to change them on the destination
> server.
>
> John

Migrate jobs from production to backup

The backup server is using the agent to run log shipping. If I were to
migrate jobs prior to a disaster, the agent would run them. Assuming I can
turn them off so that having them run is not an issue, migrating them one at
a time is tedious.
Is there a way to mass migrate the jobs from one server to the other?
(packages are already migrated)
If such a thing as a mass import of the jobs is available, will the job
migration automatically schedule the packages or will it be necessary to
reschedule them (assuming a disaster event occurs and log-shipping is the
backup solution).
Regards,
JamieHi
"thejamie" wrote:

> The backup server is using the agent to run log shipping. If I were to
> migrate jobs prior to a disaster, the agent would run them. Assuming I c
an
> turn them off so that having them run is not an issue, migrating them one
at
> a time is tedious.
> Is there a way to mass migrate the jobs from one server to the other?
> (packages are already migrated)
>
As described in http://support.microsoft.com/kb/314546 you can script all
jobs.

> If such a thing as a mass import of the jobs is available, will the job
> migration automatically schedule the packages or will it be necessary to
> reschedule them (assuming a disaster event occurs and log-shipping is the
> backup solution).
>
Scripting will re-create the same schedules. The jobs should be enabled when
you are scripting them if you don't want to change them on the destination
server.

> --
> Regards,
> Jamie
John|||I hadn't noticed before, but there appears to be a wizard in SQL 2005 for
this. We have our production running on 2000 and with disk space at a
premium and backup time stretched to the limit, we needed to start
compressing backups and decided to buy a package. It works great. I am
impressed to see that the 2005 version already does this. Elated actually.
--
Regards,
Jamie
"John Bell" wrote:

> Hi
> "thejamie" wrote:
>
> As described in http://support.microsoft.com/kb/314546 you can script all
> jobs.
>
> Scripting will re-create the same schedules. The jobs should be enabled wh
en
> you are scripting them if you don't want to change them on the destination
> server.
>
> John

Monday, March 12, 2012

Migrate database from SQL2005 to SQL 2000 (or MSDE)

Hi,
Is it possible to do? (how to do it)
I've tied to do backup and thet to restore it but it hasn't work.
Regards
KrisHi
No, the backup and data files are not compatible when going from 2005 to 200
0.
You have to script the schema and data out and run it against 2000.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kris" wrote:

> Hi,
> Is it possible to do? (how to do it)
> I've tied to do backup and thet to restore it but it hasn't work.
> Regards
> Kris

Migrate database from SQL2005 to SQL 2000 (or MSDE)

Hi,
Is it possible to do? (how to do it)
I've tied to do backup and thet to restore it but it hasn't work.
Regards
KrisHi
No, the backup and data files are not compatible when going from 2005 to 2000.
You have to script the schema and data out and run it against 2000.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kris" wrote:
> Hi,
> Is it possible to do? (how to do it)
> I've tied to do backup and thet to restore it but it hasn't work.
> Regards
> Kris

Migrate database from SQL2005 to SQL 2000 (or MSDE)

Hi,
Is it possible to do? (how to do it)
I've tied to do backup and thet to restore it but it hasn't work.
Regards
Kris
Hi
No, the backup and data files are not compatible when going from 2005 to 2000.
You have to script the schema and data out and run it against 2000.
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kris" wrote:

> Hi,
> Is it possible to do? (how to do it)
> I've tied to do backup and thet to restore it but it hasn't work.
> Regards
> Kris

Migrate Database from SQL Server 2005 beta 3 to Sql Server 2005 Release

Do you now, How can I move database with datas to release version of sql server?
Procedores backup/restore can't help becouse of unsuported version database.

Any ideas?What about generate a schema script? Then run an install of your schema in a new query. You could at least get the db schema but not the data.|||but I have many datas

Migrate Backup DAT file from MS SQL to MSDE 2000

Hi,
Anyone know how to migrate migrate backup file DAT from MS
SQL 7.0 to MSDE 2000?
Thanks
Michael
If this is a backup file created with SQL Servers BACKUP command then you
can simply restore the database to the MSDE 2000 instance. The RESTORE
command will convert the database for you.
Jim
"Michael" <anonymous@.discussions.microsoft.com> wrote in message
news:0a9401c503f4$51839a90$a401280a@.phx.gbl...
> Hi,
> Anyone know how to migrate migrate backup file DAT from MS
> SQL 7.0 to MSDE 2000?
> Thanks
> Michael

Friday, March 9, 2012

Microsoft.SqlServer.Management.Smo Backup and Restore classes

Hi,

Hopefully someone out there will be able to help me with this question. I'm trying to setup my C# program to use the Backup and Restore classes to perform backups and restores on an SQL Express 2005 database.

From the documentation I've read... it seems that when you go to restore the database, it's a good idea to backup the current transaction log. But when I do this using the Backup.SqlBackup method I get an error saying that no database backup is detected so a log backup can't occur. I'm not sure if this has something to do with the fact that I moved my backup files from the default SQL Express/Server Backup folder to a different location. Shouldn't it know I've already performed a backup though?

And does anyone know how to set a parameter to backup to a different file location than the default? I've been doing a backup then a file move. Works the same, but it would be nice to have everything together in the Backup object.

Thanks!

Without full backup transaction log backup is useless. After processing full backup database is marked, so server allows log backups. No any search of backup files, of course.

create database [dummy];
go

-- here will be an error because there is no full backup
backup log [dummy] to disk = 'delete.it.bak'
go

-- this works fine
backup database [dummy] to disk = 'delete.it.bak'
exec xp_cmdshell 'move d:\databases\mssql.1\mssql\backup\delete.it.bak d:\databases\mssql.1\mssql\backup\dont.delete.it.bak'
backup log [dummy] to disk = 'delete.it.bak'
go

drop database [dummy]

To backup file in nondefault directory you should simply specify full path in backup device name. But make sure that SQL Server service account have access to such dir.

WBR, Evergray
--
Words mean nothing...

|||I want to backup to nondefault directory, so I tried

USE master
EXEC sp_addumpdevice 'disk', 'testing_Backup',
'C:\testing.Bak'

BACKUP DATABASE testDB TO testing_Backup

and received the following error message:

Cannot open backup device 'testing_Backup(C:\testing.Bak)'. Operating system error 5(Access is denied.).

I suppose this is due to insufficient access right of SQL Server service account, but what shall I do with it?

|||Windows Vista doesn't allow you to write in root (c:\).
Try it on d:\

Microsoft.SqlServer.Management.Smo Backup and Restore classes

Hi,

Hopefully someone out there will be able to help me with this question. I'm trying to setup my C# program to use the Backup and Restore classes to perform backups and restores on an SQL Express 2005 database.

From the documentation I've read... it seems that when you go to restore the database, it's a good idea to backup the current transaction log. But when I do this using the Backup.SqlBackup method I get an error saying that no database backup is detected so a log backup can't occur. I'm not sure if this has something to do with the fact that I moved my backup files from the default SQL Express/Server Backup folder to a different location. Shouldn't it know I've already performed a backup though?

And does anyone know how to set a parameter to backup to a different file location than the default? I've been doing a backup then a file move. Works the same, but it would be nice to have everything together in the Backup object.

Thanks!

Without full backup transaction log backup is useless. After processing full backup database is marked, so server allows log backups. No any search of backup files, of course.

create database [dummy];
go

-- here will be an error because there is no full backup
backup log [dummy] to disk = 'delete.it.bak'
go

-- this works fine
backup database [dummy] to disk = 'delete.it.bak'
exec xp_cmdshell 'move d:\databases\mssql.1\mssql\backup\delete.it.bak d:\databases\mssql.1\mssql\backup\dont.delete.it.bak'
backup log [dummy] to disk = 'delete.it.bak'
go

drop database [dummy]

To backup file in nondefault directory you should simply specify full path in backup device name. But make sure that SQL Server service account have access to such dir.

WBR, Evergray
--
Words mean nothing...

|||I want to backup to nondefault directory, so I tried

USE master
EXEC sp_addumpdevice 'disk', 'testing_Backup',
'C:\testing.Bak'

BACKUP DATABASE testDB TO testing_Backup

and received the following error message:

Cannot open backup device 'testing_Backup(C:\testing.Bak)'. Operating system error 5(Access is denied.).

I suppose this is due to insufficient access right of SQL Server service account, but what shall I do with it?

|||Windows Vista doesn't allow you to write in root (c:\).
Try it on d:\

Microsoft.SqlServer.Management.Smo Backup and Restore classes

Hi,

Hopefully someone out there will be able to help me with this question. I'm trying to setup my C# program to use the Backup and Restore classes to perform backups and restores on an SQL Express 2005 database.

From the documentation I've read... it seems that when you go to restore the database, it's a good idea to backup the current transaction log. But when I do this using the Backup.SqlBackup method I get an error saying that no database backup is detected so a log backup can't occur. I'm not sure if this has something to do with the fact that I moved my backup files from the default SQL Express/Server Backup folder to a different location. Shouldn't it know I've already performed a backup though?

And does anyone know how to set a parameter to backup to a different file location than the default? I've been doing a backup then a file move. Works the same, but it would be nice to have everything together in the Backup object.

Thanks!

Without full backup transaction log backup is useless. After processing full backup database is marked, so server allows log backups. No any search of backup files, of course.

create database [dummy];
go

-- here will be an error because there is no full backup
backup log [dummy] to disk = 'delete.it.bak'
go

-- this works fine
backup database [dummy] to disk = 'delete.it.bak'
exec xp_cmdshell 'move d:\databases\mssql.1\mssql\backup\delete.it.bak d:\databases\mssql.1\mssql\backup\dont.delete.it.bak'
backup log [dummy] to disk = 'delete.it.bak'
go

drop database [dummy]

To backup file in nondefault directory you should simply specify full path in backup device name. But make sure that SQL Server service account have access to such dir.

WBR, Evergray
--
Words mean nothing...

|||I want to backup to nondefault directory, so I tried

USE master
EXEC sp_addumpdevice 'disk', 'testing_Backup',
'C:\testing.Bak'

BACKUP DATABASE testDB TO testing_Backup

and received the following error message:

Cannot open backup device 'testing_Backup(C:\testing.Bak)'. Operating system error 5(Access is denied.).

I suppose this is due to insufficient access right of SQL Server service account, but what shall I do with it?

|||Windows Vista doesn't allow you to write in root (c:\).
Try it on d:\

Microsoft.SqlServer.Management.Smo Backup and Restore classes

Hi,

Hopefully someone out there will be able to help me with this question. I'm trying to setup my C# program to use the Backup and Restore classes to perform backups and restores on an SQL Express 2005 database.

From the documentation I've read... it seems that when you go to restore the database, it's a good idea to backup the current transaction log. But when I do this using the Backup.SqlBackup method I get an error saying that no database backup is detected so a log backup can't occur. I'm not sure if this has something to do with the fact that I moved my backup files from the default SQL Express/Server Backup folder to a different location. Shouldn't it know I've already performed a backup though?

And does anyone know how to set a parameter to backup to a different file location than the default? I've been doing a backup then a file move. Works the same, but it would be nice to have everything together in the Backup object.

Thanks!

Without full backup transaction log backup is useless. After processing full backup database is marked, so server allows log backups. No any search of backup files, of course.

create database [dummy];
go

-- here will be an error because there is no full backup
backup log [dummy] to disk = 'delete.it.bak'
go

-- this works fine
backup database [dummy] to disk = 'delete.it.bak'
exec xp_cmdshell 'move d:\databases\mssql.1\mssql\backup\delete.it.bak d:\databases\mssql.1\mssql\backup\dont.delete.it.bak'
backup log [dummy] to disk = 'delete.it.bak'
go

drop database [dummy]

To backup file in nondefault directory you should simply specify full path in backup device name. But make sure that SQL Server service account have access to such dir.

WBR, Evergray
--
Words mean nothing...

|||I want to backup to nondefault directory, so I tried

USE master
EXEC sp_addumpdevice 'disk', 'testing_Backup',
'C:\testing.Bak'

BACKUP DATABASE testDB TO testing_Backup

and received the following error message:

Cannot open backup device 'testing_Backup(C:\testing.Bak)'. Operating system error 5(Access is denied.).

I suppose this is due to insufficient access right of SQL Server service account, but what shall I do with it?

|||Windows Vista doesn't allow you to write in root (c:\).
Try it on d:\

Microsoft.SqlServer.Management

I am looking for a way to script out all tables within a SQL Server 2005 database using VB.NET. I am writing a backup utility and have been able to do stored procedures, the data within the tables, but am now stuck on scripting out the tables with their primary keys, indexes, etc. Sure, I could hard-code some stuff like "CREATE TABLE dbo" & strTable, but I am pretty sure there is a way to do it within VB.NET using SMO. So, any help that someone could offer is greatly appreciated.

Thanks

I just googled it and found the following:

http://www.yukonxml.com/articles/smo/

Not sure if the above will be any help for you

Monday, February 20, 2012

Microsoft SQL server Virtual Backup specification

Hi,
My task is to freeze SQL server so that it can be in a consistent state and after my job is done i need to thaw it. I have gone through the VDI specification given by Microsoft SQl server. It is concerned with APIs to third party vendors to take backup of SQL server with or without snapshot. Using that is there a way to do my task ?

Thanks in Advance

Can you tell us a little more about what you're trying to accomplish?

Are you building your own backup app, or what are you accomplishing by freezing the database?

There may be other less disruptive (and easier) methods to use, depending on what you're needing to do.

|||Hi Kevin,
Thanks for the reply.I want to build a backup application. But according to my requirements, i cant install VSS agent on the machine. Is there any way to freeze the SQL server using VDI ?

Microsoft SQL server Virtual Backup specification

Hi,
My task is to freeze SQL server so that it can be in a consistent state and after my job is done i need to thaw it. I have gone through the VDI specification given by Microsoft SQl server. It is concerned with APIs to third party vendors to take backup of SQL server with or without snapshot. Using that is there a way to do my task ?

Thanks in Advance

Can you tell us a little more about what you're trying to accomplish?

Are you building your own backup app, or what are you accomplishing by freezing the database?

There may be other less disruptive (and easier) methods to use, depending on what you're needing to do.

|||Hi Kevin,
Thanks for the reply.I want to build a backup application. But according to my requirements, i cant install VSS agent on the machine. Is there any way to freeze the SQL server using VDI ?

Microsoft SQL server Virtual Backup specification

Hi,
My task is to freeze SQL server so that it can be in a consistent state and after my job is done i need to thaw it. I have gone through the VDI specification given by Microsoft SQl server. It is concerned with APIs to third party vendors to take backup of SQL server with or without snapshot. Using that is there a way to do my task ?

Thanks in Advance

Can you tell us a little more about what you're trying to accomplish?

Are you building your own backup app, or what are you accomplishing by freezing the database?

There may be other less disruptive (and easier) methods to use, depending on what you're needing to do.

|||Hi Kevin,
Thanks for the reply.I want to build a backup application. But according to my requirements, i cant install VSS agent on the machine. Is there any way to freeze the SQL server using VDI ?