Is it possible to relocate the data and/or the log files after they have bee
n
assigned a location? Thanks everyone for your help."coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.
There are several ways of doing this.
One method is to do a backup and restore.
Look at the MOVE TO option in RESTORE in the BOL.
Rick Sawtell
MCT, MCSD, MCDBA|||yes,
1. detach and attach
2. backup and restore
Aleksandar Grbic
MCDBA, Senior Database Administrator
"coenzyme" wrote:
> Is it possible to relocate the data and/or the log files after they have b
een
> assigned a location? Thanks everyone for your help.|||You could run sp_detach_db, move the files to the new location, and then
run sp_attach_db. Another method is to backup and then restore.
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.
Showing posts with label file. Show all posts
Showing posts with label file. Show all posts
Friday, March 30, 2012
MDF and LDF file locations
Is it possible to relocate the data and/or the log files after they have been
assigned a location? Thanks everyone for your help.
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.
There are several ways of doing this.
One method is to do a backup and restore.
Look at the MOVE TO option in RESTORE in the BOL.
Rick Sawtell
MCT, MCSD, MCDBA
|||yes,
1. detach and attach
2. backup and restore
Aleksandar Grbic
MCDBA, Senior Database Administrator
"coenzyme" wrote:
> Is it possible to relocate the data and/or the log files after they have been
> assigned a location? Thanks everyone for your help.
|||You could run sp_detach_db, move the files to the new location, and then
run sp_attach_db. Another method is to backup and then restore.
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.
assigned a location? Thanks everyone for your help.
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.
There are several ways of doing this.
One method is to do a backup and restore.
Look at the MOVE TO option in RESTORE in the BOL.
Rick Sawtell
MCT, MCSD, MCDBA
|||yes,
1. detach and attach
2. backup and restore
Aleksandar Grbic
MCDBA, Senior Database Administrator
"coenzyme" wrote:
> Is it possible to relocate the data and/or the log files after they have been
> assigned a location? Thanks everyone for your help.
|||You could run sp_detach_db, move the files to the new location, and then
run sp_attach_db. Another method is to backup and then restore.
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.
MDF and LDF file locations
Is it possible to relocate the data and/or the log files after they have been
assigned a location? Thanks everyone for your help."coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.
There are several ways of doing this.
One method is to do a backup and restore.
Look at the MOVE TO option in RESTORE in the BOL.
Rick Sawtell
MCT, MCSD, MCDBA|||yes,
1. detach and attach
2. backup and restore
--
Aleksandar Grbic
MCDBA, Senior Database Administrator
"coenzyme" wrote:
> Is it possible to relocate the data and/or the log files after they have been
> assigned a location? Thanks everyone for your help.|||You could run sp_detach_db, move the files to the new location, and then
run sp_attach_db. Another method is to backup and then restore.
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.sql
assigned a location? Thanks everyone for your help."coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.
There are several ways of doing this.
One method is to do a backup and restore.
Look at the MOVE TO option in RESTORE in the BOL.
Rick Sawtell
MCT, MCSD, MCDBA|||yes,
1. detach and attach
2. backup and restore
--
Aleksandar Grbic
MCDBA, Senior Database Administrator
"coenzyme" wrote:
> Is it possible to relocate the data and/or the log files after they have been
> assigned a location? Thanks everyone for your help.|||You could run sp_detach_db, move the files to the new location, and then
run sp_attach_db. Another method is to backup and then restore.
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6827AE2A-BCDD-49BC-B98E-4B14F414D465@.microsoft.com...
> Is it possible to relocate the data and/or the log files after they have
been
> assigned a location? Thanks everyone for your help.sql
mdf and ldf file extensions
Hello All,
One of my customers created a database in SQL 2K SP3a. He gave the data
file LDF extension and log file MDF extension.
When I do sp_helpdb 'dbname', the extensions are pointing to the correct
files, meaning LDF is pointing to the data file and MDF is pointing to the
log file just as he designed.
My question is: is it just a standard suggested by Microsoft to name the
data file with MDF extension and log file with LDF and NDF extensions? Is
there going to be any repercussions later on if we name the files with wrong
extensions.
I though it was odd that SQL Server let the files be named with wrong
extensions in the first place.
Any ideas?
Thanks,
BivaThis will not confuse SQL Server. SQL Server doesn't rely
on the file name extension to determine the type of the
file or how it deals with the file. But it may be
confusing to a DBA, and wouldn't be considered best
practice from a naming convention standpoint.
If you don't like the current naming, you can detach the
database, rename the files to the conventional extensions,
and then attach the database using the renamed files.
Linchi
>--Original Message--
>Hello All,
>One of my customers created a database in SQL 2K SP3a.
He gave the data
>file LDF extension and log file MDF extension.
>When I do sp_helpdb 'dbname', the extensions are pointing
to the correct
>files, meaning LDF is pointing to the data file and MDF
is pointing to the
>log file just as he designed.
>My question is: is it just a standard suggested by
Microsoft to name the
>data file with MDF extension and log file with LDF and
NDF extensions? Is
>there going to be any repercussions later on if we name
the files with wrong
>extensions.
>I though it was odd that SQL Server let the files be
named with wrong
>extensions in the first place.
>Any ideas?
>Thanks,
>Biva
>
>.
>|||> My question is: is it just a standard suggested by Microsoft to name the
> data file with MDF extension and log file with LDF and NDF extensions?
The pedantic part of me is tugging to correct this. By default, at least.
Data files have MDF (and NDF extensions, in the case of multiple files).
Log files have LDF extensions (whether singular or multiple).
You can certainly override this behavior. I'm not certain that there are
any advantages of doing so, and I can certainly think of some drawbacks.
But there it is.
--
Aaron Bertrand
SQL Server MVP|||Hi Biva,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
You concern is if the MDF, NDF, LDF is just a suggested standard by
Microsoft and if there problem when change the extension to these files,
right?
When create a database, you should set a filename of the data, log, etc.
These fine name and extension should be specified (they are 'os_file_name'
when you refer it to 'create database' in BOL, SQL Server Books Online).
Although 'os_file_name' can be any valid operating system file name, the
name more clearly reflects the purpose of the file if you use the following
recommended extensions.
You can create a database like this:
USE master
GO
CREATE DATABASE Sales
ON
( NAME = Sales_dat,
FILENAME = 'c:\program files\microsoft sql
server\mssql\data\saledat.mdfx',
SIZE = 10,
MAXSIZE = 50,
FILEGROWTH = 5 )
LOG ON
( NAME = 'Sales_log',
FILENAME = 'c:\program files\microsoft sql
server\mssql\data\salelog.ldfx',
SIZE = 5MB,
MAXSIZE = 25MB,
FILEGROWTH = 5MB )
GO
As we know, the system table 'master' will control the user databases and
operation of SQL Server as a whole by keeping track of all information of
them. When you use:
Use master
Go
Select * from sysdatabases
You will get the fileinformation of sales with the extension you defined,
that is
'c:\program files\microsoft sql server\mssql\data\saledat.mdfx'
and you can create table or execute other operations on it.
But if you revise the extension of the file and thenuse the database again,
the SQL Server will notify you that the file is not exist although there
may be someway de recover. It is strongly suggested you to keep the
suggested file extension by Microsoft.
Hope this answered your questions. If you still have more concern about it,
please feel free to post new message here and I am ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
One of my customers created a database in SQL 2K SP3a. He gave the data
file LDF extension and log file MDF extension.
When I do sp_helpdb 'dbname', the extensions are pointing to the correct
files, meaning LDF is pointing to the data file and MDF is pointing to the
log file just as he designed.
My question is: is it just a standard suggested by Microsoft to name the
data file with MDF extension and log file with LDF and NDF extensions? Is
there going to be any repercussions later on if we name the files with wrong
extensions.
I though it was odd that SQL Server let the files be named with wrong
extensions in the first place.
Any ideas?
Thanks,
BivaThis will not confuse SQL Server. SQL Server doesn't rely
on the file name extension to determine the type of the
file or how it deals with the file. But it may be
confusing to a DBA, and wouldn't be considered best
practice from a naming convention standpoint.
If you don't like the current naming, you can detach the
database, rename the files to the conventional extensions,
and then attach the database using the renamed files.
Linchi
>--Original Message--
>Hello All,
>One of my customers created a database in SQL 2K SP3a.
He gave the data
>file LDF extension and log file MDF extension.
>When I do sp_helpdb 'dbname', the extensions are pointing
to the correct
>files, meaning LDF is pointing to the data file and MDF
is pointing to the
>log file just as he designed.
>My question is: is it just a standard suggested by
Microsoft to name the
>data file with MDF extension and log file with LDF and
NDF extensions? Is
>there going to be any repercussions later on if we name
the files with wrong
>extensions.
>I though it was odd that SQL Server let the files be
named with wrong
>extensions in the first place.
>Any ideas?
>Thanks,
>Biva
>
>.
>|||> My question is: is it just a standard suggested by Microsoft to name the
> data file with MDF extension and log file with LDF and NDF extensions?
The pedantic part of me is tugging to correct this. By default, at least.
Data files have MDF (and NDF extensions, in the case of multiple files).
Log files have LDF extensions (whether singular or multiple).
You can certainly override this behavior. I'm not certain that there are
any advantages of doing so, and I can certainly think of some drawbacks.
But there it is.
--
Aaron Bertrand
SQL Server MVP|||Hi Biva,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
You concern is if the MDF, NDF, LDF is just a suggested standard by
Microsoft and if there problem when change the extension to these files,
right?
When create a database, you should set a filename of the data, log, etc.
These fine name and extension should be specified (they are 'os_file_name'
when you refer it to 'create database' in BOL, SQL Server Books Online).
Although 'os_file_name' can be any valid operating system file name, the
name more clearly reflects the purpose of the file if you use the following
recommended extensions.
You can create a database like this:
USE master
GO
CREATE DATABASE Sales
ON
( NAME = Sales_dat,
FILENAME = 'c:\program files\microsoft sql
server\mssql\data\saledat.mdfx',
SIZE = 10,
MAXSIZE = 50,
FILEGROWTH = 5 )
LOG ON
( NAME = 'Sales_log',
FILENAME = 'c:\program files\microsoft sql
server\mssql\data\salelog.ldfx',
SIZE = 5MB,
MAXSIZE = 25MB,
FILEGROWTH = 5MB )
GO
As we know, the system table 'master' will control the user databases and
operation of SQL Server as a whole by keeping track of all information of
them. When you use:
Use master
Go
Select * from sysdatabases
You will get the fileinformation of sales with the extension you defined,
that is
'c:\program files\microsoft sql server\mssql\data\saledat.mdfx'
and you can create table or execute other operations on it.
But if you revise the extension of the file and thenuse the database again,
the SQL Server will notify you that the file is not exist although there
may be someway de recover. It is strongly suggested you to keep the
suggested file extension by Microsoft.
Hope this answered your questions. If you still have more concern about it,
please feel free to post new message here and I am ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
MDF and LDF at the same drive
Dear All,
My Database Server is using RAID 5.
I put the mdf and ldf file of my database at the same drive.
Does it affect the SQL Server Performance?
Thanks
Robert Lie
The best thing would be not to use Raid 5 due to performance.
For best overall performance, locate the database files (.mdf) and log files
(.ldf) on separate arrays in your server to isolate potentially conflicting
reads and writes. [6.5, 7.0, 2000] Updated 12-20-2004
*****
To store your database files (.mdf), the best performance is gained by
storing them using RAID 10 arrays. If this is too expensive, then RAID 5 is
the next best bet. Each RAID array (5 or 10) should have as many physical
disks in the array as the controller will support. This allows reads and
writes to be performed simultaneously on each physical drive in the array,
significantly boosting disk I/O. [6.5, 7.0, 2000] Updated 12-20-2004
From: http://www.sql-server-performance.co...rver_setup.asp
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Robert Lie" <robert.lie24@.gmail.com> schrieb im Newsbeitrag
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie
|||Hi Robert,
yes but it only becomes a problem in very large databases, the ldf (log
file) should be on a drive of its own in a perfect world and using RAID5 for
it is overkill and will slow it's performance as the log file is written to
sequentially and most other things including the mdf file are written to
randomly. Again this is only a concirn is big installations and if you have
a spare physical drive then the ldf file could be put on that.
Regards
Alex White MCDBA MCSE
http://www.intralan.co.uk
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie
|||Hi,
It is always recommended to put Data files and Log files in multiple drives,
it will be even better if you put the files in drives belongs to different
disk controllers.
This will help you to reduce the disk I/O and eventually the better
performance.
But incase if your volume pd transaction is less then you may not have any
I/O issues, inthis case you can keep both the files in same drives which
belongs to same disk controller. And monitor the Disk Queue length , all
hardware resorce usage using Perfmon.
If you find every thing is normal then you are good. See the website
http://www.sql-server-performance.com/ for more performanace monitoring and
tuning options.
Thanks
Hari
SQL server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie
My Database Server is using RAID 5.
I put the mdf and ldf file of my database at the same drive.
Does it affect the SQL Server Performance?
Thanks
Robert Lie
The best thing would be not to use Raid 5 due to performance.
For best overall performance, locate the database files (.mdf) and log files
(.ldf) on separate arrays in your server to isolate potentially conflicting
reads and writes. [6.5, 7.0, 2000] Updated 12-20-2004
*****
To store your database files (.mdf), the best performance is gained by
storing them using RAID 10 arrays. If this is too expensive, then RAID 5 is
the next best bet. Each RAID array (5 or 10) should have as many physical
disks in the array as the controller will support. This allows reads and
writes to be performed simultaneously on each physical drive in the array,
significantly boosting disk I/O. [6.5, 7.0, 2000] Updated 12-20-2004
From: http://www.sql-server-performance.co...rver_setup.asp
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Robert Lie" <robert.lie24@.gmail.com> schrieb im Newsbeitrag
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie
|||Hi Robert,
yes but it only becomes a problem in very large databases, the ldf (log
file) should be on a drive of its own in a perfect world and using RAID5 for
it is overkill and will slow it's performance as the log file is written to
sequentially and most other things including the mdf file are written to
randomly. Again this is only a concirn is big installations and if you have
a spare physical drive then the ldf file could be put on that.
Regards
Alex White MCDBA MCSE
http://www.intralan.co.uk
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie
|||Hi,
It is always recommended to put Data files and Log files in multiple drives,
it will be even better if you put the files in drives belongs to different
disk controllers.
This will help you to reduce the disk I/O and eventually the better
performance.
But incase if your volume pd transaction is less then you may not have any
I/O issues, inthis case you can keep both the files in same drives which
belongs to same disk controller. And monitor the Disk Queue length , all
hardware resorce usage using Perfmon.
If you find every thing is normal then you are good. See the website
http://www.sql-server-performance.com/ for more performanace monitoring and
tuning options.
Thanks
Hari
SQL server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie
MDF and LDF at the same drive
Dear All,
My Database Server is using RAID 5.
I put the mdf and ldf file of my database at the same drive.
Does it affect the SQL Server Performance?
Thanks
Robert LieThe best thing would be not to use Raid 5 due to performance.
For best overall performance, locate the database files (.mdf) and log files
(.ldf) on separate arrays in your server to isolate potentially conflicting
reads and writes. [6.5, 7.0, 2000] Updated 12-20-2004
*****
To store your database files (.mdf), the best performance is gained by
storing them using RAID 10 arrays. If this is too expensive, then RAID 5 is
the next best bet. Each RAID array (5 or 10) should have as many physical
disks in the array as the controller will support. This allows reads and
writes to be performed simultaneously on each physical drive in the array,
significantly boosting disk I/O. [6.5, 7.0, 2000] Updated 12-20-2004
From: http://www.sql-server-performance.com/sql_server_setup.asp
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Robert Lie" <robert.lie24@.gmail.com> schrieb im Newsbeitrag
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie|||Hi Robert,
yes but it only becomes a problem in very large databases, the ldf (log
file) should be on a drive of its own in a perfect world and using RAID5 for
it is overkill and will slow it's performance as the log file is written to
sequentially and most other things including the mdf file are written to
randomly. Again this is only a concirn is big installations and if you have
a spare physical drive then the ldf file could be put on that.
--
Regards
Alex White MCDBA MCSE
http://www.intralan.co.uk
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie|||Hi,
It is always recommended to put Data files and Log files in multiple drives,
it will be even better if you put the files in drives belongs to different
disk controllers.
This will help you to reduce the disk I/O and eventually the better
performance.
But incase if your volume pd transaction is less then you may not have any
I/O issues, inthis case you can keep both the files in same drives which
belongs to same disk controller. And monitor the Disk Queue length , all
hardware resorce usage using Perfmon.
If you find every thing is normal then you are good. See the website
http://www.sql-server-performance.com/ for more performanace monitoring and
tuning options.
Thanks
Hari
SQL server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie
My Database Server is using RAID 5.
I put the mdf and ldf file of my database at the same drive.
Does it affect the SQL Server Performance?
Thanks
Robert LieThe best thing would be not to use Raid 5 due to performance.
For best overall performance, locate the database files (.mdf) and log files
(.ldf) on separate arrays in your server to isolate potentially conflicting
reads and writes. [6.5, 7.0, 2000] Updated 12-20-2004
*****
To store your database files (.mdf), the best performance is gained by
storing them using RAID 10 arrays. If this is too expensive, then RAID 5 is
the next best bet. Each RAID array (5 or 10) should have as many physical
disks in the array as the controller will support. This allows reads and
writes to be performed simultaneously on each physical drive in the array,
significantly boosting disk I/O. [6.5, 7.0, 2000] Updated 12-20-2004
From: http://www.sql-server-performance.com/sql_server_setup.asp
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Robert Lie" <robert.lie24@.gmail.com> schrieb im Newsbeitrag
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie|||Hi Robert,
yes but it only becomes a problem in very large databases, the ldf (log
file) should be on a drive of its own in a perfect world and using RAID5 for
it is overkill and will slow it's performance as the log file is written to
sequentially and most other things including the mdf file are written to
randomly. Again this is only a concirn is big installations and if you have
a spare physical drive then the ldf file could be put on that.
--
Regards
Alex White MCDBA MCSE
http://www.intralan.co.uk
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie|||Hi,
It is always recommended to put Data files and Log files in multiple drives,
it will be even better if you put the files in drives belongs to different
disk controllers.
This will help you to reduce the disk I/O and eventually the better
performance.
But incase if your volume pd transaction is less then you may not have any
I/O issues, inthis case you can keep both the files in same drives which
belongs to same disk controller. And monitor the Disk Queue length , all
hardware resorce usage using Perfmon.
If you find every thing is normal then you are good. See the website
http://www.sql-server-performance.com/ for more performanace monitoring and
tuning options.
Thanks
Hari
SQL server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23xPXnqWSFHA.2788@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> My Database Server is using RAID 5.
> I put the mdf and ldf file of my database at the same drive.
> Does it affect the SQL Server Performance?
> Thanks
> Robert Lie
MDF - Basic Question
Is it possible to 'query' an mdf file using MS Jet Provider or
somethnig like jet provider without having to 'attach' the mdf as a
database on SqlServer. Thanks.No. You must have a SQL Server engine to connect to it. You could install
MSDE (SQL Server 2000) or SQL Server Express (SQL Server 2005) and use it.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"S Chapman" <s_chapman47@.hotmail.co.uk> wrote in message
news:1148033398.353253.150440@.i40g2000cwc.googlegroups.com...
Is it possible to 'query' an mdf file using MS Jet Provider or
somethnig like jet provider without having to 'attach' the mdf as a
database on SqlServer. Thanks.
somethnig like jet provider without having to 'attach' the mdf as a
database on SqlServer. Thanks.No. You must have a SQL Server engine to connect to it. You could install
MSDE (SQL Server 2000) or SQL Server Express (SQL Server 2005) and use it.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"S Chapman" <s_chapman47@.hotmail.co.uk> wrote in message
news:1148033398.353253.150440@.i40g2000cwc.googlegroups.com...
Is it possible to 'query' an mdf file using MS Jet Provider or
somethnig like jet provider without having to 'attach' the mdf as a
database on SqlServer. Thanks.
MDB via Linked Server
I have a view names WSDetailJobList.
It contains one field and some joined tables from an MDB file for which we
have set up a linked server.
Here is a snippet of the view
select
...
EA.EmailAddress,
...
join
EZWEBPOST...WebPost WP
on
WP.ReqID = R.RequirementID
join
EZWEBPOST...tblEmailAddresses EA
on
EA.EmailAddressID = WP.ReplyEmailAddressID
...
It works perfectly from QA and from EM.
We have a consultant trying to use the view.
He's getting...
nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and
ANSI_WARNINGS options to be set for the connection. This ensures consistent
query semantics.
Can someone point me in the right direction?
Kyle!
Read about the command SET ANSI_NULLS and SET ANSI_WARNINGS in Books Online. Ask you programmer from
what type of environment he/she it accessing your SQL Server. Also, if you are using stored
procedures, you set ANSI WARNINGS inside the procedure. But ANSI_NULLS you need to set when you
create the procedure.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:enFB50CpFHA.3084@.TK2MSFTNGP09.phx.gbl...
>I have a view names WSDetailJobList.
> It contains one field and some joined tables from an MDB file for which we have set up a linked
> server.
> Here is a snippet of the view
> select
> ...
> EA.EmailAddress,
> ...
> join
> EZWEBPOST...WebPost WP
> on
> WP.ReqID = R.RequirementID
> join
> EZWEBPOST...tblEmailAddresses EA
> on
> EA.EmailAddressID = WP.ReplyEmailAddressID
> ...
> It works perfectly from QA and from EM.
> We have a consultant trying to use the view.
> He's getting...
> nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set
> for the connection. This ensures consistent query semantics.
>
> Can someone point me in the right direction?
> Kyle!
>
It contains one field and some joined tables from an MDB file for which we
have set up a linked server.
Here is a snippet of the view
select
...
EA.EmailAddress,
...
join
EZWEBPOST...WebPost WP
on
WP.ReqID = R.RequirementID
join
EZWEBPOST...tblEmailAddresses EA
on
EA.EmailAddressID = WP.ReplyEmailAddressID
...
It works perfectly from QA and from EM.
We have a consultant trying to use the view.
He's getting...
nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and
ANSI_WARNINGS options to be set for the connection. This ensures consistent
query semantics.
Can someone point me in the right direction?
Kyle!
Read about the command SET ANSI_NULLS and SET ANSI_WARNINGS in Books Online. Ask you programmer from
what type of environment he/she it accessing your SQL Server. Also, if you are using stored
procedures, you set ANSI WARNINGS inside the procedure. But ANSI_NULLS you need to set when you
create the procedure.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:enFB50CpFHA.3084@.TK2MSFTNGP09.phx.gbl...
>I have a view names WSDetailJobList.
> It contains one field and some joined tables from an MDB file for which we have set up a linked
> server.
> Here is a snippet of the view
> select
> ...
> EA.EmailAddress,
> ...
> join
> EZWEBPOST...WebPost WP
> on
> WP.ReqID = R.RequirementID
> join
> EZWEBPOST...tblEmailAddresses EA
> on
> EA.EmailAddressID = WP.ReplyEmailAddressID
> ...
> It works perfectly from QA and from EM.
> We have a consultant trying to use the view.
> He's getting...
> nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set
> for the connection. This ensures consistent query semantics.
>
> Can someone point me in the right direction?
> Kyle!
>
MDB via Linked Server
I have a view names WSDetailJobList.
It contains one field and some joined tables from an MDB file for which we
have set up a linked server.
Here is a snippet of the view
select
...
EA.EmailAddress,
...
join
EZWEBPOST...WebPost WP
on
WP.ReqID = R.RequirementID
join
EZWEBPOST...tblEmailAddresses EA
on
EA.EmailAddressID = WP.ReplyEmailAddressID
...
It works perfectly from QA and from EM.
We have a consultant trying to use the view.
He's getting...
nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and
ANSI_WARNINGS options to be set for the connection. This ensures consistent
query semantics.
Can someone point me in the right direction?
Kyle!Read about the command SET ANSI_NULLS and SET ANSI_WARNINGS in Books Online. Ask you programmer from
what type of environment he/she it accessing your SQL Server. Also, if you are using stored
procedures, you set ANSI WARNINGS inside the procedure. But ANSI_NULLS you need to set when you
create the procedure.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:enFB50CpFHA.3084@.TK2MSFTNGP09.phx.gbl...
>I have a view names WSDetailJobList.
> It contains one field and some joined tables from an MDB file for which we have set up a linked
> server.
> Here is a snippet of the view
> select
> ...
> EA.EmailAddress,
> ...
> join
> EZWEBPOST...WebPost WP
> on
> WP.ReqID = R.RequirementID
> join
> EZWEBPOST...tblEmailAddresses EA
> on
> EA.EmailAddressID = WP.ReplyEmailAddressID
> ...
> It works perfectly from QA and from EM.
> We have a consultant trying to use the view.
> He's getting...
> nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set
> for the connection. This ensures consistent query semantics.
>
> Can someone point me in the right direction?
> Kyle!
>
It contains one field and some joined tables from an MDB file for which we
have set up a linked server.
Here is a snippet of the view
select
...
EA.EmailAddress,
...
join
EZWEBPOST...WebPost WP
on
WP.ReqID = R.RequirementID
join
EZWEBPOST...tblEmailAddresses EA
on
EA.EmailAddressID = WP.ReplyEmailAddressID
...
It works perfectly from QA and from EM.
We have a consultant trying to use the view.
He's getting...
nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and
ANSI_WARNINGS options to be set for the connection. This ensures consistent
query semantics.
Can someone point me in the right direction?
Kyle!Read about the command SET ANSI_NULLS and SET ANSI_WARNINGS in Books Online. Ask you programmer from
what type of environment he/she it accessing your SQL Server. Also, if you are using stored
procedures, you set ANSI WARNINGS inside the procedure. But ANSI_NULLS you need to set when you
create the procedure.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:enFB50CpFHA.3084@.TK2MSFTNGP09.phx.gbl...
>I have a view names WSDetailJobList.
> It contains one field and some joined tables from an MDB file for which we have set up a linked
> server.
> Here is a snippet of the view
> select
> ...
> EA.EmailAddress,
> ...
> join
> EZWEBPOST...WebPost WP
> on
> WP.ReqID = R.RequirementID
> join
> EZWEBPOST...tblEmailAddresses EA
> on
> EA.EmailAddressID = WP.ReplyEmailAddressID
> ...
> It works perfectly from QA and from EM.
> We have a consultant trying to use the view.
> He's getting...
> nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set
> for the connection. This ensures consistent query semantics.
>
> Can someone point me in the right direction?
> Kyle!
>
MDB via Linked Server
I have a view names WSDetailJobList.
It contains one field and some joined tables from an MDB file for which we
have set up a linked server.
Here is a snippet of the view
select
...
EA.EmailAddress,
...
join
EZWEBPOST...WebPost WP
on
WP.ReqID = R.RequirementID
join
EZWEBPOST...tblEmailAddresses EA
on
EA.EmailAddressID = WP.ReplyEmailAddressID
...
It works perfectly from QA and from EM.
We have a consultant trying to use the view.
He's getting...
nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and
ANSI_WARNINGS options to be set for the connection. This ensures consistent
query semantics.
Can someone point me in the right direction?
Kyle!Read about the command SET ANSI_NULLS and SET ANSI_WARNINGS in Books Online.
Ask you programmer from
what type of environment he/she it accessing your SQL Server. Also, if you a
re using stored
procedures, you set ANSI WARNINGS inside the procedure. But ANSI_NULLS you n
eed to set when you
create the procedure.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:enFB50CpFHA.3084@.TK2MSFTNGP09.phx.gbl...
>I have a view names WSDetailJobList.
> It contains one field and some joined tables from an MDB file for which we
have set up a linked
> server.
> Here is a snippet of the view
> select
> ...
> EA.EmailAddress,
> ...
> join
> EZWEBPOST...WebPost WP
> on
> WP.ReqID = R.RequirementID
> join
> EZWEBPOST...tblEmailAddresses EA
> on
> EA.EmailAddressID = WP.ReplyEmailAddressID
> ...
> It works perfectly from QA and from EM.
> We have a consultant trying to use the view.
> He's getting...
> nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and ANSI_WA
RNINGS options to be set
> for the connection. This ensures consistent query semantics.
>
> Can someone point me in the right direction?
> Kyle!
>sql
It contains one field and some joined tables from an MDB file for which we
have set up a linked server.
Here is a snippet of the view
select
...
EA.EmailAddress,
...
join
EZWEBPOST...WebPost WP
on
WP.ReqID = R.RequirementID
join
EZWEBPOST...tblEmailAddresses EA
on
EA.EmailAddressID = WP.ReplyEmailAddressID
...
It works perfectly from QA and from EM.
We have a consultant trying to use the view.
He's getting...
nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and
ANSI_WARNINGS options to be set for the connection. This ensures consistent
query semantics.
Can someone point me in the right direction?
Kyle!Read about the command SET ANSI_NULLS and SET ANSI_WARNINGS in Books Online.
Ask you programmer from
what type of environment he/she it accessing your SQL Server. Also, if you a
re using stored
procedures, you set ANSI WARNINGS inside the procedure. But ANSI_NULLS you n
eed to set when you
create the procedure.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:enFB50CpFHA.3084@.TK2MSFTNGP09.phx.gbl...
>I have a view names WSDetailJobList.
> It contains one field and some joined tables from an MDB file for which we
have set up a linked
> server.
> Here is a snippet of the view
> select
> ...
> EA.EmailAddress,
> ...
> join
> EZWEBPOST...WebPost WP
> on
> WP.ReqID = R.RequirementID
> join
> EZWEBPOST...tblEmailAddresses EA
> on
> EA.EmailAddressID = WP.ReplyEmailAddressID
> ...
> It works perfectly from QA and from EM.
> We have a consultant trying to use the view.
> He's getting...
> nativecode=7405 - Heterogeneous queries require the ANSI_NULLS and ANSI_WA
RNINGS options to be set
> for the connection. This ensures consistent query semantics.
>
> Can someone point me in the right direction?
> Kyle!
>sql
mdb file support UTF8
i create mdb file in VB.NET project in vs2005 . i want that it support UTF8 for arabic language.
thanks .
There are two ways to do that you can create typed dataset with UTF8 or use some configuration provided by Microsoft, so there is no standard way to do it. Hope this helps.
http://msdn2.microsoft.com/en-us/library/aa662944(office.11).aspx
http://office.microsoft.com/en-us/ork2003/HA011402281033.aspx
Wednesday, March 28, 2012
MDAC error
I have upgraded MDAC to vers 2.7 SP1(winXP).
On checking via the MDAC Cmponent Checker that one file has an error or maybe currupt.
I have tried to reinstall with no joy. The error description is as follows:
Item Name,Item Type,ErrorString,Status
oledb32.dll,File,Field 'FileVersion' mismatch: Expect '2.71.9030.0 built by: Lab06_N(dagbuild)' Got '2.71.9031.4 built by: Lab06_N(dagbuild)',Error
Could you shed any light on what might be the problem is?
Cheers PetermJust uninstall everything related to MDAC and remove registry keys, reboot the box.
For information on MDAC issues refer to this Article (http://www.8wire.com/articles/index.asp?AID=2318) and this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;324520).
Make sure to install latest MDAC and SP from MS.
On checking via the MDAC Cmponent Checker that one file has an error or maybe currupt.
I have tried to reinstall with no joy. The error description is as follows:
Item Name,Item Type,ErrorString,Status
oledb32.dll,File,Field 'FileVersion' mismatch: Expect '2.71.9030.0 built by: Lab06_N(dagbuild)' Got '2.71.9031.4 built by: Lab06_N(dagbuild)',Error
Could you shed any light on what might be the problem is?
Cheers PetermJust uninstall everything related to MDAC and remove registry keys, reboot the box.
For information on MDAC issues refer to this Article (http://www.8wire.com/articles/index.asp?AID=2318) and this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;324520).
Make sure to install latest MDAC and SP from MS.
MDAC and SQL Server 2005
In the SQL Server 2005 upgrade advisor help file it states the following...
"Upgrade Advisor detected an older version of MDAC. MDAC versions before MDAC 2.8 SP1 do not support named instances. To allow application connections to named instances, upgrade to MDAC 2.8 SP1."
I've installed our application which uses ADO (not ADO.NET) to connect to an SQL Server named instance on a client machine. Our application installs MDAC 2.6. Therefore on older machines such as Windows 95 MDAC is upgraded to 2.6. Our application can still connect to the named instance without MDAC 2.8 SP1 being present.
Is this statement in the upgrade advisor entirely true or am I misunderstanding what it means?
Thanks.MDAC 2.6 does support named instances. However, SQL Server 2005 requires MDAC 2.8SP1 or higher
Hope this helps.
Regards
Uwa|||Thanks for the reply. When you say SQL Server 2005 requires MDAC 2.8SP1 or higher, do you mean being able to use SQL Server itself on the machine it is installed on or do you mean 2.8SP1 is required by clients for connectivity.
I've got a client machine here with MDAC 2.6SP2 installed where our application can perfectly connect to my server which is running SQL Server 2005 in a named instance.
Thanks|||SQL Server 2005 requires MDAC 28SP1 or higher on the machine it's installed on. Client machines with any MDAC version can connect to it but with some possible limitations (for example there is no support for named instances prior to MDAC 26).
For better performance and if you use the new data types in SQL Server 2005 or other cool new features (MARS, notifications etc), I would recommend you use the new SQLNCLI (SQL Server native client) which has the equivalent of the OLEDB provider and ODBC Driver in one DLL package. It has it's own MSI installer that is on the Server media. Please see http://support.microsoft.com/?kbid=910016 for more info|||Thanks for the information. My main concern is getting our existing applications that are based on SQL Server 2000 working with SQL Server 2005 so I am just concerned about MDAC at the moment.
I will certainly check out SQLNCLI though as that sounds interesting.
Thanks|||SQL Native Client is a good choice if you are using new features in SQL Server 2005. It's peformance is likely to be better than MDAC in many cases and it also scales better on multiprocessor machines.
However, if you have deployed clients and you are simply upgrading the server to SQL Server 2005 there is no requirement to upgrade from MDAC to SQL Native Client.|||
Thanks guys for good info.
I have a similar question. We have an application (C++ and built in 32bit) using ODBC driver to connec to SQL Server 2000 or Oracle 9 server. Can our application connect to SQL Server 2005 (64bit) without modification? We dont mind to install MDAC 2.8SP1 on the SQL Server 2005 (64bit) machine.
I would appreciate your help.
John
|||ODBC connectivity to SQL Server 2005 on 64bit is supported either via MDAC or the new SQL Native Client ODBC driver (which offers better performance and features in some areas).
And by the way, MDAC 28 is part of the Windows 2003 and XP operating systems so you will not need to install this.
Hope this helps.
Uwa
MDAC and SQL Server 2005
In the SQL Server 2005 upgrade advisor help file it states the following...
"Upgrade Advisor detected an older version of MDAC. MDAC versions before MDAC 2.8 SP1 do not support named instances. To allow application connections to named instances, upgrade to MDAC 2.8 SP1."
I've installed our application which uses ADO (not ADO.NET) to connect to an SQL Server named instance on a client machine. Our application installs MDAC 2.6. Therefore on older machines such as Windows 95 MDAC is upgraded to 2.6. Our application can still connect to the named instance without MDAC 2.8 SP1 being present.
Is this statement in the upgrade advisor entirely true or am I misunderstanding what it means?
Thanks.MDAC 2.6 does support named instances. However, SQL Server 2005 requires MDAC 2.8SP1 or higher
Hope this helps.
Regards
Uwa|||Thanks for the reply. When you say SQL Server 2005 requires MDAC 2.8SP1 or higher, do you mean being able to use SQL Server itself on the machine it is installed on or do you mean 2.8SP1 is required by clients for connectivity.
I've got a client machine here with MDAC 2.6SP2 installed where our application can perfectly connect to my server which is running SQL Server 2005 in a named instance.
Thanks|||SQL Server 2005 requires MDAC 28SP1 or higher on the machine it's installed on. Client machines with any MDAC version can connect to it but with some possible limitations (for example there is no support for named instances prior to MDAC 26).
For better performance and if you use the new data types in SQL Server 2005 or other cool new features (MARS, notifications etc), I would recommend you use the new SQLNCLI (SQL Server native client) which has the equivalent of the OLEDB provider and ODBC Driver in one DLL package. It has it's own MSI installer that is on the Server media. Please see http://support.microsoft.com/?kbid=910016 for more info|||Thanks for the information. My main concern is getting our existing applications that are based on SQL Server 2000 working with SQL Server 2005 so I am just concerned about MDAC at the moment.
I will certainly check out SQLNCLI though as that sounds interesting.
Thanks|||SQL Native Client is a good choice if you are using new features in SQL Server 2005. It's peformance is likely to be better than MDAC in many cases and it also scales better on multiprocessor machines.
However, if you have deployed clients and you are simply upgrading the server to SQL Server 2005 there is no requirement to upgrade from MDAC to SQL Native Client.|||
Thanks guys for good info.
I have a similar question. We have an application (C++ and built in 32bit) using ODBC driver to connec to SQL Server 2000 or Oracle 9 server. Can our application connect to SQL Server 2005 (64bit) without modification? We dont mind to install MDAC 2.8SP1 on the SQL Server 2005 (64bit) machine.
I would appreciate your help.
John
|||ODBC connectivity to SQL Server 2005 on 64bit is supported either via MDAC or the new SQL Native Client ODBC driver (which offers better performance and features in some areas).
And by the way, MDAC 28 is part of the Windows 2003 and XP operating systems so you will not need to install this.
Hope this helps.
Uwa
Wednesday, March 21, 2012
Maxing out log files when using SIMPLE
We have our databases set to SIMPLE model, but we continue to blow up during DataWarehouse loads because the log file fills. Our understanding is that SIMPLE should have no logging yet it appers to. I have 2 requests.
1) Is there a command to tell the database prior to the DataWarehouse load to not log any transactions?
2) Do we need to do more then set the DB to SIMPLE to get a general "no log" effect?
Thanks,
Todd1) No. Logging is never entirely turned off. The transaction log is simply not saved when you are in SIMPLE recovery mode.
2) Probably. The culprit is ikely to be your code. I would guess there is either:
a) A begin transaction statement somewhere way at the top of the process
or
b) the BCP/DTS load command is not batching the rows it is inserting.|||I know the culprit is the code. There is a join of massive tables. We had gone the batching route but it still was blowing up. We have ben increasing the max size of the log but were hoping we could stop going that direction.
Thanks|||If this is a complete refresh of the table (meaning you can drop it before running the insert), you can try to write the insert as SELECT INTO.|||With SIMPLE recovery, the log is not needed for backup, but SQL Server still needs it for recovery. Therefore every transaction is still logged, causing the log file to expand if there is no free space.
A section of a log file is marked for reuse as soon as all transactions are committed or rolled back and they are not needed for recovery, meaning the data has been written to disk during a checkpoint.|||Thanks for all the input
1) Is there a command to tell the database prior to the DataWarehouse load to not log any transactions?
2) Do we need to do more then set the DB to SIMPLE to get a general "no log" effect?
Thanks,
Todd1) No. Logging is never entirely turned off. The transaction log is simply not saved when you are in SIMPLE recovery mode.
2) Probably. The culprit is ikely to be your code. I would guess there is either:
a) A begin transaction statement somewhere way at the top of the process
or
b) the BCP/DTS load command is not batching the rows it is inserting.|||I know the culprit is the code. There is a join of massive tables. We had gone the batching route but it still was blowing up. We have ben increasing the max size of the log but were hoping we could stop going that direction.
Thanks|||If this is a complete refresh of the table (meaning you can drop it before running the insert), you can try to write the insert as SELECT INTO.|||With SIMPLE recovery, the log is not needed for backup, but SQL Server still needs it for recovery. Therefore every transaction is still logged, causing the log file to expand if there is no free space.
A section of a log file is marked for reuse as soon as all transactions are committed or rolled back and they are not needed for recovery, meaning the data has been written to disk during a checkpoint.|||Thanks for all the input
Wednesday, March 7, 2012
maximum datafile/log file size
Is there any limit to the maximum size of a datafile or transaction log you can have with SQL Server 2000 on Windows 2000. Also is there a maximum size that should be adhered to for performance and admin reasons ?.What number do you have in mind? The limitation is implemented through a Growth Limit setting if AutoGrowth is enabled. If Growth Limit is not set then it will be limited by the amount of free space on the disk.|||Books Online {Maximum Capacity Specifications}
Database size 1,048,516 TB ***
Databases per instance of SQL Server32,767
Filegroups per database 256
Files per database 32,767
File size (data) 32 TB
File size (log) 32 TB
footnote ***
The data portion of a database cannot exceed 2 GB in size when using the SQL Server 2000 Desktop Engine (MSDE 2000) or the Microsoft Data Engine (MSDE) 1.0. The total size of the database, including log files, can exceed 2 GB provided the sum of the sizes of the data files remains 2 GB or lower.
in addition, Database objects include all tables, views, stored procedures, extended stored procedures, triggers, rules, defaults, and constraints. The sum of the number of all these objects in a database cannot exceed 2,147,483,647.|||The database I have in mind is going to grow to be order of Terabytes in size, my question about size limits has been answered but can someone put this into the context of performance and admin implications.|||there is no one fix for this issue.
querying large sets of data has many obstacles to overcome.
index creation:
clustered, non-clustered, composite, indexed views, computed columns
query creation:
Probably the most misunderstood part of the dba's job.
what are your indexes?
what are yhour search arguments?
are you computing columns in the queries?
join strategies
and too many others
keep your result sets as small as you can and use effective search arguments.
use stored procedures views create statistics on commonly searched columns that will not be indexed.
Dont forget that transactions and queries are natural enemies and there is a great benefit to creating an OLAP solution for decision support services.
Microsoft SQL Server 2000 Performance Tuning Technical Reference (http://www.microsoft.com/MSPress/books/4944.asp)
Microsoft SQL Server 2000 RDBMS Performance Tuning Guide for Data Warehousing (http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/rdbmspft.mspx)
Database size 1,048,516 TB ***
Databases per instance of SQL Server32,767
Filegroups per database 256
Files per database 32,767
File size (data) 32 TB
File size (log) 32 TB
footnote ***
The data portion of a database cannot exceed 2 GB in size when using the SQL Server 2000 Desktop Engine (MSDE 2000) or the Microsoft Data Engine (MSDE) 1.0. The total size of the database, including log files, can exceed 2 GB provided the sum of the sizes of the data files remains 2 GB or lower.
in addition, Database objects include all tables, views, stored procedures, extended stored procedures, triggers, rules, defaults, and constraints. The sum of the number of all these objects in a database cannot exceed 2,147,483,647.|||The database I have in mind is going to grow to be order of Terabytes in size, my question about size limits has been answered but can someone put this into the context of performance and admin implications.|||there is no one fix for this issue.
querying large sets of data has many obstacles to overcome.
index creation:
clustered, non-clustered, composite, indexed views, computed columns
query creation:
Probably the most misunderstood part of the dba's job.
what are your indexes?
what are yhour search arguments?
are you computing columns in the queries?
join strategies
and too many others
keep your result sets as small as you can and use effective search arguments.
use stored procedures views create statistics on commonly searched columns that will not be indexed.
Dont forget that transactions and queries are natural enemies and there is a great benefit to creating an OLAP solution for decision support services.
Microsoft SQL Server 2000 Performance Tuning Technical Reference (http://www.microsoft.com/MSPress/books/4944.asp)
Microsoft SQL Server 2000 RDBMS Performance Tuning Guide for Data Warehousing (http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/rdbmspft.mspx)
Monday, February 20, 2012
max width for input fixed width column
Is there a maximum width for fixed width column?
I'm trying to read in a flat file (which, admittedly, has one very wide column), and it keeps breaking because of truncation when it tries to read in the file.
Any ideas?
Jim Work
What is the error exactly?|||Error: 0xC02020A1 at Data Flow Task, Flat File Source [1]: Data conversion failed. The data conversion for column "Column 1" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
Error: 0xC020902A at Data Flow Task, Flat File Source [1]: The "output column "Column 1" (157)" failed because truncation occurred, and the truncation row disposition on "output column "Column 1" (157)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
Error: 0xC0202092 at Data Flow Task, Flat File Source [1]: An error occurred while processing file "C:\data\sampleDepositFile1.txt" on data row 1.
Does that help?
|||Yes, it does.
Sounds to me like there are characters in the data that don't have a match in the codepage you are working with. Could be a non-unicode/unicode issue. Are there NULLs in the data? NULLs truncate strings as well.
What codepage are you using? 1252? What kind of data do you have in the file?|||1252 (ANSI - Latin I )
This is what the connection manager defaulted to, and I believe it matches up with my source data. Should I change it to (and go back and save the source data as) UTF-8?
Thanks for any insight you can give me!
|||How big is your column in the source file, and what have you defined in the flat file source? Pull it up in the advanced editor and ensure that the columns are the correct size there.
Subscribe to:
Posts (Atom)