sql error: properties

Showing posts with label properties. Show all posts

Saturday, February 25, 2012

"Maximum Memory" setting in SQL Server properties

I have inherrited a sql 2k standard server running Win2K standard Ed with 3.5
gb RAM (!?!) on a raid 5 (!?!). The server is dedicated for SQL only and has
4 CPUs.
The "maximum memory" setting is set to 3500 MB and SQL is using around 1.75
GB of physical ram and 1.75 GB of Virtual Memory (total:3500 MB). Any inputs
on if the "maximum memory" setting should be left to 3500mb or should it be
reduced to 2000 MB so SQL uses only the physical ram? I am aware that the
transaction log should not be on a raid 5 for performance reasons and I know
that SQL 2k Standard + Win2k standard will not let me use more than 2 GB of
RAM for SQL. The average Physical Disk (_total) activity is 56% which is
considered very high.
Any inputs would be appreciated on this setting while we order the SQL2K
Enterprise on Win2K Advanced Ed. and add an extra controller and 15 RPM
drives...Hi
SQL Server Standard Edition is limited to 2GB of RAM. If you have more, it
will not use it. You need to install SQL Server Expertise Edition to use
more RAM (and set /3GB switch in your boot.ini). SQL Server knows it must
leave space for the OS, so the .25 is left for the OS in the sub 2GB memory
area.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Anonymous" <Anonymous@.discussions.microsoft.com> wrote in message
news:E5260014-1A9E-47AF-9247-0F8F5B25F8DF@.microsoft.com...
> I have inherrited a sql 2k standard server running Win2K standard Ed with
3.5
> gb RAM (!?!) on a raid 5 (!?!). The server is dedicated for SQL only and
has
> 4 CPUs.
> The "maximum memory" setting is set to 3500 MB and SQL is using around
1.75
> GB of physical ram and 1.75 GB of Virtual Memory (total:3500 MB). Any
inputs
> on if the "maximum memory" setting should be left to 3500mb or should it
be
> reduced to 2000 MB so SQL uses only the physical ram? I am aware that the
> transaction log should not be on a raid 5 for performance reasons and I
know
> that SQL 2k Standard + Win2k standard will not let me use more than 2 GB
of
> RAM for SQL. The average Physical Disk (_total) activity is 56% which is
> considered very high.
> Any inputs would be appreciated on this setting while we order the SQL2K
> Enterprise on Win2K Advanced Ed. and add an extra controller and 15 RPM
> drives...
>|||Thanks for your reply.
I fully understand what you are saying (as it was also statement in my
request). I am interested to know about he virtual memory portion of it.
Thanks again
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> SQL Server Standard Edition is limited to 2GB of RAM. If you have more, it
> will not use it. You need to install SQL Server Expertise Edition to use
> more RAM (and set /3GB switch in your boot.ini). SQL Server knows it must
> leave space for the OS, so the .25 is left for the OS in the sub 2GB memory
> area.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Anonymous" <Anonymous@.discussions.microsoft.com> wrote in message
> news:E5260014-1A9E-47AF-9247-0F8F5B25F8DF@.microsoft.com...
> > I have inherrited a sql 2k standard server running Win2K standard Ed with
> 3.5
> > gb RAM (!?!) on a raid 5 (!?!). The server is dedicated for SQL only and
> has
> > 4 CPUs.
> >
> > The "maximum memory" setting is set to 3500 MB and SQL is using around
> 1.75
> > GB of physical ram and 1.75 GB of Virtual Memory (total:3500 MB). Any
> inputs
> > on if the "maximum memory" setting should be left to 3500mb or should it
> be
> > reduced to 2000 MB so SQL uses only the physical ram? I am aware that the
> > transaction log should not be on a raid 5 for performance reasons and I
> know
> > that SQL 2k Standard + Win2k standard will not let me use more than 2 GB
> of
> > RAM for SQL. The average Physical Disk (_total) activity is 56% which is
> > considered very high.
> >
> > Any inputs would be appreciated on this setting while we order the SQL2K
> > Enterprise on Win2K Advanced Ed. and add an extra controller and 15 RPM
> > drives...
> >
> >
>
>|||"Anonymous" <Anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
news:1D46A3CC-2D84-4FAA-AA97-24DDA8A27443@.microsoft.com...
> Thanks for your reply.
> I fully understand what you are saying (as it was also statement in my
> request). I am interested to know about he virtual memory portion of it.
From the application's point of view physical and virtual memory are just
the same. You must not sum them up. Physical mem in TaskMGR shows the
portion of the application that's actually in main memory while virtual
mem shows the total allocated size. Your case is optimal with regard to
swapping: the process is completely in physical mem.
As Mike said, your SQL Server will never use more than what it uses at the
moment unless you install enterprise edition.
You should use perfmon to determine what causes the high disk activity.
Regards
robert
> Thanks again
> "Mike Epprecht (SQL MVP)" wrote:
> > Hi
> >
> > SQL Server Standard Edition is limited to 2GB of RAM. If you have
more, it
> > will not use it. You need to install SQL Server Expertise Edition to
use
> > more RAM (and set /3GB switch in your boot.ini). SQL Server knows it
must
> > leave space for the OS, so the .25 is left for the OS in the sub 2GB
memory
> > area.
> >
> > Regards
> > --
> > Mike Epprecht, Microsoft SQL Server MVP
> > Zurich, Switzerland
> >
> > IM: mike@.epprecht.net
> >
> > MVP Program: http://www.microsoft.com/mvp
> >
> > Blog: http://www.msmvps.com/epprecht/
> >
> > "Anonymous" <Anonymous@.discussions.microsoft.com> wrote in message
> > news:E5260014-1A9E-47AF-9247-0F8F5B25F8DF@.microsoft.com...
> > > I have inherrited a sql 2k standard server running Win2K standard Ed
with
> > 3.5
> > > gb RAM (!?!) on a raid 5 (!?!). The server is dedicated for SQL
only and
> > has
> > > 4 CPUs.
> > >
> > > The "maximum memory" setting is set to 3500 MB and SQL is using
around
> > 1.75
> > > GB of physical ram and 1.75 GB of Virtual Memory (total:3500 MB).
Any
> > inputs
> > > on if the "maximum memory" setting should be left to 3500mb or
should it
> > be
> > > reduced to 2000 MB so SQL uses only the physical ram? I am aware
that the
> > > transaction log should not be on a raid 5 for performance reasons
and I
> > know
> > > that SQL 2k Standard + Win2k standard will not let me use more than
2 GB
> > of
> > > RAM for SQL. The average Physical Disk (_total) activity is 56%
which is
> > > considered very high.
> > >
> > > Any inputs would be appreciated on this setting while we order the
SQL2K
> > > Enterprise on Win2K Advanced Ed. and add an extra controller and 15
RPM
> > > drives...
> > >
> > >
> >
> >
> >

"Maximum Memory" setting in SQL Server properties

Sunday, February 19, 2012

"Invalid command option D."

When trying to start SQL 2000 from dos prompt.
I changed the start up locations -D -L -E for my server from EM
server properties, Moved the Data and log files (MDF and LDFs), then tried
to
restart the server and it failed. I duplicated all files to their original
locations,
and again tried to restart from command-line with -d -l but nothing works...
When I changed the Server Properties I used capital D, and when I try to
start
SQL from DOS I get "Invalid command option D."
Please help me !! what Have I done to myself
Does anyone have any idea what I need to do to get this server backup'
Thanks!!WANNABE wrote:
> When trying to start SQL 2000 from dos prompt.
> I changed the start up locations -D -L -E for my server from EM
> server properties, Moved the Data and log files (MDF and LDFs), then tried
> to
> restart the server and it failed. I duplicated all files to their original
> locations,
> and again tried to restart from command-line with -d -l but nothing works...
> When I changed the Server Properties I used capital D, and when I try to
> start
> SQL from DOS I get "Invalid command option D."
> Please help me !! what Have I done to myself
> Does anyone have any idea what I need to do to get this server backup'
> Thanks!!
>
What is the EXACT command, including switches, that you are running from
the DOS prompt?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||You need to put back the model database to where it used to be. The reference to the model database
is *inside* master.mdf. SQL Server cannot start without model since it cannot create tempdb, and SQL
Server cannot live without tempdb. You probably want to do the same for msdb, and other user
database, but those will not prohibit SQL Server from starting. You really should read KB 224071
first... :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:O%23ITWuKvGHA.4460@.TK2MSFTNGP04.phx.gbl...
> When trying to start SQL 2000 from dos prompt.
> I changed the start up locations -D -L -E for my server from EM
> server properties, Moved the Data and log files (MDF and LDFs), then tried to
> restart the server and it failed. I duplicated all files to their original locations,
> and again tried to restart from command-line with -d -l but nothing works...
> When I changed the Server Properties I used capital D, and when I try to start
> SQL from DOS I get "Invalid command option D."
> Please help me !! what Have I done to myself
> Does anyone have any idea what I need to do to get this server backup'
> Thanks!!
>|||Thanks, but I do have all dbs in both places, and it still wont start. I
try "sqlservr" and it returns the "Invalid command option D."
error
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23FpPvYLvGHA.428@.TK2MSFTNGP03.phx.gbl...
> You need to put back the model database to where it used to be. The
> reference to the model database is *inside* master.mdf. SQL Server cannot
> start without model since it cannot create tempdb, and SQL Server cannot
> live without tempdb. You probably want to do the same for msdb, and other
> user database, but those will not prohibit SQL Server from starting. You
> really should read KB 224071 first... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "WANNABE" <breichenbach AT istate DOT com> wrote in message
> news:O%23ITWuKvGHA.4460@.TK2MSFTNGP04.phx.gbl...
>> When trying to start SQL 2000 from dos prompt.
>> I changed the start up locations -D -L -E for my server from EM
>> server properties, Moved the Data and log files (MDF and LDFs), then
>> tried to
>> restart the server and it failed. I duplicated all files to their
>> original locations,
>> and again tried to restart from command-line with -d -l but nothing
>> works...
>> When I changed the Server Properties I used capital D, and when I try to
>> start
>> SQL from DOS I get "Invalid command option D."
>> Please help me !! what Have I done to myself
>> Does anyone have any idea what I need to do to get this server backup'
>> Thanks!!
>|||Can you post what you try to execute in the command prompt? Also, the switches to SQL Server
programs are case sensitive.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:e%23rPBuLvGHA.4460@.TK2MSFTNGP05.phx.gbl...
> Thanks, but I do have all dbs in both places, and it still wont start. I try "sqlservr" and it
> returns the "Invalid command option D."
> error
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%23FpPvYLvGHA.428@.TK2MSFTNGP03.phx.gbl...
>> You need to put back the model database to where it used to be. The reference to the model
>> database is *inside* master.mdf. SQL Server cannot start without model since it cannot create
>> tempdb, and SQL Server cannot live without tempdb. You probably want to do the same for msdb, and
>> other user database, but those will not prohibit SQL Server from starting. You really should read
>> KB 224071 first... :-)
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "WANNABE" <breichenbach AT istate DOT com> wrote in message
>> news:O%23ITWuKvGHA.4460@.TK2MSFTNGP04.phx.gbl...
>> When trying to start SQL 2000 from dos prompt.
>> I changed the start up locations -D -L -E for my server from EM
>> server properties, Moved the Data and log files (MDF and LDFs), then tried to
>> restart the server and it failed. I duplicated all files to their original locations,
>> and again tried to restart from command-line with -d -l but nothing works...
>> When I changed the Server Properties I used capital D, and when I try to start
>> SQL from DOS I get "Invalid command option D."
>> Please help me !! what Have I done to myself
>> Does anyone have any idea what I need to do to get this server backup'
>> Thanks!!
>>
>|||I will be gone until next Tuesday.. I'll repost this if I still need help..
All I enter from the command line prompt is
sqlservr
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23dIFp4LvGHA.324@.TK2MSFTNGP06.phx.gbl...
> Can you post what you try to execute in the command prompt? Also, the
> switches to SQL Server programs are case sensitive.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "WANNABE" <breichenbach AT istate DOT com> wrote in message
> news:e%23rPBuLvGHA.4460@.TK2MSFTNGP05.phx.gbl...
>> Thanks, but I do have all dbs in both places, and it still wont start. I
>> try "sqlservr" and it returns the "Invalid command option D."
>> error
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:%23FpPvYLvGHA.428@.TK2MSFTNGP03.phx.gbl...
>> You need to put back the model database to where it used to be. The
>> reference to the model database is *inside* master.mdf. SQL Server
>> cannot start without model since it cannot create tempdb, and SQL Server
>> cannot live without tempdb. You probably want to do the same for msdb,
>> and other user database, but those will not prohibit SQL Server from
>> starting. You really should read KB 224071 first... :-)
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "WANNABE" <breichenbach AT istate DOT com> wrote in message
>> news:O%23ITWuKvGHA.4460@.TK2MSFTNGP04.phx.gbl...
>> When trying to start SQL 2000 from dos prompt.
>> I changed the start up locations -D -L -E for my server from EM
>> server properties, Moved the Data and log files (MDF and LDFs), then
>> tried to
>> restart the server and it failed. I duplicated all files to their
>> original locations,
>> and again tried to restart from command-line with -d -l but nothing
>> works...
>> When I changed the Server Properties I used capital D, and when I try
>> to start
>> SQL from DOS I get "Invalid command option D."
>> Please help me !! what Have I done to myself
>> Does anyone have any idea what I need to do to get this server backup'
>> Thanks!!
>>
>>
>|||If you only run sqlservr from command line, then the parameters are picked up from the registry. I
suggest you edit the registry to put in the right case, d instead of D.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:OspGsOMvGHA.4436@.TK2MSFTNGP05.phx.gbl...
>I will be gone until next Tuesday.. I'll repost this if I still need help..
> All I enter from the command line prompt is
> sqlservr
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%23dIFp4LvGHA.324@.TK2MSFTNGP06.phx.gbl...
>> Can you post what you try to execute in the command prompt? Also, the switches to SQL Server
>> programs are case sensitive.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "WANNABE" <breichenbach AT istate DOT com> wrote in message
>> news:e%23rPBuLvGHA.4460@.TK2MSFTNGP05.phx.gbl...
>> Thanks, but I do have all dbs in both places, and it still wont start. I try "sqlservr" and it
>> returns the "Invalid command option D."
>> error
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%23FpPvYLvGHA.428@.TK2MSFTNGP03.phx.gbl...
>> You need to put back the model database to where it used to be. The reference to the model
>> database is *inside* master.mdf. SQL Server cannot start without model since it cannot create
>> tempdb, and SQL Server cannot live without tempdb. You probably want to do the same for msdb,
>> and other user database, but those will not prohibit SQL Server from starting. You really
>> should read KB 224071 first... :-)
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "WANNABE" <breichenbach AT istate DOT com> wrote in message
>> news:O%23ITWuKvGHA.4460@.TK2MSFTNGP04.phx.gbl...
>> When trying to start SQL 2000 from dos prompt.
>> I changed the start up locations -D -L -E for my server from EM
>> server properties, Moved the Data and log files (MDF and LDFs), then tried to
>> restart the server and it failed. I duplicated all files to their original locations,
>> and again tried to restart from command-line with -d -l but nothing works...
>> When I changed the Server Properties I used capital D, and when I try to start
>> SQL from DOS I get "Invalid command option D."
>> Please help me !! what Have I done to myself
>> Does anyone have any idea what I need to do to get this server backup'
>> Thanks!!
>>
>>
>

"Invalid command option D."

Saturday, February 11, 2012

"Database diagram support object cannot be installed...

...because this database does not have a valid owner. To continue, first use
the Files page of the Database Properties dialog box or the ALTER
AUTHORIZATION statement to set the database owner to a valid login, then add
the database diagram support objects. "
I am getting the previous error when trying to create diagrams in a
database. The database was originally created with a domain user account, but
I ran the script "EXEC sp_changedbowner 'sa'" to change the owner to sa.
Still having problems.
Does anyone know how I could resolve this issue?Are you on SP1? If not, check the compatability mode of the database, it
needs to be set to 90 in RTM for diagrams to work
select compatibility_level
from sys.databases
where name = 'database name'
To alter it use sp_dbcmptlevel e.g.
EXEC sp_dbcmptlevel 'pubs', 90
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:100CF59A-E171-46B7-969A-18DF27AF8AEE@.microsoft.com...
> ...because this database does not have a valid owner. To continue, first
> use
> the Files page of the Database Properties dialog box or the ALTER
> AUTHORIZATION statement to set the database owner to a valid login, then
> add
> the database diagram support objects. "
> I am getting the previous error when trying to create diagrams in a
> database. The database was originally created with a domain user account,
> but
> I ran the script "EXEC sp_changedbowner 'sa'" to change the owner to sa.
> Still having problems.
> Does anyone know how I could resolve this issue?|||That was it! Thank you!
"Jasper Smith" wrote:
> Are you on SP1? If not, check the compatability mode of the database, it
> needs to be set to 90 in RTM for diagrams to work
> select compatibility_level
> from sys.databases
> where name = 'database name'
> To alter it use sp_dbcmptlevel e.g.
> EXEC sp_dbcmptlevel 'pubs', 90
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
>
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:100CF59A-E171-46B7-969A-18DF27AF8AEE@.microsoft.com...
> > ...because this database does not have a valid owner. To continue, first
> > use
> > the Files page of the Database Properties dialog box or the ALTER
> > AUTHORIZATION statement to set the database owner to a valid login, then
> > add
> > the database diagram support objects. "
> >
> > I am getting the previous error when trying to create diagrams in a
> > database. The database was originally created with a domain user account,
> > but
> > I ran the script "EXEC sp_changedbowner 'sa'" to change the owner to sa.
> > Still having problems.
> >
> > Does anyone know how I could resolve this issue?
>
>

"Database diagram support object cannot be installed...

...because this database does not have a valid owner. To continue, first us
e
the Files page of the Database Properties dialog box or the ALTER
AUTHORIZATION statement to set the database owner to a valid login, then add
the database diagram support objects. "
I am getting the previous error when trying to create diagrams in a
database. The database was originally created with a domain user account, bu
t
I ran the script "EXEC sp_changedbowner 'sa'" to change the owner to sa.
Still having problems.
Does anyone know how I could resolve this issue?Are you on SP1? If not, check the compatability mode of the database, it
needs to be set to 90 in RTM for diagrams to work
select compatibility_level
from sys.databases
where name = 'database name'
To alter it use sp_dbcmptlevel e.g.
EXEC sp_dbcmptlevel 'pubs', 90
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:100CF59A-E171-46B7-969A-18DF27AF8AEE@.microsoft.com...
> ...because this database does not have a valid owner. To continue, first
> use
> the Files page of the Database Properties dialog box or the ALTER
> AUTHORIZATION statement to set the database owner to a valid login, then
> add
> the database diagram support objects. "
> I am getting the previous error when trying to create diagrams in a
> database. The database was originally created with a domain user account,
> but
> I ran the script "EXEC sp_changedbowner 'sa'" to change the owner to sa.
> Still having problems.
> Does anyone know how I could resolve this issue?|||That was it! Thank you!
"Jasper Smith" wrote:

> Are you on SP1? If not, check the compatability mode of the database, it
> needs to be set to 90 in RTM for diagrams to work
> select compatibility_level
> from sys.databases
> where name = 'database name'
> To alter it use sp_dbcmptlevel e.g.
> EXEC sp_dbcmptlevel 'pubs', 90
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
>
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:100CF59A-E171-46B7-969A-18DF27AF8AEE@.microsoft.com...
>
>

Friday, January 27, 2012

"Attempt to repair any minor problems." What is the point?

What is the point of having this checkbox on the Database Mainenance Plan
properties (Integrity tab) window?
For the plan to fix minor problems, it requires the db to be in Single User
Mode.
"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
processed. Database needs to be in single user mode."
For the plan to execute it requires SQLAgent to be running.
For SqlAgent to be running, it requires NOT Single User Mode.The message indicates that the *database* needs to be in single-user mode.
This should not be confused with the *server* being in single-user mode.
Personally, I prefer to fix errors manually rather than do this in a
maintenance plan.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Travis" <travis@.c*Y*C*l*Eutah.com> wrote in message
news:%23GMp%238tMEHA.1608@.TK2MSFTNGP12.phx.gbl...
> What is the point of having this checkbox on the Database Mainenance Plan
> properties (Integrity tab) window?
>
> For the plan to fix minor problems, it requires the db to be in Single
User
> Mode.
> "[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
> processed. Database needs to be in single user mode."
> For the plan to execute it requires SQLAgent to be running.
> For SqlAgent to be running, it requires NOT Single User Mode.
>
>|||I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on 31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free space)...
Rebuilding indexes for table 'AccessStatusMap'
......................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628: [Microsoft][ODBC SQL Server Driver][SQL Server]A floating point exception occurred in the user process. Current transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator.
=BFDo Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
>--Original Message--
>What is the point of having this checkbox on the Database Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be running.
>For SqlAgent to be running, it requires NOT Single User Mode.
>
>.
>|||My guess is you have some invalid float data in the table/index. Turn on
trace flag 2570 and run DBCC CHECKTABLE on the table in question. 2570
switches on some extra data range value checking of things like floats and
dates. FYI: this functionality is controlled by documented T-SQL in SQL
Server 2005 rather than a trace flag.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ignacio" <anonymous@.discussions.microsoft.com> wrote in message
news:1bfe01c44737$1dc83550$3501280a@.phx.gbl...
I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free
space)...
Rebuilding indexes for table 'AccessStatusMap'
......................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating
point exception occurred in the user process. Current
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
execution completed. If DBCC printed error messages,
contact your system administrator.
¿Do Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
>--Original Message--
>What is the point of having this checkbox on the Database
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be
running.
>For SqlAgent to be running, it requires NOT Single User
Mode.
>
>.
>

Urgent Please Help - Conserving Page Real Estate

When the page header properties are set as 'PrintOnFirstPage' = False, so
that it doesn't show on the first page, it still seems to take up space on
the first page.
Is there a way to compress this space?
The pseudo report header that I created in the body (to show up only on page
1) is showing up about an inch lower than it really should when the report
renders. I am thinking that this is probably because the page header space
is still being consumed, even though it isn't literally being printed there.
Am I right? Is there a way to conserve that page real estate?
Thanks,
LisaThis is a bug. I don't know of any way to collapse out that space until we
get the bug fixed.
--
My employer's lawyers require me to say:
"This posting is provided 'AS IS' with no warranties, and confers no
rights."
"Lisa" <Lisa.Lambert@._nospam_etalk.com> wrote in message
news:O4ZqFEFZEHA.4092@.TK2MSFTNGP11.phx.gbl...
> When the page header properties are set as 'PrintOnFirstPage' = False, so
> that it doesn't show on the first page, it still seems to take up space on
> the first page.
> Is there a way to compress this space?
> The pseudo report header that I created in the body (to show up only on
page
> 1) is showing up about an inch lower than it really should when the report
> renders. I am thinking that this is probably because the page header
space
> is still being consumed, even though it isn't literally being printed
there.
> Am I right? Is there a way to conserve that page real estate?
> Thanks,
> Lisa
>
>|||Thank you.
"Chris Hays [MSFT]" <chays@.online.microsoft.com> wrote in message
news:u9OQBqFZEHA.3476@.tk2msftngp13.phx.gbl...
> This is a bug. I don't know of any way to collapse out that space until
we
> get the bug fixed.
> --
> My employer's lawyers require me to say:
> "This posting is provided 'AS IS' with no warranties, and confers no
> rights."
> "Lisa" <Lisa.Lambert@._nospam_etalk.com> wrote in message
> news:O4ZqFEFZEHA.4092@.TK2MSFTNGP11.phx.gbl...
> > When the page header properties are set as 'PrintOnFirstPage' = False,
so
> > that it doesn't show on the first page, it still seems to take up space
on
> > the first page.
> > Is there a way to compress this space?
> >
> > The pseudo report header that I created in the body (to show up only on
> page
> > 1) is showing up about an inch lower than it really should when the
report
> > renders. I am thinking that this is probably because the page header
> space
> > is still being consumed, even though it isn't literally being printed
> there.
> > Am I right? Is there a way to conserve that page real estate?
> >
> > Thanks,
> >
> > Lisa
> >
> >
> >
>

Saturday, February 25, 2012

"Maximum Memory" setting in SQL Server properties

"Maximum Memory" setting in SQL Server properties

"Maximum Memory" setting in SQL Server properties

Sunday, February 19, 2012

"Invalid command option D."

"Invalid command option D."

Saturday, February 11, 2012

"Database diagram support object cannot be installed...

"Database diagram support object cannot be installed...

Friday, January 27, 2012

"Attempt to repair any minor problems." What is the point?

Urgent Please Help - Conserving Page Real Estate

sql error

Blog Archive

About Me