Hi,everyone
I am a newbie to the SQL server.
In my project,I need a SQL server in minimal size to meet the XPE
environment.
How can I get the goal mentioned above?
Where can I find the technical articles or files needed for building minimal
SQL?
Any hints are appreciated!
Best regards!
MerryMerry.Win wrote:
> Hi,everyone
> I am a newbie to the SQL server.
> In my project,I need a SQL server in minimal size to meet the XPE
> environment.
> How can I get the goal mentioned above?
> Where can I find the technical articles or files needed for building minimal
> SQL?
> Any hints are appreciated!
> Best regards!
> Merry`
A good place to start is the SQL Server Home Page:
http://www.microsoft.com/sql/default.mspx
Check out SQL Server Mobile:
http://www.microsoft.com/sql/editions/sqlmobile/default.mspx
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Showing posts with label size. Show all posts
Showing posts with label size. Show all posts
Wednesday, March 28, 2012
Help for thin SQL Server
Hi,everyone
I am a newbie to the SQL server.
In my project,I need a SQL server in minimal size to meet the XPE
environment.
How can I get the goal mentioned above?
Where can I find the technical articles or files needed for building minimal
SQL?
Any hints are appreciated!
Best regards!
MerryMerry.Win wrote:
> Hi,everyone
> I am a newbie to the SQL server.
> In my project,I need a SQL server in minimal size to meet the XPE
> environment.
> How can I get the goal mentioned above?
> Where can I find the technical articles or files needed for building minim
al
> SQL?
> Any hints are appreciated!
> Best regards!
> Merry`
A good place to start is the SQL Server Home Page:
http://www.microsoft.com/sql/default.mspx
Check out SQL Server Mobile:
http://www.microsoft.com/sql/editio...le/default.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
I am a newbie to the SQL server.
In my project,I need a SQL server in minimal size to meet the XPE
environment.
How can I get the goal mentioned above?
Where can I find the technical articles or files needed for building minimal
SQL?
Any hints are appreciated!
Best regards!
MerryMerry.Win wrote:
> Hi,everyone
> I am a newbie to the SQL server.
> In my project,I need a SQL server in minimal size to meet the XPE
> environment.
> How can I get the goal mentioned above?
> Where can I find the technical articles or files needed for building minim
al
> SQL?
> Any hints are appreciated!
> Best regards!
> Merry`
A good place to start is the SQL Server Home Page:
http://www.microsoft.com/sql/default.mspx
Check out SQL Server Mobile:
http://www.microsoft.com/sql/editio...le/default.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Monday, March 26, 2012
Help Finding Current Size of a Field
How do I find the current size of each field in a table's column?
I have a table with a field for notes/memos. I need to see which ones are about to reach the size limit and what the current size is.
Does this make sense?
Thank you,
KarenSELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = 'MyTable'|||thanks!
Karen
I have a table with a field for notes/memos. I need to see which ones are about to reach the size limit and what the current size is.
Does this make sense?
Thank you,
KarenSELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = 'MyTable'|||thanks!
Karen
Wednesday, March 21, 2012
Help bcp import reports row size too large error
Hi
I want to use bcp tool to export a table from one machine to another
machine. And now the export works fine. But when I want to import the
text file generated by the export process to the target database, bcp
reports an error, and the operation fails. The error is
"Cannot sort a row of size 22416, which is greater than the allowable
maximum of 8094."
I think this error happens because my target table row size is too
big. Because I can not change the schema of target table, I do not how
to resolve it. Anybody can help me? Thanks.Hi
Your row size of 22416 is far more than 8094, therefore I would expect that
the row terminator is not being specified correctly. What command did you use
to BCP out the file and how are you trying to load it?
Are the versions of SQL Server on each machine the same or different?
John
"Hailin.Cai@.gmail.com" wrote:
> Hi
> I want to use bcp tool to export a table from one machine to another
> machine. And now the export works fine. But when I want to import the
> text file generated by the export process to the target database, bcp
> reports an error, and the operation fails. The error is
> "Cannot sort a row of size 22416, which is greater than the allowable
> maximum of 8094."
> I think this error happens because my target table row size is too
> big. Because I can not change the schema of target table, I do not how
> to resolve it. Anybody can help me? Thanks.
>|||If you are using Microsoft's BCP utility to extract the data from the
source database, then I assume the source is SQL Server 2005 and is
using something like VARCHAR(MAX) to allow row size greater than the
normal limit.
If the target table can not be changed you have to decide what is the
proper thing to do with the rows that have the problem. Should they
be discarded? Should the problem column(s) be truncated?
Once you know how you want to deal with the problem, I suggest writing
a VIEW on the source system. The view should truncate the output (if
that is the choice), or skip the rows, whatever you have to do so the
output from the view matches the table on the target system. Then BCP
out from the view, rather than the table.
Roy Harvey
Beacon Falls, CT
On Thu, 27 Sep 2007 16:29:51 -0700, Hailin.Cai@.gmail.com wrote:
>Hi
>I want to use bcp tool to export a table from one machine to another
>machine. And now the export works fine. But when I want to import the
>text file generated by the export process to the target database, bcp
>reports an error, and the operation fails. The error is
>"Cannot sort a row of size 22416, which is greater than the allowable
>maximum of 8094."
>I think this error happens because my target table row size is too
>big. Because I can not change the schema of target table, I do not how
>to resolve it. Anybody can help me? Thanks.|||On Sep 28, 9:42 am, "Roy Harvey (SQL Server MVP)"
<roy_har...@.snet.net> wrote:
> If you are using Microsoft's BCP utility to extract the data from the
> source database, then I assume the source is SQL Server 2005 and is
> using something like VARCHAR(MAX) to allow row size greater than the
> normal limit.
> If the target table can not be changed you have to decide what is the
> proper thing to do with the rows that have the problem. Should they
> be discarded? Should the problem column(s) be truncated?
> Once you know how you want to deal with the problem, I suggest writing
> a VIEW on the source system. The view should truncate the output (if
> that is the choice), or skip the rows, whatever you have to do so the
> output from the view matches the table on the target system. Then BCP
> out from the view, rather than the table.
> Roy Harvey
> Beacon Falls, CT
>
> On Thu, 27 Sep 2007 16:29:51 -0700, Hailin...@.gmail.com wrote:
> >Hi
> >I want to use bcp tool to export a table from one machine to another
> >machine. And now the export works fine. But when I want to import the
> >text file generated by the export process to the target database, bcp
> >reports an error, and the operation fails. The error is
> >"Cannot sort a row of size 22416, which is greater than the allowable
> >maximum of 8094."
> >I think this error happens because my target table row size is too
> >big. Because I can not change the schema of target table, I do not how
> >to resolve it. Anybody can help me? Thanks.- Hide quoted text -
> - Show quoted text -
Thanks for your suggestion. I will try.
I want to use bcp tool to export a table from one machine to another
machine. And now the export works fine. But when I want to import the
text file generated by the export process to the target database, bcp
reports an error, and the operation fails. The error is
"Cannot sort a row of size 22416, which is greater than the allowable
maximum of 8094."
I think this error happens because my target table row size is too
big. Because I can not change the schema of target table, I do not how
to resolve it. Anybody can help me? Thanks.Hi
Your row size of 22416 is far more than 8094, therefore I would expect that
the row terminator is not being specified correctly. What command did you use
to BCP out the file and how are you trying to load it?
Are the versions of SQL Server on each machine the same or different?
John
"Hailin.Cai@.gmail.com" wrote:
> Hi
> I want to use bcp tool to export a table from one machine to another
> machine. And now the export works fine. But when I want to import the
> text file generated by the export process to the target database, bcp
> reports an error, and the operation fails. The error is
> "Cannot sort a row of size 22416, which is greater than the allowable
> maximum of 8094."
> I think this error happens because my target table row size is too
> big. Because I can not change the schema of target table, I do not how
> to resolve it. Anybody can help me? Thanks.
>|||If you are using Microsoft's BCP utility to extract the data from the
source database, then I assume the source is SQL Server 2005 and is
using something like VARCHAR(MAX) to allow row size greater than the
normal limit.
If the target table can not be changed you have to decide what is the
proper thing to do with the rows that have the problem. Should they
be discarded? Should the problem column(s) be truncated?
Once you know how you want to deal with the problem, I suggest writing
a VIEW on the source system. The view should truncate the output (if
that is the choice), or skip the rows, whatever you have to do so the
output from the view matches the table on the target system. Then BCP
out from the view, rather than the table.
Roy Harvey
Beacon Falls, CT
On Thu, 27 Sep 2007 16:29:51 -0700, Hailin.Cai@.gmail.com wrote:
>Hi
>I want to use bcp tool to export a table from one machine to another
>machine. And now the export works fine. But when I want to import the
>text file generated by the export process to the target database, bcp
>reports an error, and the operation fails. The error is
>"Cannot sort a row of size 22416, which is greater than the allowable
>maximum of 8094."
>I think this error happens because my target table row size is too
>big. Because I can not change the schema of target table, I do not how
>to resolve it. Anybody can help me? Thanks.|||On Sep 28, 9:42 am, "Roy Harvey (SQL Server MVP)"
<roy_har...@.snet.net> wrote:
> If you are using Microsoft's BCP utility to extract the data from the
> source database, then I assume the source is SQL Server 2005 and is
> using something like VARCHAR(MAX) to allow row size greater than the
> normal limit.
> If the target table can not be changed you have to decide what is the
> proper thing to do with the rows that have the problem. Should they
> be discarded? Should the problem column(s) be truncated?
> Once you know how you want to deal with the problem, I suggest writing
> a VIEW on the source system. The view should truncate the output (if
> that is the choice), or skip the rows, whatever you have to do so the
> output from the view matches the table on the target system. Then BCP
> out from the view, rather than the table.
> Roy Harvey
> Beacon Falls, CT
>
> On Thu, 27 Sep 2007 16:29:51 -0700, Hailin...@.gmail.com wrote:
> >Hi
> >I want to use bcp tool to export a table from one machine to another
> >machine. And now the export works fine. But when I want to import the
> >text file generated by the export process to the target database, bcp
> >reports an error, and the operation fails. The error is
> >"Cannot sort a row of size 22416, which is greater than the allowable
> >maximum of 8094."
> >I think this error happens because my target table row size is too
> >big. Because I can not change the schema of target table, I do not how
> >to resolve it. Anybody can help me? Thanks.- Hide quoted text -
> - Show quoted text -
Thanks for your suggestion. I will try.
Friday, February 24, 2012
Help - "Could not allocate space for object as the secondary group is full" error
Hello Peers,
We have a database in SqlServer 2K with a following settings:
Primary Group Size: 1024MB
Secondary Group Size: 1023 MB
Transaction Log size: 236 MB
File Growth: 10%
Recover Model: Simple
Auto Shrink: OFF
Recovery Model: Simple
We have a table "TestTable' that has 400,000 records. All the indexes
for the table is on the Secondary group.
The problem is, when we alter a size of the column and save the
changes in EnterPriseManager, we get the error "Could not allocate
space for object 'TestTable' in database 'TestDb' because the
'Secondary' filegroup is full." We get the same error when we use
"Alter Column" command in Query Analyzer as well(We have run "Dbcc
ShrinkFile" before running the alter table command).
Could anyone throw some light on altering the size of columns on a
table with 400000+records without any problems like the one above?
TIA for any help.
Regards
Pradeep.L
On May 11, 11:56 am, pradee...@.hotmail.com wrote:
> Hello Peers,
> We have a database in SqlServer 2K with a following settings:
> Primary Group Size: 1024MB
> Secondary Group Size: 1023 MB
> Transaction Log size: 236 MB
> File Growth: 10%
> Recover Model: Simple
> Auto Shrink: OFF
> Recovery Model: Simple
> We have a table "TestTable' that has 400,000 records. All the indexes
> for the table is on the Secondary group.
> The problem is, when we alter a size of the column and save the
> changes in EnterPriseManager, we get the error "Could not allocate
> space for object 'TestTable' in database 'TestDb' because the
> 'Secondary' filegroup is full." We get the same error when we use
> "Alter Column" command in Query Analyzer as well(We have run "Dbcc
> ShrinkFile" before running the alter table command).
> Could anyone throw some light on altering the size of columns on a
> table with 400000+records without any problems like the one above?
> TIA for any help.
> Regards
> Pradeep.L
Pradeep.L,
If you right click on your database in EM and select "Properties" and
"Data File tab" what do you see? Is the "restrict file growth" radio
button checked? Are you trying to make the db bigger than is allowed?
Or are you running out of disc space on the drive where this db/file
group is stored?
Kristina
|||Hello Kristina,
[vbcol=seagreen]
No. It is set to "Unrestricted File Growth" for Datafile and
Transaction log.
[vbcol=seagreen]
I'm not sure about this. The maximum db size that is permitted in our
machine is 2GB and it complains that the cumulative size should not
exceed 2048 MB due to the license policy.
[vbcol=seagreen]
group is stored?
There is 15GB free space in the partition in which sql server is
installed
-
BTW, The purpose of trying out this issue is we need to increase the
size of quite a few columns in our production server.
Most of the columns are part of composite primary key/Index. We would
like to ensure that we don't land in sticky waters
when we go out with the change in our production server-
|||<pradeepln@.hotmail.com> wrote in message
news:1178942162.311166.101130@.e65g2000hsc.googlegr oups.com...
> Hello Kristina,
> No. It is set to "Unrestricted File Growth" for Datafile and
> Transaction log.
> I'm not sure about this. The maximum db size that is permitted in our
> machine is 2GB and it complains that the cumulative size should not
> exceed 2048 MB due to the license policy.
Ummm, 2048 MB IS 2GB.
Sounds like you've reached your max. Or I'm misunderstanding you.
> group is stored?
> There is 15GB free space in the partition in which sql server is
> installed-
> BTW, The purpose of trying out this issue is we need to increase the
> size of quite a few columns in our production server.
> Most of the columns are part of composite primary key/Index. We would
> like to ensure that we don't land in sticky waters
> when we go out with the change in our production server-
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
We have a database in SqlServer 2K with a following settings:
Primary Group Size: 1024MB
Secondary Group Size: 1023 MB
Transaction Log size: 236 MB
File Growth: 10%
Recover Model: Simple
Auto Shrink: OFF
Recovery Model: Simple
We have a table "TestTable' that has 400,000 records. All the indexes
for the table is on the Secondary group.
The problem is, when we alter a size of the column and save the
changes in EnterPriseManager, we get the error "Could not allocate
space for object 'TestTable' in database 'TestDb' because the
'Secondary' filegroup is full." We get the same error when we use
"Alter Column" command in Query Analyzer as well(We have run "Dbcc
ShrinkFile" before running the alter table command).
Could anyone throw some light on altering the size of columns on a
table with 400000+records without any problems like the one above?
TIA for any help.
Regards
Pradeep.L
On May 11, 11:56 am, pradee...@.hotmail.com wrote:
> Hello Peers,
> We have a database in SqlServer 2K with a following settings:
> Primary Group Size: 1024MB
> Secondary Group Size: 1023 MB
> Transaction Log size: 236 MB
> File Growth: 10%
> Recover Model: Simple
> Auto Shrink: OFF
> Recovery Model: Simple
> We have a table "TestTable' that has 400,000 records. All the indexes
> for the table is on the Secondary group.
> The problem is, when we alter a size of the column and save the
> changes in EnterPriseManager, we get the error "Could not allocate
> space for object 'TestTable' in database 'TestDb' because the
> 'Secondary' filegroup is full." We get the same error when we use
> "Alter Column" command in Query Analyzer as well(We have run "Dbcc
> ShrinkFile" before running the alter table command).
> Could anyone throw some light on altering the size of columns on a
> table with 400000+records without any problems like the one above?
> TIA for any help.
> Regards
> Pradeep.L
Pradeep.L,
If you right click on your database in EM and select "Properties" and
"Data File tab" what do you see? Is the "restrict file growth" radio
button checked? Are you trying to make the db bigger than is allowed?
Or are you running out of disc space on the drive where this db/file
group is stored?
Kristina
|||Hello Kristina,
[vbcol=seagreen]
No. It is set to "Unrestricted File Growth" for Datafile and
Transaction log.
[vbcol=seagreen]
I'm not sure about this. The maximum db size that is permitted in our
machine is 2GB and it complains that the cumulative size should not
exceed 2048 MB due to the license policy.
[vbcol=seagreen]
group is stored?
There is 15GB free space in the partition in which sql server is
installed
-BTW, The purpose of trying out this issue is we need to increase the
size of quite a few columns in our production server.
Most of the columns are part of composite primary key/Index. We would
like to ensure that we don't land in sticky waters
when we go out with the change in our production server
-|||<pradeepln@.hotmail.com> wrote in message
news:1178942162.311166.101130@.e65g2000hsc.googlegr oups.com...
> Hello Kristina,
> No. It is set to "Unrestricted File Growth" for Datafile and
> Transaction log.
> I'm not sure about this. The maximum db size that is permitted in our
> machine is 2GB and it complains that the cumulative size should not
> exceed 2048 MB due to the license policy.
Ummm, 2048 MB IS 2GB.
Sounds like you've reached your max. Or I'm misunderstanding you.
> group is stored?
> There is 15GB free space in the partition in which sql server is
> installed
-> BTW, The purpose of trying out this issue is we need to increase the
> size of quite a few columns in our production server.
> Most of the columns are part of composite primary key/Index. We would
> like to ensure that we don't land in sticky waters
> when we go out with the change in our production server
->
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
Help
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE=3D flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 =BD......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.This seems to be a duplicate post to the one in "Clients".
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tommy2" <tommy2@.ptd.net> wrote in message
news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 ......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.|||Hi,
To truncate the log file in 6.5 do the below steps:-
use dbname
go
dbcc checktable(syslogs)
go
Dump tran dbname with no_log
After running that execute below command to get the log size.
DBCC SQLPERF(LOGSPACE)
Thanks
Hari
SQL Server MVP
"tommy2" <tommy2@.ptd.net> wrote in message
news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 ......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.|||Thanks for your help!!
I have a cpl questions if you would not mind.
do users have to be off to run this procedure?
will running this procedure endanger any of the data?
any special things I need to know or do because this is version 6.5?
what do I need to back up before running this procedure?
I really thank you for your help!!
Tom
Hari Prasad wrote:
> Hi,
> To truncate the log file in 6.5 do the below steps:-
> use dbname
> go
> dbcc checktable(syslogs)
> go
> Dump tran dbname with no_log
>
> After running that execute below command to get the log size.
> DBCC SQLPERF(LOGSPACE)
> Thanks
> Hari
> SQL Server MVP
> "tommy2" <tommy2@.ptd.net> wrote in message
> news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
> I am having a issue with a customers server. the specs are:
> 2003 server
> sql 6.5
> log file size is 1998MB (customer increased this 2 times this week) Log
> space avail:600mb
> In EM i try and truncate the log file... but the free space never
> increases. Also there is no maint. plan on this database. When I try
> and create one it advises against creating one with databases over
> 400MB.
> SQL has been on this server for 6 months. The problem just started.
> The past day or so these errors are showing up:
>
> Any help?
>
> Event Type: Error
> Event Source: MSSQLServer
> Event Category: (2)
> Event ID: 17060
> Date: 8/4/2006
> Time: 7:51:20 AM
> User: N/A
> Computer: AUX-SERVER
> Description:
> The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
> be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE=3D flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: Error : 701, Severity: 17, State: 2,
> There is insufficient system memory to run this query..
> Data:
> 0000: bd 02 00 00 11 00 00 00 =BD......
> 0008: 00 00 00 00 07 00 00 00 ......
> 0010: 6d 61 73 74 65 72 00 master.
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE=3D flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 =BD......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.This seems to be a duplicate post to the one in "Clients".
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tommy2" <tommy2@.ptd.net> wrote in message
news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 ......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.|||Hi,
To truncate the log file in 6.5 do the below steps:-
use dbname
go
dbcc checktable(syslogs)
go
Dump tran dbname with no_log
After running that execute below command to get the log size.
DBCC SQLPERF(LOGSPACE)
Thanks
Hari
SQL Server MVP
"tommy2" <tommy2@.ptd.net> wrote in message
news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 ......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.|||Thanks for your help!!
I have a cpl questions if you would not mind.
do users have to be off to run this procedure?
will running this procedure endanger any of the data?
any special things I need to know or do because this is version 6.5?
what do I need to back up before running this procedure?
I really thank you for your help!!
Tom
Hari Prasad wrote:
> Hi,
> To truncate the log file in 6.5 do the below steps:-
> use dbname
> go
> dbcc checktable(syslogs)
> go
> Dump tran dbname with no_log
>
> After running that execute below command to get the log size.
> DBCC SQLPERF(LOGSPACE)
> Thanks
> Hari
> SQL Server MVP
> "tommy2" <tommy2@.ptd.net> wrote in message
> news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
> I am having a issue with a customers server. the specs are:
> 2003 server
> sql 6.5
> log file size is 1998MB (customer increased this 2 times this week) Log
> space avail:600mb
> In EM i try and truncate the log file... but the free space never
> increases. Also there is no maint. plan on this database. When I try
> and create one it advises against creating one with databases over
> 400MB.
> SQL has been on this server for 6 months. The problem just started.
> The past day or so these errors are showing up:
>
> Any help?
>
> Event Type: Error
> Event Source: MSSQLServer
> Event Category: (2)
> Event ID: 17060
> Date: 8/4/2006
> Time: 7:51:20 AM
> User: N/A
> Computer: AUX-SERVER
> Description:
> The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
> be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE=3D flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: Error : 701, Severity: 17, State: 2,
> There is insufficient system memory to run this query..
> Data:
> 0000: bd 02 00 00 11 00 00 00 =BD......
> 0008: 00 00 00 00 07 00 00 00 ......
> 0010: 6d 61 73 74 65 72 00 master.
Sunday, February 19, 2012
Help
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE=3D flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 =BD......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.This seems to be a duplicate post to the one in "Clients".
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tommy2" <tommy2@.ptd.net> wrote in message
news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 ½......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.|||Hi,
To truncate the log file in 6.5 do the below steps:-
use dbname
go
dbcc checktable(syslogs)
go
Dump tran dbname with no_log
After running that execute below command to get the log size.
DBCC SQLPERF(LOGSPACE)
Thanks
Hari
SQL Server MVP
"tommy2" <tommy2@.ptd.net> wrote in message
news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 ½......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.|||Thanks for your help!!
I have a cpl questions if you would not mind.
do users have to be off to run this procedure?
will running this procedure endanger any of the data?
any special things I need to know or do because this is version 6.5?
what do I need to back up before running this procedure?
I really thank you for your help!!
Tom
Hari Prasad wrote:
> Hi,
> To truncate the log file in 6.5 do the below steps:-
> use dbname
> go
> dbcc checktable(syslogs)
> go
> Dump tran dbname with no_log
>
> After running that execute below command to get the log size.
> DBCC SQLPERF(LOGSPACE)
> Thanks
> Hari
> SQL Server MVP
> "tommy2" <tommy2@.ptd.net> wrote in message
> news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
> I am having a issue with a customers server. the specs are:
> 2003 server
> sql 6.5
> log file size is 1998MB (customer increased this 2 times this week) Log
> space avail:600mb
> In EM i try and truncate the log file... but the free space never
> increases. Also there is no maint. plan on this database. When I try
> and create one it advises against creating one with databases over
> 400MB.
> SQL has been on this server for 6 months. The problem just started.
> The past day or so these errors are showing up:
>
> Any help?
>
> Event Type: Error
> Event Source: MSSQLServer
> Event Category: (2)
> Event ID: 17060
> Date: 8/4/2006
> Time: 7:51:20 AM
> User: N/A
> Computer: AUX-SERVER
> Description:
> The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
> be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE=3D flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: Error : 701, Severity: 17, State: 2,
> There is insufficient system memory to run this query..
> Data:
> 0000: bd 02 00 00 11 00 00 00 =BD......
> 0008: 00 00 00 00 07 00 00 00 ......
> 0010: 6d 61 73 74 65 72 00 master.
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE=3D flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 =BD......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.This seems to be a duplicate post to the one in "Clients".
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tommy2" <tommy2@.ptd.net> wrote in message
news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 ½......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.|||Hi,
To truncate the log file in 6.5 do the below steps:-
use dbname
go
dbcc checktable(syslogs)
go
Dump tran dbname with no_log
After running that execute below command to get the log size.
DBCC SQLPERF(LOGSPACE)
Thanks
Hari
SQL Server MVP
"tommy2" <tommy2@.ptd.net> wrote in message
news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.
SQL has been on this server for 6 months. The problem just started.
The past day or so these errors are showing up:
Any help?
Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 8/4/2006
Time: 7:51:20 AM
User: N/A
Computer: AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 ½......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.|||Thanks for your help!!
I have a cpl questions if you would not mind.
do users have to be off to run this procedure?
will running this procedure endanger any of the data?
any special things I need to know or do because this is version 6.5?
what do I need to back up before running this procedure?
I really thank you for your help!!
Tom
Hari Prasad wrote:
> Hi,
> To truncate the log file in 6.5 do the below steps:-
> use dbname
> go
> dbcc checktable(syslogs)
> go
> Dump tran dbname with no_log
>
> After running that execute below command to get the log size.
> DBCC SQLPERF(LOGSPACE)
> Thanks
> Hari
> SQL Server MVP
> "tommy2" <tommy2@.ptd.net> wrote in message
> news:1154722787.468850.206630@.s13g2000cwa.googlegroups.com...
> I am having a issue with a customers server. the specs are:
> 2003 server
> sql 6.5
> log file size is 1998MB (customer increased this 2 times this week) Log
> space avail:600mb
> In EM i try and truncate the log file... but the free space never
> increases. Also there is no maint. plan on this database. When I try
> and create one it advises against creating one with databases over
> 400MB.
> SQL has been on this server for 6 months. The problem just started.
> The past day or so these errors are showing up:
>
> Any help?
>
> Event Type: Error
> Event Source: MSSQLServer
> Event Category: (2)
> Event ID: 17060
> Date: 8/4/2006
> Time: 7:51:20 AM
> User: N/A
> Computer: AUX-SERVER
> Description:
> The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
> be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE=3D flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: Error : 701, Severity: 17, State: 2,
> There is insufficient system memory to run this query..
> Data:
> 0000: bd 02 00 00 11 00 00 00 =BD......
> 0008: 00 00 00 00 07 00 00 00 ......
> 0010: 6d 61 73 74 65 72 00 master.
Subscribe to:
Posts (Atom)