Moving C2 Audits

I'm not seeing or finding how to move the location of the C2 Audit files. I
used the pretty standard script to enable C2 Auditing:
EXEC sp_configure 'show advanced option', 1
RECONFIGURE WITH OVERRIDE
EXEC sp_configure 'c2 audit mode', 1
RECONFIGURE WITH OVERRIDE
However, it would be nice if I could move them from the C:\ drive to a
folder already being backed up since we need these audit trails for at least
one year (Government thing). Any ideas? I'll keep looking, but I know we
get pretty quick responses in here also!
Thanks
AllenSorry , what is C2 Audit files ?
"A McGuire" <allen.mcguire@.gmail.com.invalid> wrote in message
news:e4aqFxLtGHA.2260@.TK2MSFTNGP03.phx.gbl...
> I'm not seeing or finding how to move the location of the C2 Audit files.
> I used the pretty standard script to enable C2 Auditing:
> EXEC sp_configure 'show advanced option', 1
> RECONFIGURE WITH OVERRIDE
> EXEC sp_configure 'c2 audit mode', 1
> RECONFIGURE WITH OVERRIDE
> However, it would be nice if I could move them from the C:\ drive to a
> folder already being backed up since we need these audit trails for at
> least one year (Government thing). Any ideas? I'll keep looking, but I
> know we get pretty quick responses in here also!
> Thanks
> Allen
>|||Hi,
By default SQL Server logs the C2 trace into data folder which you mentioned
during SQL Server installation.
The file can be copied to a different location by writing a batch file and
scheduled using SQL Server Agent every 1 hour.
Thanks
Hari
SQL Server MVP
"A McGuire" <allen.mcguire@.gmail.com.invalid> wrote in message
news:e4aqFxLtGHA.2260@.TK2MSFTNGP03.phx.gbl...
> I'm not seeing or finding how to move the location of the C2 Audit files.
> I used the pretty standard script to enable C2 Auditing:
> EXEC sp_configure 'show advanced option', 1
> RECONFIGURE WITH OVERRIDE
> EXEC sp_configure 'c2 audit mode', 1
> RECONFIGURE WITH OVERRIDE
> However, it would be nice if I could move them from the C:\ drive to a
> folder already being backed up since we need these audit trails for at
> least one year (Government thing). Any ideas? I'll keep looking, but I
> know we get pretty quick responses in here also!
> Thanks
> Allen
>|||C2 audits are predefined audits you can run to trace specific events on a
SQL Server. It is compliant with Government auditing policies and
procedures.
http://www.microsoft.com/technet/se...r/sql2kaud.mspx
A Google search will produce more results for you.
In SQL 2005 it is a standard checkbox you can turn on by checking the
Properties of a Server, then clicking on Security. In SQL 2000, you have to
run the script I show below.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uX%23l0rStGHA.4748@.TK2MSFTNGP03.phx.gbl...
> Sorry , what is C2 Audit files ?
>
>
> "A McGuire" <allen.mcguire@.gmail.com.invalid> wrote in message
> news:e4aqFxLtGHA.2260@.TK2MSFTNGP03.phx.gbl...
>|||Yeah, not really what I had in mind though. Just like I can change the
location of my data files and log files, I want my traces to go to another
location as well. This should be something we can run a script to configure
IMHO. I don't want to write batch files for each of my 70 SQL Servers ;-)
The default size of an audit file is 200 MB, and with C2 auditing, that will
be reached daily for some servers - no way around it. Furthermore, you
can't copy an active trace file, so I would have to continually check back
to see if the thing is 200 MB yet, then copy it to another location on the
same computer - awaiting pickup by our backup system. That is way too much
disk activity for me.
I would like to see the ability to write them directly to another location -
other than the original /data folder.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uY92JSUtGHA.4968@.TK2MSFTNGP03.phx.gbl...
> Hi,
> By default SQL Server logs the C2 trace into data folder which you
> mentioned during SQL Server installation.
> The file can be copied to a different location by writing a batch file and
> scheduled using SQL Server Agent every 1 hour.
> Thanks
> Hari
> SQL Server MVP
>
> "A McGuire" <allen.mcguire@.gmail.com.invalid> wrote in message
> news:e4aqFxLtGHA.2260@.TK2MSFTNGP03.phx.gbl...
>|||Ok - I've been told that audits get written to the default data directory.
However, we have dedicated drives for log and data files (E: and F:, for
example). What I had to do to get the C2 audits (trace files) to write to
our data directory was:
1) launch Enterprise Manager
2) right-click and Properties
3) Database Settings tab
4) Change 'default data directory' to F:\<location>
5) Stop and restart the services
Good to go. The traces will begin writing to the drive you specified as
your default data directory.
"A McGuire" <allen.mcguire@.gmail.com.invalid> wrote in message
news:e4aqFxLtGHA.2260@.TK2MSFTNGP03.phx.gbl...
> I'm not seeing or finding how to move the location of the C2 Audit files.
> I used the pretty standard script to enable C2 Auditing:
> EXEC sp_configure 'show advanced option', 1
> RECONFIGURE WITH OVERRIDE
> EXEC sp_configure 'c2 audit mode', 1
> RECONFIGURE WITH OVERRIDE
> However, it would be nice if I could move them from the C:\ drive to a
> folder already being backed up since we need these audit trails for at
> least one year (Government thing). Any ideas? I'll keep looking, but I
> know we get pretty quick responses in here also!
> Thanks
> Allen
>sql

Moved database to new server...before creating logins

I feel like an idiot for this.
We are moving our SQL Server database (2000 Standard) to a new server
(also 2000 standard--don't worry, we've got a separate license for it).
What I did was backup the database on the old server and restore it to
the new server for testing our software application.
Only problem is, I didn't create the users beforehand, so now I can't
log into the new server with the login. It says I can't access my
default database.
WIthout dropping the database, is there a way I can fix this? It would
be easy enough to drop and re-restore the database, but if there is a
shorter way that would also work just as well, please enlighten me.Sure there are several articles here that cover this and more. But at the
least you can just create a new Login and then use sp_change_users_login to
map the user to the login.
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://www.databasejournal.com/feat...cle.php/3379901 Moving
system DB's
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"Brent White" <bwhite@.badgersportswear.com> wrote in message
news:1131724756.657385.127960@.f14g2000cwb.googlegroups.com...
>I feel like an idiot for this.
> We are moving our SQL Server database (2000 Standard) to a new server
> (also 2000 standard--don't worry, we've got a separate license for it).
> What I did was backup the database on the old server and restore it to
> the new server for testing our software application.
> Only problem is, I didn't create the users beforehand, so now I can't
> log into the new server with the login. It says I can't access my
> default database.
> WIthout dropping the database, is there a way I can fix this? It would
> be easy enough to drop and re-restore the database, but if there is a
> shorter way that would also work just as well, please enlighten me.
>|||Hi,
i found a good article by Mr. Vyas ,a very famous SQL Professional :
http://vyaskn.tripod.com/moving_sql_server.htm
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Brent White" wrote:

> I feel like an idiot for this.
> We are moving our SQL Server database (2000 Standard) to a new server
> (also 2000 standard--don't worry, we've got a separate license for it).
> What I did was backup the database on the old server and restore it to
> the new server for testing our software application.
> Only problem is, I didn't create the users beforehand, so now I can't
> log into the new server with the login. It says I can't access my
> default database.
> WIthout dropping the database, is there a way I can fix this? It would
> be easy enough to drop and re-restore the database, but if there is a
> shorter way that would also work just as well, please enlighten me.
>

move/copy database objects from SQL Server Express to SQL Server Standard?

Can anyone refer me to good 'recipes' or sources of information on this
topic??

I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.

Thank you, TomHi Tom

If the objects are on source code control you may just want to check out the
scripts and run them through SQLCMD.

If you want the whole database then you can either use backup/restore or
sp_detach_db/sp_attach_db, failing that you could use the import/export
wizard, If SQLExpress is does not allow external connections then you will
need to push it (export) from the SQLExpress machine.

Check out http://support.microsoft.com/kb/314546
John

"tlyczko" <tlyczko@.gmail.comwrote in message
news:1157561832.911996.148780@.b28g2000cwb.googlegr oups.com...

Quote:

Originally Posted by

Can anyone refer me to good 'recipes' or sources of information on this
topic??
>
I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.
>
Thank you, Tom
>

|||I should have said SS 2005 Developer, not Express, I am installing SS
2005 Dev to my workstation here.

But everything you said should work, I just have to learn how!!!!!!!!

I will read the KB article, I suppose I could learn SSIS for just
tables or queries etc., or even just re-create the queries on the SS
dev box.

Thanks a lot for answering!!

:) tom

John Bell wrote:

Quote:

Originally Posted by

Hi Tom
>
If the objects are on source code control you may just want to check out the
scripts and run them through SQLCMD.
>
If you want the whole database then you can either use backup/restore or
sp_detach_db/sp_attach_db, failing that you could use the import/export
wizard, If SQLExpress is does not allow external connections then you will
need to push it (export) from the SQLExpress machine.
>
Check out http://support.microsoft.com/kb/314546
>
John
>
>
"tlyczko" <tlyczko@.gmail.comwrote in message
news:1157561832.911996.148780@.b28g2000cwb.googlegr oups.com...

Quote:

Originally Posted by

Can anyone refer me to good 'recipes' or sources of information on this
topic??

I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.

Thank you, Tom

|||tlyczko wrote:

Quote:

Originally Posted by

I should have said SS 2005 Developer, not Express, I am installing SS
2005 Dev to my workstation here.

I found this link, I can't remember where:

http://blogs.msdn.com/euanga/archiv.../18/668916.aspx
HTH tom

move/copy database items from SS 2005 Express to SS 2005 Standard?

Can anyone refer me to good 'recipes' or sources of information on this
topic'
I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.
Thank you, TomYou can:
1. Using SSMS, script out the code to re-create the table, views, queries,
etc.
2. Using SSIS, Transfer the entire database, schema and/or data
3. Pull your script files from source control, thereby making sure that
nothing is moved to the production server except items that 'should' be
moved to production. (You are using source control, aren't you?)
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
> Can anyone refer me to good 'recipes' or sources of information on this
> topic'
> I have Visual Studio Tools for Office, which installs SS 2005 Express
> locally to my XP box, and I want to develop in SS 2005, then copy the
> tables or queries or reports etc. to a SS 2005 Standard server.
> Thank you, Tom
>|||I don't know anything yet about source control...do you mean Visual
SourceSafe'
I tried looking around a few months ago for decent documentation,
how-to, etc. about VSS 2005, and I didn't find anything, it was not
terribly intuitive either...
I don't always need to transfer the entire database either, I might
only have to transfer a query, for example.
Or I might have to refresh the tables in my dev workstation from the
main server...
Thank you,
Tom
Arnie Rowland wrote:[vbcol=seagreen]
> You can:
> 1. Using SSMS, script out the code to re-create the table, views, queries,
> etc.
> 2. Using SSIS, Transfer the entire database, schema and/or data
> 3. Pull your script files from source control, thereby making sure that
> nothing is moved to the production server except items that 'should' be
> moved to production. (You are using source control, aren't you?)
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "tlyczko" <tlyczko@.gmail.com> wrote in message
> news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...|||Visual SourceSafe is but one of many source control products, albeit one
that is included with Visual Studio.
You might find part 4 of this tutorial useful for an introductory view of
Sourcesafe.
http://msdn2.microsoft.com/en-us/library/ms167593.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157567635.523378.239270@.p79g2000cwp.googlegroups.com...
>I don't know anything yet about source control...do you mean Visual
> SourceSafe'
> I tried looking around a few months ago for decent documentation,
> how-to, etc. about VSS 2005, and I didn't find anything, it was not
> terribly intuitive either...
> I don't always need to transfer the entire database either, I might
> only have to transfer a query, for example.
> Or I might have to refresh the tables in my dev workstation from the
> main server...
> Thank you,
> Tom
> Arnie Rowland wrote:
>|||Visual SourceSafe didn't come with our Visual Studio...
Thank you for sending the link, I think I remember that Perforce makes
a single-user version that I could use...I'll check their website.
Thank you, Tom

> Most good judgment comes from experience.
> Most experience comes from bad judgment.
Agreed.
Thank you, Tom

move/copy database items from SS 2005 Express to SS 2005 Standard?

Can anyone refer me to good 'recipes' or sources of information on this
topic'
I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.
Thank you, TomYou can:
1. Using SSMS, script out the code to re-create the table, views, queries,
etc.
2. Using SSIS, Transfer the entire database, schema and/or data
3. Pull your script files from source control, thereby making sure that
nothing is moved to the production server except items that 'should' be
moved to production. (You are using source control, aren't you?)
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
> Can anyone refer me to good 'recipes' or sources of information on this
> topic'
> I have Visual Studio Tools for Office, which installs SS 2005 Express
> locally to my XP box, and I want to develop in SS 2005, then copy the
> tables or queries or reports etc. to a SS 2005 Standard server.
> Thank you, Tom
>|||I don't know anything yet about source control...do you mean Visual
SourceSafe'
I tried looking around a few months ago for decent documentation,
how-to, etc. about VSS 2005, and I didn't find anything, it was not
terribly intuitive either...
I don't always need to transfer the entire database either, I might
only have to transfer a query, for example.
Or I might have to refresh the tables in my dev workstation from the
main server...
Thank you,
Tom
Arnie Rowland wrote:
> You can:
> 1. Using SSMS, script out the code to re-create the table, views, queries,
> etc.
> 2. Using SSIS, Transfer the entire database, schema and/or data
> 3. Pull your script files from source control, thereby making sure that
> nothing is moved to the production server except items that 'should' be
> moved to production. (You are using source control, aren't you?)
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "tlyczko" <tlyczko@.gmail.com> wrote in message
> news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
> > Can anyone refer me to good 'recipes' or sources of information on this
> > topic'
> >
> > I have Visual Studio Tools for Office, which installs SS 2005 Express
> > locally to my XP box, and I want to develop in SS 2005, then copy the
> > tables or queries or reports etc. to a SS 2005 Standard server.
> >
> > Thank you, Tom
> >|||Visual SourceSafe is but one of many source control products, albeit one
that is included with Visual Studio.
You might find part 4 of this tutorial useful for an introductory view of
Sourcesafe.
http://msdn2.microsoft.com/en-us/library/ms167593.aspx
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157567635.523378.239270@.p79g2000cwp.googlegroups.com...
>I don't know anything yet about source control...do you mean Visual
> SourceSafe'
> I tried looking around a few months ago for decent documentation,
> how-to, etc. about VSS 2005, and I didn't find anything, it was not
> terribly intuitive either...
> I don't always need to transfer the entire database either, I might
> only have to transfer a query, for example.
> Or I might have to refresh the tables in my dev workstation from the
> main server...
> Thank you,
> Tom
> Arnie Rowland wrote:
>> You can:
>> 1. Using SSMS, script out the code to re-create the table, views,
>> queries,
>> etc.
>> 2. Using SSIS, Transfer the entire database, schema and/or data
>> 3. Pull your script files from source control, thereby making sure that
>> nothing is moved to the production server except items that 'should' be
>> moved to production. (You are using source control, aren't you?)
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "tlyczko" <tlyczko@.gmail.com> wrote in message
>> news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
>> > Can anyone refer me to good 'recipes' or sources of information on this
>> > topic'
>> >
>> > I have Visual Studio Tools for Office, which installs SS 2005 Express
>> > locally to my XP box, and I want to develop in SS 2005, then copy the
>> > tables or queries or reports etc. to a SS 2005 Standard server.
>> >
>> > Thank you, Tom
>> >
>|||Visual SourceSafe didn't come with our Visual Studio...
Thank you for sending the link, I think I remember that Perforce makes
a single-user version that I could use...I'll check their website.
Thank you, Tom
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
Agreed.
Thank you, Tom

Move database to another partition

I have recently installed SQL Server 2005 Standard Edition on a server with 2
partitions. I then installed Sharepoint which installed a database and put it
in the default location on the c: partition. I would like to move this to d:.
I have tried to do this by detaching and attaching, and also by backing and
restoring, but both the attach and the backup dialog boxes only allow me to
browse the c: drive. Is this a feature of Standard Edition? Do I need to use
Enterprise? Or is there a configuration setting I can change somewhere?
TIA25degc wrote:
> I have recently installed SQL Server 2005 Standard Edition on a server with 2
> partitions. I then installed Sharepoint which installed a database and put it
> in the default location on the c: partition. I would like to move this to d:.
> I have tried to do this by detaching and attaching, and also by backing and
> restoring, but both the attach and the backup dialog boxes only allow me to
> browse the c: drive. Is this a feature of Standard Edition? Do I need to use
> Enterprise? Or is there a configuration setting I can change somewhere?
> TIA
Not sure why you can't browse your other drive, but a workaround would
be to not use the GUI to do this. Instead use the SQL commands to
detach/reattach the database:
EXEC sp_detach_db DBname, 'true'
Copy the files from C: to D:
EXEC sp_attach_db @.dbname = 'DBName', @.filename1 = 'D:\MDFFile',
@.filename2 = 'D:\LDFFile'|||Thanks. This highlighted an issue with the d: drive. Although
readable/writable through Windows I decided to reformat, and now it is
working fine.
Thanks for your help.
"Tracy McKibben" wrote:
> 25degc wrote:
> > I have recently installed SQL Server 2005 Standard Edition on a server with 2
> > partitions. I then installed Sharepoint which installed a database and put it
> > in the default location on the c: partition. I would like to move this to d:.
> > I have tried to do this by detaching and attaching, and also by backing and
> > restoring, but both the attach and the backup dialog boxes only allow me to
> > browse the c: drive. Is this a feature of Standard Edition? Do I need to use
> > Enterprise? Or is there a configuration setting I can change somewhere?
> >
> > TIA
> Not sure why you can't browse your other drive, but a workaround would
> be to not use the GUI to do this. Instead use the SQL commands to
> detach/reattach the database:
> EXEC sp_detach_db DBname, 'true'
> Copy the files from C: to D:
> EXEC sp_attach_db @.dbname = 'DBName', @.filename1 = 'D:\MDFFile',
> @.filename2 = 'D:\LDFFile'
>

Move database to another partition

25degc wrote:
> I have recently installed SQL Server 2005 Standard Edition on a server wit
h 2
> partitions. I then installed Sharepoint which installed a database and put
it
> in the default location on the c: partition. I would like to move this to
d:.
> I have tried to do this by detaching and attaching, and also by backing an
d
> restoring, but both the attach and the backup dialog boxes only allow me t
o
> browse the c: drive. Is this a feature of Standard Edition? Do I need to u
se
> Enterprise? Or is there a configuration setting I can change somewhere?
> TIA
Not sure why you can't browse your other drive, but a workaround would
be to not use the GUI to do this. Instead use the SQL commands to
detach/reattach the database:
EXEC sp_detach_db DBname, 'true'
Copy the files from C: to D:
EXEC sp_attach_db @.dbname = 'DBName', @.filename1 = 'D:\MDFFile',
@.filename2 = 'D:\LDFFile'I have recently installed SQL Server 2005 Standard Edition on a server with
2
partitions. I then installed Sharepoint which installed a database and put i
t
in the default location on the c: partition. I would like to move this to d:
.
I have tried to do this by detaching and attaching, and also by backing and
restoring, but both the attach and the backup dialog boxes only allow me to
browse the c: drive. Is this a feature of Standard Edition? Do I need to use
Enterprise? Or is there a configuration setting I can change somewhere?
TIA|||25degc wrote:
> I have recently installed SQL Server 2005 Standard Edition on a server wit
h 2
> partitions. I then installed Sharepoint which installed a database and put
it
> in the default location on the c: partition. I would like to move this to
d:.
> I have tried to do this by detaching and attaching, and also by backing an
d
> restoring, but both the attach and the backup dialog boxes only allow me t
o
> browse the c: drive. Is this a feature of Standard Edition? Do I need to u
se
> Enterprise? Or is there a configuration setting I can change somewhere?
> TIA
Not sure why you can't browse your other drive, but a workaround would
be to not use the GUI to do this. Instead use the SQL commands to
detach/reattach the database:
EXEC sp_detach_db DBname, 'true'
Copy the files from C: to D:
EXEC sp_attach_db @.dbname = 'DBName', @.filename1 = 'D:\MDFFile',
@.filename2 = 'D:\LDFFile'|||Thanks. This highlighted an issue with the d: drive. Although
readable/writable through Windows I decided to reformat, and now it is
working fine.
Thanks for your help.
"Tracy McKibben" wrote:

> 25degc wrote:
> Not sure why you can't browse your other drive, but a workaround would
> be to not use the GUI to do this. Instead use the SQL commands to
> detach/reattach the database:
> EXEC sp_detach_db DBname, 'true'
> Copy the files from C: to D:
> EXEC sp_attach_db @.dbname = 'DBName', @.filename1 = 'D:\MDFFile',
> @.filename2 = 'D:\LDFFile'
>|||Thanks. This highlighted an issue with the d: drive. Although
readable/writable through Windows I decided to reformat, and now it is
working fine.
Thanks for your help.
"Tracy McKibben" wrote:

> 25degc wrote:
> Not sure why you can't browse your other drive, but a workaround would
> be to not use the GUI to do this. Instead use the SQL commands to
> detach/reattach the database:
> EXEC sp_detach_db DBname, 'true'
> Copy the files from C: to D:
> EXEC sp_attach_db @.dbname = 'DBName', @.filename1 = 'D:\MDFFile',
> @.filename2 = 'D:\LDFFile'
>

Move Database From Standard To Express

Our company uses MS SQL 2005 Standard for various databases. I've got the
Express Edition installed at home for doing work on the databases after hours.
Is it possible to copy/export the database from the Standard Edition to the
Express Edition and back?
What happens if the database is more than 4Gb?Hi
see the link bellow
http://msdn2.microsoft.com/en-us/library/ms143393.aspx
it is not possible to do this.
What happens if the database is more than 4Gb
Server throws an error message saying that insufficient disk space or file
has reach its limit ,some thing like that.
in 2000 msde you can work around this by adding one more data file to the
file group. but i haven't tested this on sql express
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"Hiwj" <Hiwj@.discussions.microsoft.com> wrote in message
news:7DDA6F6E-BC8F-4F61-8670-FAC5C830E63F@.microsoft.com...
> Our company uses MS SQL 2005 Standard for various databases. I've got the
> Express Edition installed at home for doing work on the databases after
> hours.
> Is it possible to copy/export the database from the Standard Edition to
> the
> Express Edition and back?
> What happens if the database is more than 4Gb?
>

Move Database From Standard To Express

Our company uses MS SQL 2005 Standard for various databases. I've got the
Express Edition installed at home for doing work on the databases after hour
s.
Is it possible to copy/export the database from the Standard Edition to the
Express Edition and back?
What happens if the database is more than 4Gb?Hi
see the link bellow
http://msdn2.microsoft.com/en-us/library/ms143393.aspx
it is not possible to do this.
What happens if the database is more than 4Gb
Server throws an error message saying that insufficient disk space or file
has reach its limit ,some thing like that.
in 2000 msde you can work around this by adding one more data file to the
file group. but i haven't tested this on sql express
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"Hiwj" <Hiwj@.discussions.microsoft.com> wrote in message
news:7DDA6F6E-BC8F-4F61-8670-FAC5C830E63F@.microsoft.com...
> Our company uses MS SQL 2005 Standard for various databases. I've got the
> Express Edition installed at home for doing work on the databases after
> hours.
> Is it possible to copy/export the database from the Standard Edition to
> the
> Express Edition and back?
> What happens if the database is more than 4Gb?
>

Ms Reporting Services install

Where can I find the Reporting Service setup ?
Is it linked to a particular version of SQLServer 2000 (Standard...)
On the CD ?SQL Server 2000 Reporting Services is not a part of a SQL installation, it comes on different CD. It also comes in different edditions (Standard, Advanced, Development...).|||HI ,

To have it function properly ,you will need visual studio.net 2003