Hi there. Running a Sql 2000 installation with latest service pack on
Windows 2000 server. My database dump to disk backup keeps increasing
by about 1 meg per day. The database itself is increasing by a small
percentage of that. In fact the dump is now about the same size as the
database. What's going on? Thanks.
What kind of backup are you doing? If you don't use the INIT option the
current backup will append to the existing ones in the dump device.
Andrew J. Kelly
SQL Server MVP
"cscott" <christopher@.uncommonlaw.com> wrote in message
news:a94f8da8.0406070533.6a59d6fb@.posting.google.c om...
> Hi there. Running a Sql 2000 installation with latest service pack on
> Windows 2000 server. My database dump to disk backup keeps increasing
> by about 1 meg per day. The database itself is increasing by a small
> percentage of that. In fact the dump is now about the same size as the
> database. What's going on? Thanks.
|||Hi ,
To add on to Andrew post, Execute the below comand from query analyzer to
check if BACKUP is executed in append mode.
restore headeronly from disk='Directory\dbname.BAK'
If this list more than 1 entry (Check the postion column in output), means
you have taken the backup in Append mode. To remove he append mode add an
OPTION
INIT along with backup database command
BACKUP DATABASE dbname to disk='c:\dbname.bak' with INIT
Thanks
Hari
MCDBA
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uYtrikJTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> What kind of backup are you doing? If you don't use the INIT option the
> current backup will append to the existing ones in the dump device.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "cscott" <christopher@.uncommonlaw.com> wrote in message
> news:a94f8da8.0406070533.6a59d6fb@.posting.google.c om...
>
|||Used the maintenance plan wizard to set it up. It's a dump to disk.
There aren't many options to select really. It does seem like it's
appending the dump. Is there an option in Enterprise manager to disable
append or will I have to do it the hard way? Thanks.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
|||Maint plan doesn't append. It creates a new backup device each time it performs a backup. Verify using RESTORE
HEADERONLY.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christopher Scott" <christopher@.uncommonlaw.com> wrote in message
news:%23cTXggVTEHA.2416@.TK2MSFTNGP12.phx.gbl...
>
> Used the maintenance plan wizard to set it up. It's a dump to disk.
> There aren't many options to select really. It does seem like it's
> appending the dump. Is there an option in Enterprise manager to disable
> append or will I have to do it the hard way? Thanks.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!
Showing posts with label installation. Show all posts
Showing posts with label installation. Show all posts
Monday, March 19, 2012
Database dump size
Hi there. Running a Sql 2000 installation with latest service pack on
Windows 2000 server. My database dump to disk backup keeps increasing
by about 1 meg per day. The database itself is increasing by a small
percentage of that. In fact the dump is now about the same size as the
database. What's going on? Thanks.What kind of backup are you doing? If you don't use the INIT option the
current backup will append to the existing ones in the dump device.
Andrew J. Kelly
SQL Server MVP
"cscott" <christopher@.uncommonlaw.com> wrote in message
news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
> Hi there. Running a Sql 2000 installation with latest service pack on
> Windows 2000 server. My database dump to disk backup keeps increasing
> by about 1 meg per day. The database itself is increasing by a small
> percentage of that. In fact the dump is now about the same size as the
> database. What's going on? Thanks.|||Hi ,
To add on to Andrew post, Execute the below comand from query analyzer to
check if BACKUP is executed in append mode.
restore headeronly from disk='Directory\dbname.BAK'
If this list more than 1 entry (Check the postion column in output), means
you have taken the backup in Append mode. To remove he append mode add an
OPTION
INIT along with backup database command
BACKUP DATABASE dbname to disk='c:\dbname.bak' with INIT
Thanks
Hari
MCDBA
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uYtrikJTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> What kind of backup are you doing? If you don't use the INIT option the
> current backup will append to the existing ones in the dump device.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "cscott" <christopher@.uncommonlaw.com> wrote in message
> news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
>|||Used the maintenance plan wizard to set it up. It's a dump to disk.
There aren't many options to select really. It does seem like it's
appending the dump. Is there an option in Enterprise manager to disable
append or will I have to do it the hard way? Thanks.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Maint plan doesn't append. It creates a new backup device each time it perfo
rms a backup. Verify using RESTORE
HEADERONLY.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christopher Scott" <christopher@.uncommonlaw.com> wrote in message
news:%23cTXggVTEHA.2416@.TK2MSFTNGP12.phx.gbl...
>
> Used the maintenance plan wizard to set it up. It's a dump to disk.
> There aren't many options to select really. It does seem like it's
> appending the dump. Is there an option in Enterprise manager to disable
> append or will I have to do it the hard way? Thanks.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!
Windows 2000 server. My database dump to disk backup keeps increasing
by about 1 meg per day. The database itself is increasing by a small
percentage of that. In fact the dump is now about the same size as the
database. What's going on? Thanks.What kind of backup are you doing? If you don't use the INIT option the
current backup will append to the existing ones in the dump device.
Andrew J. Kelly
SQL Server MVP
"cscott" <christopher@.uncommonlaw.com> wrote in message
news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
> Hi there. Running a Sql 2000 installation with latest service pack on
> Windows 2000 server. My database dump to disk backup keeps increasing
> by about 1 meg per day. The database itself is increasing by a small
> percentage of that. In fact the dump is now about the same size as the
> database. What's going on? Thanks.|||Hi ,
To add on to Andrew post, Execute the below comand from query analyzer to
check if BACKUP is executed in append mode.
restore headeronly from disk='Directory\dbname.BAK'
If this list more than 1 entry (Check the postion column in output), means
you have taken the backup in Append mode. To remove he append mode add an
OPTION
INIT along with backup database command
BACKUP DATABASE dbname to disk='c:\dbname.bak' with INIT
Thanks
Hari
MCDBA
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uYtrikJTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> What kind of backup are you doing? If you don't use the INIT option the
> current backup will append to the existing ones in the dump device.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "cscott" <christopher@.uncommonlaw.com> wrote in message
> news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
>|||Used the maintenance plan wizard to set it up. It's a dump to disk.
There aren't many options to select really. It does seem like it's
appending the dump. Is there an option in Enterprise manager to disable
append or will I have to do it the hard way? Thanks.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Maint plan doesn't append. It creates a new backup device each time it perfo
rms a backup. Verify using RESTORE
HEADERONLY.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christopher Scott" <christopher@.uncommonlaw.com> wrote in message
news:%23cTXggVTEHA.2416@.TK2MSFTNGP12.phx.gbl...
>
> Used the maintenance plan wizard to set it up. It's a dump to disk.
> There aren't many options to select really. It does seem like it's
> appending the dump. Is there an option in Enterprise manager to disable
> append or will I have to do it the hard way? Thanks.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!
Database dump size
Hi there. Running a Sql 2000 installation with latest service pack on
Windows 2000 server. My database dump to disk backup keeps increasing
by about 1 meg per day. The database itself is increasing by a small
percentage of that. In fact the dump is now about the same size as the
database. What's going on? Thanks.Hello
Can you please give us details of the type of backup your
doing as well as your recovery model.
J
>--Original Message--
>Hi there. Running a Sql 2000 installation with latest
service pack on
>Windows 2000 server. My database dump to disk backup
keeps increasing
>by about 1 meg per day. The database itself is increasing
by a small
>percentage of that. In fact the dump is now about the
same size as the
>database. What's going on? Thanks.
>.
>|||What kind of backup are you doing? If you don't use the INIT option the
current backup will append to the existing ones in the dump device.
--
Andrew J. Kelly
SQL Server MVP
"cscott" <christopher@.uncommonlaw.com> wrote in message
news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
> Hi there. Running a Sql 2000 installation with latest service pack on
> Windows 2000 server. My database dump to disk backup keeps increasing
> by about 1 meg per day. The database itself is increasing by a small
> percentage of that. In fact the dump is now about the same size as the
> database. What's going on? Thanks.|||Hi ,
To add on to Andrew post, Execute the below comand from query analyzer to
check if BACKUP is executed in append mode.
restore headeronly from disk='Directory\dbname.BAK'
If this list more than 1 entry (Check the postion column in output), means
you have taken the backup in Append mode. To remove he append mode add an
OPTION
INIT along with backup database command
BACKUP DATABASE dbname to disk='c:\dbname.bak' with INIT
Thanks
Hari
MCDBA
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uYtrikJTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> What kind of backup are you doing? If you don't use the INIT option the
> current backup will append to the existing ones in the dump device.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "cscott" <christopher@.uncommonlaw.com> wrote in message
> news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
> > Hi there. Running a Sql 2000 installation with latest service pack on
> > Windows 2000 server. My database dump to disk backup keeps increasing
> > by about 1 meg per day. The database itself is increasing by a small
> > percentage of that. In fact the dump is now about the same size as the
> > database. What's going on? Thanks.
>
Windows 2000 server. My database dump to disk backup keeps increasing
by about 1 meg per day. The database itself is increasing by a small
percentage of that. In fact the dump is now about the same size as the
database. What's going on? Thanks.Hello
Can you please give us details of the type of backup your
doing as well as your recovery model.
J
>--Original Message--
>Hi there. Running a Sql 2000 installation with latest
service pack on
>Windows 2000 server. My database dump to disk backup
keeps increasing
>by about 1 meg per day. The database itself is increasing
by a small
>percentage of that. In fact the dump is now about the
same size as the
>database. What's going on? Thanks.
>.
>|||What kind of backup are you doing? If you don't use the INIT option the
current backup will append to the existing ones in the dump device.
--
Andrew J. Kelly
SQL Server MVP
"cscott" <christopher@.uncommonlaw.com> wrote in message
news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
> Hi there. Running a Sql 2000 installation with latest service pack on
> Windows 2000 server. My database dump to disk backup keeps increasing
> by about 1 meg per day. The database itself is increasing by a small
> percentage of that. In fact the dump is now about the same size as the
> database. What's going on? Thanks.|||Hi ,
To add on to Andrew post, Execute the below comand from query analyzer to
check if BACKUP is executed in append mode.
restore headeronly from disk='Directory\dbname.BAK'
If this list more than 1 entry (Check the postion column in output), means
you have taken the backup in Append mode. To remove he append mode add an
OPTION
INIT along with backup database command
BACKUP DATABASE dbname to disk='c:\dbname.bak' with INIT
Thanks
Hari
MCDBA
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uYtrikJTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> What kind of backup are you doing? If you don't use the INIT option the
> current backup will append to the existing ones in the dump device.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "cscott" <christopher@.uncommonlaw.com> wrote in message
> news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
> > Hi there. Running a Sql 2000 installation with latest service pack on
> > Windows 2000 server. My database dump to disk backup keeps increasing
> > by about 1 meg per day. The database itself is increasing by a small
> > percentage of that. In fact the dump is now about the same size as the
> > database. What's going on? Thanks.
>
Friday, February 17, 2012
DataBase Creation
I am developing and application which requires a database and 7 tables.
I am trying to figure out how to do the installation of this database and
what approach to installing a database is appropriate, as I have never
installed an application which requires the installation of database.
I was hoping someone could point me in the direction of the "appropriate
way to do this".
Should I create the script files for the database and tables ind then
execute that SQL to build the tables, possibly prompting the user for the
location as to where the tables should be installed?
Should I do a Database backup of an "empty" database structure (database
and tables) and then do some sort of restore of the database through my
application?
What is the appropriate technique to this type of installation?
Thanks in advance for your assistance!!!!!!If you want to supply your database with some pre-defined values are some
data records, sending a backup of the database might be a good option, since
all the users have to do is to restore the database at their end using
Enterprise Manager. If you want to avoid this hazzle, you can create the
scripts for the database along with table creation and data insertion
scripts and then have it execute. The "pubs" database of SQL Server is done
in this way. If you have SQL Server installed, you can see how this script
is structured, by navigating to: C:\Program Files\Microsoft SQL
Server\MSSQL\Install\instpubs.sql
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
news:Xns946EDAE2F587DJimHeaveyhotmailcom@.207.46.248.16...
> I am developing and application which requires a database and 7 tables.
> I am trying to figure out how to do the installation of this database and
> what approach to installing a database is appropriate, as I have never
> installed an application which requires the installation of database.
> I was hoping someone could point me in the direction of the "appropriate
> way to do this".
> Should I create the script files for the database and tables ind then
> execute that SQL to build the tables, possibly prompting the user for the
> location as to where the tables should be installed?
> Should I do a Database backup of an "empty" database structure (database
> and tables) and then do some sort of restore of the database through my
> application?
> What is the appropriate technique to this type of installation?
>
> Thanks in advance for your assistance!!!!!!|||I have seen companies do both... The problem I have with delivering mdf and
ldf files or backup files, is that
1. These files may have a limited life span, since MS could change the
file format
2. You would have pre-selected collation and initial file sizes and
layout
I prefer using scripts, then you are covered... Then high end user can then
create the database in any way they see fit and run your scripts to setup
the tables and data...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
news:Xns946EDAE2F587DJimHeaveyhotmailcom@.207.46.248.16...
> I am developing and application which requires a database and 7 tables.
> I am trying to figure out how to do the installation of this database and
> what approach to installing a database is appropriate, as I have never
> installed an application which requires the installation of database.
> I was hoping someone could point me in the direction of the "appropriate
> way to do this".
> Should I create the script files for the database and tables ind then
> execute that SQL to build the tables, possibly prompting the user for the
> location as to where the tables should be installed?
> Should I do a Database backup of an "empty" database structure (database
> and tables) and then do some sort of restore of the database through my
> application?
> What is the appropriate technique to this type of installation?
>
> Thanks in advance for your assistance!!!!!!|||One of our 10 commandments here is "Always script".
We script table creation - index creation - table format
changes - everything. We script BULK INSERT's from .txt
files to pre-fill tables with data. We script the
dropping and re-creation of stored procedures.
We script the "GRANT" of access/rights/etc.
If someone makes a change in Enterprise Manager we would
never know to get it into production. That would be a
disaster.
Been working very well for us. We are simultaneously
developing three large enterprise apps - migrating from
mainframes (VAX's) that have been in use since 1980's
>--Original Message--
>If you want to supply your database with some pre-
defined values are some
>data records, sending a backup of the database might be
a good option, since
>all the users have to do is to restore the database at
their end using
>Enterprise Manager. If you want to avoid this hazzle,
you can create the
>scripts for the database along with table creation and
data insertion
>scripts and then have it execute. The "pubs" database of
SQL Server is done
>in this way. If you have SQL Server installed, you can
see how this script
>is structured, by navigating to: C:\Program
Files\Microsoft SQL
>Server\MSSQL\Install\instpubs.sql
>--
>HTH,
>SriSamp
>Please reply to the whole group only!
>http://www32.brinkster.com/srisamp
>"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
>news:Xns946EDAE2F587DJimHeaveyhotmailcom@.207.46.248.16...
>> I am developing and application which requires a
database and 7 tables.
>> I am trying to figure out how to do the installation
of this database and
>> what approach to installing a database is appropriate,
as I have never
>> installed an application which requires the
installation of database.
>> I was hoping someone could point me in the direction
of the "appropriate
>> way to do this".
>> Should I create the script files for the database and
tables ind then
>> execute that SQL to build the tables, possibly
prompting the user for the
>> location as to where the tables should be installed?
>> Should I do a Database backup of an "empty" database
structure (database
>> and tables) and then do some sort of restore of the
database through my
>> application?
>> What is the appropriate technique to this type of
installation?
>>
>> Thanks in advance for your assistance!!!!!!
>
>.
>
I am trying to figure out how to do the installation of this database and
what approach to installing a database is appropriate, as I have never
installed an application which requires the installation of database.
I was hoping someone could point me in the direction of the "appropriate
way to do this".
Should I create the script files for the database and tables ind then
execute that SQL to build the tables, possibly prompting the user for the
location as to where the tables should be installed?
Should I do a Database backup of an "empty" database structure (database
and tables) and then do some sort of restore of the database through my
application?
What is the appropriate technique to this type of installation?
Thanks in advance for your assistance!!!!!!If you want to supply your database with some pre-defined values are some
data records, sending a backup of the database might be a good option, since
all the users have to do is to restore the database at their end using
Enterprise Manager. If you want to avoid this hazzle, you can create the
scripts for the database along with table creation and data insertion
scripts and then have it execute. The "pubs" database of SQL Server is done
in this way. If you have SQL Server installed, you can see how this script
is structured, by navigating to: C:\Program Files\Microsoft SQL
Server\MSSQL\Install\instpubs.sql
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
news:Xns946EDAE2F587DJimHeaveyhotmailcom@.207.46.248.16...
> I am developing and application which requires a database and 7 tables.
> I am trying to figure out how to do the installation of this database and
> what approach to installing a database is appropriate, as I have never
> installed an application which requires the installation of database.
> I was hoping someone could point me in the direction of the "appropriate
> way to do this".
> Should I create the script files for the database and tables ind then
> execute that SQL to build the tables, possibly prompting the user for the
> location as to where the tables should be installed?
> Should I do a Database backup of an "empty" database structure (database
> and tables) and then do some sort of restore of the database through my
> application?
> What is the appropriate technique to this type of installation?
>
> Thanks in advance for your assistance!!!!!!|||I have seen companies do both... The problem I have with delivering mdf and
ldf files or backup files, is that
1. These files may have a limited life span, since MS could change the
file format
2. You would have pre-selected collation and initial file sizes and
layout
I prefer using scripts, then you are covered... Then high end user can then
create the database in any way they see fit and run your scripts to setup
the tables and data...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
news:Xns946EDAE2F587DJimHeaveyhotmailcom@.207.46.248.16...
> I am developing and application which requires a database and 7 tables.
> I am trying to figure out how to do the installation of this database and
> what approach to installing a database is appropriate, as I have never
> installed an application which requires the installation of database.
> I was hoping someone could point me in the direction of the "appropriate
> way to do this".
> Should I create the script files for the database and tables ind then
> execute that SQL to build the tables, possibly prompting the user for the
> location as to where the tables should be installed?
> Should I do a Database backup of an "empty" database structure (database
> and tables) and then do some sort of restore of the database through my
> application?
> What is the appropriate technique to this type of installation?
>
> Thanks in advance for your assistance!!!!!!|||One of our 10 commandments here is "Always script".
We script table creation - index creation - table format
changes - everything. We script BULK INSERT's from .txt
files to pre-fill tables with data. We script the
dropping and re-creation of stored procedures.
We script the "GRANT" of access/rights/etc.
If someone makes a change in Enterprise Manager we would
never know to get it into production. That would be a
disaster.
Been working very well for us. We are simultaneously
developing three large enterprise apps - migrating from
mainframes (VAX's) that have been in use since 1980's
>--Original Message--
>If you want to supply your database with some pre-
defined values are some
>data records, sending a backup of the database might be
a good option, since
>all the users have to do is to restore the database at
their end using
>Enterprise Manager. If you want to avoid this hazzle,
you can create the
>scripts for the database along with table creation and
data insertion
>scripts and then have it execute. The "pubs" database of
SQL Server is done
>in this way. If you have SQL Server installed, you can
see how this script
>is structured, by navigating to: C:\Program
Files\Microsoft SQL
>Server\MSSQL\Install\instpubs.sql
>--
>HTH,
>SriSamp
>Please reply to the whole group only!
>http://www32.brinkster.com/srisamp
>"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
>news:Xns946EDAE2F587DJimHeaveyhotmailcom@.207.46.248.16...
>> I am developing and application which requires a
database and 7 tables.
>> I am trying to figure out how to do the installation
of this database and
>> what approach to installing a database is appropriate,
as I have never
>> installed an application which requires the
installation of database.
>> I was hoping someone could point me in the direction
of the "appropriate
>> way to do this".
>> Should I create the script files for the database and
tables ind then
>> execute that SQL to build the tables, possibly
prompting the user for the
>> location as to where the tables should be installed?
>> Should I do a Database backup of an "empty" database
structure (database
>> and tables) and then do some sort of restore of the
database through my
>> application?
>> What is the appropriate technique to this type of
installation?
>>
>> Thanks in advance for your assistance!!!!!!
>
>.
>
DataBase Creation
I am developing and application which requires a database and 7 tables.
I am trying to figure out how to do the installation of this database and
what approach to installing a database is appropriate, as I have never
installed an application which requires the installation of database.
I was hoping someone could point me in the direction of the "appropriate
way to do this".
Should I create the script files for the database and tables ind then
execute that SQL to build the tables, possibly prompting the user for the
location as to where the tables should be installed?
Should I do a Database backup of an "empty" database structure (database
and tables) and then do some sort of restore of the database through my
application?
What is the appropriate technique to this type of installation?
Thanks in advance for your assistance!!!!!!If you want to supply your database with some pre-defined values are some
data records, sending a backup of the database might be a good option, since
all the users have to do is to restore the database at their end using
Enterprise Manager. If you want to avoid this hazzle, you can create the
scripts for the database along with table creation and data insertion
scripts and then have it execute. The "pubs" database of SQL Server is done
in this way. If you have SQL Server installed, you can see how this script
is structured, by navigating to: C:\Program Files\Microsoft SQL
Server\MSSQL\Install\instpubs.sql
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
news:Xns946EDAE2F587DJimHeaveyhotmailcom
@.207.46.248.16...
ldf files or backup files, is that
1. These files may have a limited life span, since MS could change the
file format
2. You would have pre-selected collation and initial file sizes and
layout
I prefer using scripts, then you are covered... Then high end user can then
create the database in any way they see fit and run your scripts to setup
the tables and data...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
news:Xns946EDAE2F587DJimHeaveyhotmailcom
@.207.46.248.16...
We script table creation - index creation - table format
changes - everything. We script BULK INSERT's from .txt
files to pre-fill tables with data. We script the
dropping and re-creation of stored procedures.
We script the "GRANT" of access/rights/etc.
If someone makes a change in Enterprise Manager we would
never know to get it into production. That would be a
disaster.
Been working very well for us. We are simultaneously
developing three large enterprise apps - migrating from
mainframes (VAX's) that have been in use since 1980's
defined values are some
a good option, since
their end using
you can create the
data insertion
SQL Server is done
see how this script
Files\Microsoft SQL
I am trying to figure out how to do the installation of this database and
what approach to installing a database is appropriate, as I have never
installed an application which requires the installation of database.
I was hoping someone could point me in the direction of the "appropriate
way to do this".
Should I create the script files for the database and tables ind then
execute that SQL to build the tables, possibly prompting the user for the
location as to where the tables should be installed?
Should I do a Database backup of an "empty" database structure (database
and tables) and then do some sort of restore of the database through my
application?
What is the appropriate technique to this type of installation?
Thanks in advance for your assistance!!!!!!If you want to supply your database with some pre-defined values are some
data records, sending a backup of the database might be a good option, since
all the users have to do is to restore the database at their end using
Enterprise Manager. If you want to avoid this hazzle, you can create the
scripts for the database along with table creation and data insertion
scripts and then have it execute. The "pubs" database of SQL Server is done
in this way. If you have SQL Server installed, you can see how this script
is structured, by navigating to: C:\Program Files\Microsoft SQL
Server\MSSQL\Install\instpubs.sql
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
news:Xns946EDAE2F587DJimHeaveyhotmailcom
@.207.46.248.16...
quote:|||I have seen companies do both... The problem I have with delivering mdf and
> I am developing and application which requires a database and 7 tables.
> I am trying to figure out how to do the installation of this database and
> what approach to installing a database is appropriate, as I have never
> installed an application which requires the installation of database.
> I was hoping someone could point me in the direction of the "appropriate
> way to do this".
> Should I create the script files for the database and tables ind then
> execute that SQL to build the tables, possibly prompting the user for the
> location as to where the tables should be installed?
> Should I do a Database backup of an "empty" database structure (database
> and tables) and then do some sort of restore of the database through my
> application?
> What is the appropriate technique to this type of installation?
>
> Thanks in advance for your assistance!!!!!!
ldf files or backup files, is that
1. These files may have a limited life span, since MS could change the
file format
2. You would have pre-selected collation and initial file sizes and
layout
I prefer using scripts, then you are covered... Then high end user can then
create the database in any way they see fit and run your scripts to setup
the tables and data...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
news:Xns946EDAE2F587DJimHeaveyhotmailcom
@.207.46.248.16...
quote:|||One of our 10 commandments here is "Always script".
> I am developing and application which requires a database and 7 tables.
> I am trying to figure out how to do the installation of this database and
> what approach to installing a database is appropriate, as I have never
> installed an application which requires the installation of database.
> I was hoping someone could point me in the direction of the "appropriate
> way to do this".
> Should I create the script files for the database and tables ind then
> execute that SQL to build the tables, possibly prompting the user for the
> location as to where the tables should be installed?
> Should I do a Database backup of an "empty" database structure (database
> and tables) and then do some sort of restore of the database through my
> application?
> What is the appropriate technique to this type of installation?
>
> Thanks in advance for your assistance!!!!!!
We script table creation - index creation - table format
changes - everything. We script BULK INSERT's from .txt
files to pre-fill tables with data. We script the
dropping and re-creation of stored procedures.
We script the "GRANT" of access/rights/etc.
If someone makes a change in Enterprise Manager we would
never know to get it into production. That would be a
disaster.
Been working very well for us. We are simultaneously
developing three large enterprise apps - migrating from
mainframes (VAX's) that have been in use since 1980's
quote:
>--Original Message--
>If you want to supply your database with some pre-
defined values are some
quote:
>data records, sending a backup of the database might be
a good option, since
quote:
>all the users have to do is to restore the database at
their end using
quote:
>Enterprise Manager. If you want to avoid this hazzle,
you can create the
quote:
>scripts for the database along with table creation and
data insertion
quote:
>scripts and then have it execute. The "pubs" database of
SQL Server is done
quote:
>in this way. If you have SQL Server installed, you can
see how this script
quote:
>is structured, by navigating to: C:\Program
Files\Microsoft SQL
quote:
>Server\MSSQL\Install\instpubs.sql
>--
>HTH,
>SriSamp
>Please reply to the whole group only!
>http://www32.brinkster.com/srisamp
>"Jim Heavey" <JimHeavey@.nospam.com> wrote in message
> news:Xns946EDAE2F587DJimHeaveyhotmailcom
@.207.46.248.16...
database and 7 tables.[QUOTE]
of this database and[QUOTE]
as I have never[QUOTE]
installation of database.[QUOTE]
of the "appropriate[QUOTE]
tables ind then[QUOTE]
prompting the user for the[QUOTE]
structure (database[QUOTE]
database through my[QUOTE]
installation?[QUOTE]
>
>.
>
Tuesday, February 14, 2012
Database Create error
I am trying to create a database in my application's installation folder and it will not create because the folder does not have the permissions for the service account added as full control. I can't figure out how to get the service account name in my program so that I can add it to the folder permissions. The service name is a long name and has the computer name and the SQL server name included in it. For example: SQLServer2005MSSQLUser$<Ccmputer Name>$SQLEXPRESS. I'm assuming this pattern is always followed. I guess my question is can I query the database for this information and then use it to add the appropriate permissions to my application's install folder?
The pattern for the service account names you described is correct for the default SQL Express settings. I would like to generalize this pattern for all the 3 groups SQL Server 2005 may create on the computer:
* Sql Server group:
SQLServer2005MSSQLUser$<<machine_name>>$<<instance_name>>
* Agent group:
SQLServer2005SQLAgentUser$<<machine_name>>$<<instance_name>>
* Full text search group:
SQLServer2005MSFTEUser$<<machine_name>>$<<instance_name>>
You can use these patterns directly by inserting the machine name and SQL Server instance name (the default instance name is called MSSQLSERVER ).
An alternative method would be to use the following query:
SELECT name, sid FROM sys.server_principals WHERE name like '%SQLServer2005MSSQLUser%'
Be aware that a system administrator may drop this server principal from the server, invalidating this query to obtain the Windows service group.
I hope this information was useful. Let us know if you have any further questions or feedback.
Thanks a lot,
Raul Garcia
SDE/T
SQL Server Engine
Subscribe to:
Posts (Atom)