Re: recreate system tables

You could restore the entire database then delete all the data, shrink it
and then back it up again. Once you've done that backup you'd have it for
future reference. Maybe someone else can come up with something better but I
can't think of another way to preserve the IDs.

--
David Portas
SQL Server MVP
--

"Vassago" <iciruzzi@xxxxxxxxx> wrote in message
news:1122572272.797029.108370@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> It's long to tell why I need the ids but I can tell you that is a third
> party tool and it works that way, I can't change it. I also can tell
> tou that I hate it because the way it works but I can't do anything
> about it.
> What you suggest is nearly imposible, I can't recreate the ids for
> every primary key and every index.
> i don't care if the database is messy, I just need the ids.
> Is there any way to backup just the schema withou the data?
>


.

Relevant Pages

  • Re: How to PURGE a transaction log?
    ... This doesn't shrink the actual file size. ... Make sure you understand backup and restore architecture for 6.5 *really* ... make sure you understand the database architecture regarding database ... doing dummy transactions and DUMP TRANSACTION until the log have moved ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL 2005 + MOSS 2007 + Size config LOG
    ... If you leave the database in full recovery model, then you will need to modify your maintenance plans to include another job that runs every hour that backs up the transaction log. ... Once you have that job setup and running, you can run the shrinkfile and shrink the file. ... The file will grow again to handle the number of transactions you have between each transaction log backup. ...
    (microsoft.public.sqlserver.server)
  • Re: SQL 2005 Shrink issue
    ... Check out this scenario to see what happens in case you perform only full backup: ... in this scenario if your database corrupts you'd lose only 1 hour of data at most. ... To restore your database to its most recent point, you'd first restore the full backup and then the log backups one after another. ... Of course you can shrink your database and log file when your database in FULL Recovery Model. ...
    (microsoft.public.sqlserver.tools)
  • Re: ALTER DATABASE (optimization job)
    ... Why do you want to shrink the file each week? ... > I have a database with a data file 16GB with Recovery model FULL ... > When this night run occurs, the transaction log on my database increases to ... > 2) After the backup change the database recovery model to simple (so no log ...
    (microsoft.public.sqlserver.tools)
  • Re: ALTER DATABASE (optimization job)
    ... Why do you want to shrink the file each week? ... > I have a database with a data file 16GB with Recovery model FULL ... > When this night run occurs, the transaction log on my database increases to ... > 2) After the backup change the database recovery model to simple (so no log ...
    (microsoft.public.sqlserver.programming)