Print button doesn't work in ReportServer 2005

I can preview reports on the server fine. The first time I clicked the
print button, I got a message asking me to install SQL Server? I said
yes, then after a few minutes I got a print error.
Now, every time I click the print button on the RS toolbar, I get this
message:
Print Error
An error occured trying to get the current window.
Besides the fact that occurred is spelled wrong, why is this error
happening? I tried deleting all RSClient* files from \Windows\Downloaded
Program Files, but that doesn't help.
How do I fix this?
TIA,
Mike RodriguezCan you try deleting the ActiveX control via IE.
Go to Tools->Internet Options
Click the Settings button
Click the View Objects button.
Delete the RSClientPrint control
I would also clear out my internet cache to make sure you are getting the
latest cab file.
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Rodriguez" <mike@.nospam.com> wrote in message
news:eb%23LX2B$FHA.3636@.TK2MSFTNGP10.phx.gbl...
>I can preview reports on the server fine. The first time I clicked the
>print button, I got a message asking me to install SQL Server? I said
>yes, then after a few minutes I got a print error.
> Now, every time I click the print button on the RS toolbar, I get this
> message:
> Print Error
> An error occured trying to get the current window.
> Besides the fact that occurred is spelled wrong, why is this error
> happening? I tried deleting all RSClient* files from \Windows\Downloaded
> Program Files, but that doesn't help.
> How do I fix this?
> TIA,
> Mike Rodriguez
>|||Hi Daniel,
Ok, I did that. Unfortunately, I still get the same error.
Any other ideas?
Mike
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:eO9RFNC$FHA.216@.TK2MSFTNGP15.phx.gbl...
> Can you try deleting the ActiveX control via IE.
> Go to Tools->Internet Options
> Click the Settings button
> Click the View Objects button.
> Delete the RSClientPrint control
> I would also clear out my internet cache to make sure you are getting the
> latest cab file.
>
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> news:eb%23LX2B$FHA.3636@.TK2MSFTNGP10.phx.gbl...
>>I can preview reports on the server fine. The first time I clicked the
>>print button, I got a message asking me to install SQL Server? I said
>>yes, then after a few minutes I got a print error.
>> Now, every time I click the print button on the RS toolbar, I get this
>> message:
>> Print Error
>> An error occured trying to get the current window.
>> Besides the fact that occurred is spelled wrong, why is this error
>> happening? I tried deleting all RSClient* files from \Windows\Downloaded
>> Program Files, but that doesn't help.
>> How do I fix this?
>> TIA,
>> Mike Rodriguez
>>
>|||Are you viewing reports through a hosted IE control? That is is this a
winforms app or are your going to the ReportServer through IE?
If it is in a hosted win forms then this is expected and the print
functionality is not supported there.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Rodriguez" <mike@.nospam.com> wrote in message
news:etvrvsC$FHA.2036@.TK2MSFTNGP14.phx.gbl...
> Hi Daniel,
> Ok, I did that. Unfortunately, I still get the same error.
> Any other ideas?
> Mike
>
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:eO9RFNC$FHA.216@.TK2MSFTNGP15.phx.gbl...
>> Can you try deleting the ActiveX control via IE.
>> Go to Tools->Internet Options
>> Click the Settings button
>> Click the View Objects button.
>> Delete the RSClientPrint control
>> I would also clear out my internet cache to make sure you are getting the
>> latest cab file.
>>
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> news:eb%23LX2B$FHA.3636@.TK2MSFTNGP10.phx.gbl...
>>I can preview reports on the server fine. The first time I clicked the
>>print button, I got a message asking me to install SQL Server? I said
>>yes, then after a few minutes I got a print error.
>> Now, every time I click the print button on the RS toolbar, I get this
>> message:
>> Print Error
>> An error occured trying to get the current window.
>> Besides the fact that occurred is spelled wrong, why is this error
>> happening? I tried deleting all RSClient* files from
>> \Windows\Downloaded Program Files, but that doesn't help.
>> How do I fix this?
>> TIA,
>> Mike Rodriguez
>>
>>
>|||Hi Daniel,
Actually, the print button works in my winforms app. It doesn't work in the
IE web application that ReportServer created for me.
What can I do?
Mike
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:OwcNYeE$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Are you viewing reports through a hosted IE control? That is is this a
> winforms app or are your going to the ReportServer through IE?
> If it is in a hosted win forms then this is expected and the print
> functionality is not supported there.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> news:etvrvsC$FHA.2036@.TK2MSFTNGP14.phx.gbl...
>> Hi Daniel,
>> Ok, I did that. Unfortunately, I still get the same error.
>> Any other ideas?
>> Mike
>>
>> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> news:eO9RFNC$FHA.216@.TK2MSFTNGP15.phx.gbl...
>> Can you try deleting the ActiveX control via IE.
>> Go to Tools->Internet Options
>> Click the Settings button
>> Click the View Objects button.
>> Delete the RSClientPrint control
>> I would also clear out my internet cache to make sure you are getting
>> the latest cab file.
>>
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> news:eb%23LX2B$FHA.3636@.TK2MSFTNGP10.phx.gbl...
>>I can preview reports on the server fine. The first time I clicked the
>>print button, I got a message asking me to install SQL Server? I said
>>yes, then after a few minutes I got a print error.
>> Now, every time I click the print button on the RS toolbar, I get this
>> message:
>> Print Error
>> An error occured trying to get the current window.
>> Besides the fact that occurred is spelled wrong, why is this error
>> happening? I tried deleting all RSClient* files from
>> \Windows\Downloaded Program Files, but that doesn't help.
>> How do I fix this?
>> TIA,
>> Mike Rodriguez
>>
>>
>>
>

Print and Raiserror

I wanted to give user message from SQL Stored Procedure.
I tried to use PRINT, but it does not go to my MS Access front end
application
I tried to use 'RAISERROR' to send out message, but the message has SQL
server message to my MS Access.
Are there any way to sent message to my front end application user form
stored procedure?
Any information is great appreciated.
Souris,souris wrote:
> I wanted to give user message from SQL Stored Procedure.
> I tried to use PRINT, but it does not go to my MS Access front end
> application
> I tried to use 'RAISERROR' to send out message, but the message has
> SQL server message to my MS Access.
> Are there any way to sent message to my front end application user
> form stored procedure?
> Any information is great appreciated.
> Souris,
You can use RAISERROR. Please post you code to generate the error and
exactly the problem you are seeing with using it. I assume you want to
notify the client app about an error condition and not just a normal
message. Is that correct?
For example, you could use:
RAISERROR ('Job id 1 expects the default level of 10.', 16, 1)
or
RAISERROR ('The level for job_id:%d should be between %d and %d.', 16,
1, @.@.JOB_ID, @.@.MIN_LVL, @.@.MAX_LVL)
David Gugick
Imceda Software
www.imceda.com|||Thanks for the message.
Here is my SQL
BEGIN
RAISERROR('YOU HAVE UPDATE DATA TODAY, IF YOU THINK YOU NEED UPLOAD ONE
MORE TIME PLEASE SEE YOUR ADMINISTRATOR, THANKS', 16, -1)
RETURN
END
The message comes following form my Access front end
Microsoft Access
ODBC - call failer
[Microsoft][ODBC SQL server Driver][SQL Driver]YOU AHVE UPDATE DATA TODAY,
OF YOU THINK YOU NEED UPLOAD ONE MORE TIME PLEASE SEE YOUR ADMINISTARTOR,
THANKS(#50000) [Microsoft][ODBC driver SQL Server][SQL server] Violation of
PRIMARY KEY constaint 'PK_TSC_CMPLD_CALLOUTS', Cannot insert duplicate key
in object 'TSC_CMPLD_CALLOUTS'. (#2627)Microsoft][ODBC SQL server
Driver][SQL Driver]The statement has been terminated.(#3621)[ODBC driver SQL
Server][SQL server] Violation of PRIMARY KEY constaint
'PK_TSC_CMPLD_CALLOUTS', Cannot insert duplicate key in object
'TSC_CMPLD_CALLOUTS'. (#2627)Microsoft][ODBC SQL server Driver][SQL
Driver]The statement has been terminated.(#3621)
How can I give the user message from my stored procedure?
Why my Access front give so much message to user?
Any information is great appreciated.
Thanks again,
Souris,
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23OSTKNfJFHA.1308@.TK2MSFTNGP15.phx.gbl...
> souris wrote:
> You can use RAISERROR. Please post you code to generate the error and
> exactly the problem you are seeing with using it. I assume you want to
> notify the client app about an error condition and not just a normal
> message. Is that correct?
>
> For example, you could use:
> RAISERROR ('Job id 1 expects the default level of 10.', 16, 1)
> or
> RAISERROR ('The level for job_id:%d should be between %d and %d.', 16, 1,
> @.@.JOB_ID, @.@.MIN_LVL, @.@.MAX_LVL)
>
>
> --
> David Gugick
> Imceda Software
> www.imceda.com|||souris wrote:
> Thanks for the message.
> Here is my SQL
> BEGIN
> RAISERROR('YOU HAVE UPDATE DATA TODAY, IF YOU THINK YOU NEED UPLOAD
> ONE MORE TIME PLEASE SEE YOUR ADMINISTRATOR, THANKS', 16, -1)
> RETURN
> END
Sounds like you are generating a lot of errors in whatever SQL you are
running. Try running the SQL with the same parameter values from Query
Analyzer or some other query tool (probably can use Access as well) and
make sure it doesn't generate any errors.
It looks like you are using RAISERROR to return a message. RAISERROR is
for raising errors only, not for messages. I would have the application
display the message on it's own, and not have it generated from the
database.
David Gugick
Imceda Software
www.imceda.com|||Thanks for the message.
My App needs download once and only once per day
The date filed is a part of my primary key.
I wanted to use RAISERROR to raise error and also let user know what
happens.
1. If I use RAISERROR the SQL statement should not continue executing the
rest of SQL, but it seems continues running to violate primary key rule.
2. If I need to write message on front end application then there must be a
way to get rid the [Microsoft ODBC][SQL Server] message from RAISERROR.
Your information is great appreciated
Souris,
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:OTuFBvyJFHA.3552@.TK2MSFTNGP12.phx.gbl...
> souris wrote:
> Sounds like you are generating a lot of errors in whatever SQL you are
> running. Try running the SQL with the same parameter values from Query
> Analyzer or some other query tool (probably can use Access as well) and
> make sure it doesn't generate any errors.
> It looks like you are using RAISERROR to return a message. RAISERROR is
> for raising errors only, not for messages. I would have the application
> display the message on it's own, and not have it generated from the
> database.
> --
> David Gugick
> Imceda Software
> www.imceda.com|||souris wrote:
> Thanks for the message.
> My App needs download once and only once per day
> The date filed is a part of my primary key.
> I wanted to use RAISERROR to raise error and also let user know what
> happens.
> 1. If I use RAISERROR the SQL statement should not continue executing
> the rest of SQL, but it seems continues running to violate primary
> key rule.
> 2. If I need to write message on front end application then there
> must be a way to get rid the [Microsoft ODBC][SQL Server] message
> from RAISERROR.
It looks like the snippet of code you posted should work. You are using
raiserror in a block with a return statement (you should add a return
code). I don't see how the rest of the SQL is being executed unless it
occurred before the raiserror. Can you post the entire procedure?
David Gugick
Imceda Software
www.imceda.com

Print

Hello Guys,

Is it Possible to receive the PRINT Message from a Stored Procedure in the applications?

If no, how SQL Entrerpris Manager receives the print generated from the RESTORE DATABASE WIHT STAT ?

RESTORE DATABASE [dbProdApp]
FROM DISK = N'C:\S_HOMSQL_Db_20030513_dbProdSys_Temp_Manual.ba k'
WITH
FILE = 1,
NOUNLOAD ,
STATS = 10,
RECOVERY ,
REPLACE ,
MOVE N'dbSolomonProdSys_Log' TO N'c:\dbProdSys_Temp_log.ldf',
MOVE N'dbSolomonProdSys_Data' TO N'c:\dbProdSys_Temp.mdf'

Thankxs Everybody!You can mention PRINT statement in the SP to get the information. Refer to books online for PRINT topic.|||BUt I'd like to receive the print messages in a ASP application for example.

Or save the messages in a temporary table.sql

principal to proxy problem

I can successfully execute my package via Business Studio but when I schedule it in SQL Agent I get the error message, 'could not get proxy data for proxy id = 2.' I am trying to execute the scheduled job with that proxy (call it abcd_proxy) because I have a logon id (call it abcd) with access to a specific network drive folder, which holds a required source flat file. The abcd logon is defined as a sysadmin account. I am unable to see that the abcd logon id is an added principal within the abcd_proxy, which I think is because the abcd logon principal has a sysadmin role. My proxy id = 2 definition looks to be defined the same way that my first proxy id was.

Does anyone have an idea about what the message means and how I can fix it?

I had to create a proxy recently to have an SSIS package write a file to a network folder. I am by no means an expert on the subject, but here is what I had to do.

I had to first create a windows account with the right credentials. I then created a credential, a proxy for the credential, and of course set the "Run As" parameter for the step to the proxy. I made sure that the new account was added as a sysadmin in SQL Server, added the account to the "Users" group on the server, as well as to the Logon as batch security policy. When I still had problems with the package being able to read a file it was related to the credentials of the account, which I had the network admin fix. Everything now runs fine.

I apologize if I have stated the obvious to you, but just wanted to share with you all the steps I had to take to perform a task very similar to what you are trying to do. Of course, I had to also use an "absolute" network path and not a mapped drive letter.

Hope this helps.

primary keys have gotten out of sequence

This is a multi-part message in MIME format.
--=_NextPart_000_0013_01C66A18.613BDBB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In Enterprise Manager, my primary keys used to be all in sequence. = After deleting a few pk and adding new ones, they are no longer in = sequence.
In Enterprise Manager, I would like to be able to view "Return all rows" = with the primary keys in numerical order.
What is the best way to accomplish this?
Thank you in advance,
TR
--=_NextPart_000_0013_01C66A18.613BDBB0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
In Enterprise Manager, my primary keys = used to be all in sequence. After deleting a few pk and adding new ones, they = are no longer in sequence.

In Enterprise Manager, I would like to = be able to view "Return all rows" with the primary keys in numerical = order.

What is the best way to accomplish this?

Thank you in advance,
TR
--=_NextPart_000_0013_01C66A18.613BDBB0--Timothy Ross wrote:
> In Enterprise Manager, my primary keys used to be all in sequence. After deleting a few pk and adding new ones, they are no longer in sequence.
> In Enterprise Manager, I would like to be able to view "Return all rows" with the primary keys in numerical order.
> What is the best way to accomplish this?
> Thank you in advance,
> TR
Tables have no inherent order. The only way to fix the order you see is
to use an ORDER BY clause in your SELECT statements. Enterprise Manager
won't do that for you - you need to write your own query. Preferably
use Query Analyzer instead because it's a much more powerful tool.
You'll need to familiarize yourself with SQL syntax first but that's
not so hard for the basic stuff. For example:
SELECT col1, col2, col3, ...
FROM your_table
ORDER BY col1 ;
--
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
--|||David - Thank you for your quick response.
I understand that I can use query analyzer for sorting. I have actually
used Microsoft Access because this will allow sorting very easily.
I also understand that the primary keys really do not need to be displayed
in any particular order.
I have been told there is a command that will re-order my primary keys
sequentially so that I can view them in Enterprise Manager in the correct
order - it has something to do with INDEX on the column, but I haven't found
any information on how to accomplish his.
CREATE INDEX indexname tablename (column) -- doesn't reorder the primary key
the way that I want it to - I was wondering if there was a way to accomplish
this.
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1146170512.392795.12240@.i40g2000cwc.googlegroups.com...
> Timothy Ross wrote:
>> In Enterprise Manager, my primary keys used to be all in sequence. After
>> deleting a few pk and adding new ones, they are no longer in sequence.
>> In Enterprise Manager, I would like to be able to view "Return all rows"
>> with the primary keys in numerical order.
>> What is the best way to accomplish this?
>> Thank you in advance,
>> TR
> Tables have no inherent order. The only way to fix the order you see is
> to use an ORDER BY clause in your SELECT statements. Enterprise Manager
> won't do that for you - you need to write your own query. Preferably
> use Query Analyzer instead because it's a much more powerful tool.
> You'll need to familiarize yourself with SQL syntax first but that's
> not so hard for the basic stuff. For example:
> SELECT col1, col2, col3, ...
> FROM your_table
> ORDER BY col1 ;
> --
> 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
> --
>|||In Enterprise Manager, I just went into "Table indexes and properties" --
verified that my primary key was under the "Column name" and the "Order" was
"Ascending". I then checked "Create as CLUSTERED"
My primary key column is now reordered numerically.
TR
"Timothy Ross" <ross_timothy@.hotmail.com> wrote in message
news:u6ZSyxjaGHA.508@.TK2MSFTNGP02.phx.gbl...
> David - Thank you for your quick response.
> I understand that I can use query analyzer for sorting. I have actually
> used Microsoft Access because this will allow sorting very easily.
> I also understand that the primary keys really do not need to be displayed
> in any particular order.
> I have been told there is a command that will re-order my primary keys
> sequentially so that I can view them in Enterprise Manager in the correct
> order - it has something to do with INDEX on the column, but I haven't
> found any information on how to accomplish his.
> CREATE INDEX indexname tablename (column) -- doesn't reorder the primary
> key the way that I want it to - I was wondering if there was a way to
> accomplish this.
>
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
> news:1146170512.392795.12240@.i40g2000cwc.googlegroups.com...
>> Timothy Ross wrote:
>> In Enterprise Manager, my primary keys used to be all in sequence.
>> After deleting a few pk and adding new ones, they are no longer in
>> sequence.
>> In Enterprise Manager, I would like to be able to view "Return all rows"
>> with the primary keys in numerical order.
>> What is the best way to accomplish this?
>> Thank you in advance,
>> TR
>> Tables have no inherent order. The only way to fix the order you see is
>> to use an ORDER BY clause in your SELECT statements. Enterprise Manager
>> won't do that for you - you need to write your own query. Preferably
>> use Query Analyzer instead because it's a much more powerful tool.
>> You'll need to familiarize yourself with SQL syntax first but that's
>> not so hard for the basic stuff. For example:
>> SELECT col1, col2, col3, ...
>> FROM your_table
>> ORDER BY col1 ;
>> --
>> 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
>> --
>|||Timothy Ross wrote:
> In Enterprise Manager, I just went into "Table indexes and properties" --
> verified that my primary key was under the "Column name" and the "Order" was
> "Ascending". I then checked "Create as CLUSTERED"
> My primary key column is now reordered numerically.
>
You can create a clustered index but all that does is to fix the order
of data as it is stored. This doesn't guarantee that the data will
always be returned in the same order. Although in some cases it may
appear to give that effect you shouldn't rely on it.
--
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
--|||David - I agree that if I delete some of my primary keys and add some new
ones that I would have to do this again to re-order them - it will not be
automatic.
TR
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1146174590.856030.154560@.j73g2000cwa.googlegroups.com...
> Timothy Ross wrote:
>> In Enterprise Manager, I just went into "Table indexes and properties" --
>> verified that my primary key was under the "Column name" and the "Order"
>> was
>> "Ascending". I then checked "Create as CLUSTERED"
>> My primary key column is now reordered numerically.
> You can create a clustered index but all that does is to fix the order
> of data as it is stored. This doesn't guarantee that the data will
> always be returned in the same order. Although in some cases it may
> appear to give that effect you shouldn't rely on it.
> --
> 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
> --
>|||Timothy
This is NOT what David is saying.
There is absolutely no guarantee what order the rows from a table will be
returned, with a clustered index or without one. The only way to be sure
that you get the data in the order you want it is to request it to be sorted
with ORDER BY.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Timothy Ross" <ross_timothy@.hotmail.com> wrote in message
news:eeUdtakaGHA.1192@.TK2MSFTNGP04.phx.gbl...
> David - I agree that if I delete some of my primary keys and add some new
> ones that I would have to do this again to re-order them - it will not be
> automatic.
> TR
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
> news:1146174590.856030.154560@.j73g2000cwa.googlegroups.com...
>> Timothy Ross wrote:
>> In Enterprise Manager, I just went into "Table indexes and
>> properties" --
>> verified that my primary key was under the "Column name" and the "Order"
>> was
>> "Ascending". I then checked "Create as CLUSTERED"
>> My primary key column is now reordered numerically.
>>
>> You can create a clustered index but all that does is to fix the order
>> of data as it is stored. This doesn't guarantee that the data will
>> always be returned in the same order. Although in some cases it may
>> appear to give that effect you shouldn't rely on it.
>> --
>> 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
>> --
>|||Not sure what you are talking about - I did order the rows -- verified that
my primary key was under the "Column name" and the "Order" was
"Ascending"
This re-ordered my primary key column numerically.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:e761cnkaGHA.3720@.TK2MSFTNGP03.phx.gbl...
> Timothy
> This is NOT what David is saying.
> There is absolutely no guarantee what order the rows from a table will be
> returned, with a clustered index or without one. The only way to be sure
> that you get the data in the order you want it is to request it to be
> sorted with ORDER BY.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Timothy Ross" <ross_timothy@.hotmail.com> wrote in message
> news:eeUdtakaGHA.1192@.TK2MSFTNGP04.phx.gbl...
>> David - I agree that if I delete some of my primary keys and add some new
>> ones that I would have to do this again to re-order them - it will not be
>> automatic.
>> TR
>> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
>> news:1146174590.856030.154560@.j73g2000cwa.googlegroups.com...
>> Timothy Ross wrote:
>> In Enterprise Manager, I just went into "Table indexes and
>> properties" --
>> verified that my primary key was under the "Column name" and the
>> "Order" was
>> "Ascending". I then checked "Create as CLUSTERED"
>> My primary key column is now reordered numerically.
>>
>> You can create a clustered index but all that does is to fix the order
>> of data as it is stored. This doesn't guarantee that the data will
>> always be returned in the same order. Although in some cases it may
>> appear to give that effect you shouldn't rely on it.
>> --
>> 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 guess I misunderstood what you were talking about. I don't see how you can
have the primary key column NOT in order if you use ORDER BY when retrieving
the data.
But if you're satisfied, that's fine (for now).
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Timothy Ross" <ross_timothy@.hotmail.com> wrote in message
news:eozjgWtaGHA.3720@.TK2MSFTNGP03.phx.gbl...
> Not sure what you are talking about - I did order the rows -- verified
> that my primary key was under the "Column name" and the "Order" was
> "Ascending"
> This re-ordered my primary key column numerically.
>
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:e761cnkaGHA.3720@.TK2MSFTNGP03.phx.gbl...
>> Timothy
>> This is NOT what David is saying.
>> There is absolutely no guarantee what order the rows from a table will be
>> returned, with a clustered index or without one. The only way to be sure
>> that you get the data in the order you want it is to request it to be
>> sorted with ORDER BY.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.solidqualitylearning.com
>>
>> "Timothy Ross" <ross_timothy@.hotmail.com> wrote in message
>> news:eeUdtakaGHA.1192@.TK2MSFTNGP04.phx.gbl...
>> David - I agree that if I delete some of my primary keys and add some
>> new ones that I would have to do this again to re-order them - it will
>> not be automatic.
>> TR
>> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
>> news:1146174590.856030.154560@.j73g2000cwa.googlegroups.com...
>> Timothy Ross wrote:
>> In Enterprise Manager, I just went into "Table indexes and
>> properties" --
>> verified that my primary key was under the "Column name" and the
>> "Order" was
>> "Ascending". I then checked "Create as CLUSTERED"
>> My primary key column is now reordered numerically.
>>
>> You can create a clustered index but all that does is to fix the order
>> of data as it is stored. This doesn't guarantee that the data will
>> always be returned in the same order. Although in some cases it may
>> appear to give that effect you shouldn't rely on it.
>> --
>> 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
>> --
>>
>>
>|||On Thu, 27 Apr 2006 16:52:04 -0400, "Timothy Ross"
<ross_timothy@.hotmail.com> wrote:
>I have been told there is a command that will re-order my primary keys
>sequentially so that I can view them in Enterprise Manager in the correct
>order - it has something to do with INDEX on the column, but I haven't found
>any information on how to accomplish his.
If you have a clustered index (or primary key) on the table, then the
physical and logical order will be the same.
But even then, a select statement without an order-by does not seem to
guarantee things will display in order. Just why not, I do not really
understand. May have to do with reuse of freed pages and order of
insertion, so the logical and physical *page* order are not the same,
irrespective of the logical and physical *row* orders.
Josh|||> But even then, a select statement without an order-by does not seem to
> guarantee things will display in order. Just why not, I do not really
> understand. May have to do with reuse of freed pages and order of
> insertion, so the logical and physical *page* order are not the same,
> irrespective of the logical and physical *row* orders.
SQL Server is free to return data in any sequence (e.g. most efficient
manner) unless the query contains ORDER BY. For example, there is a
'merry-go-round' scan feature that allows multiple concurrent queries to
'piggyback' on a scan already in progress. Once the later queries retrieve
the last row, the scan resumes at the beginning and continues until the
initially retrieved row is encountered. This could result in rows returned
in an arbitrary order.
It's good to have an understanding of the physical implementation for
performance analysis. However, you can rely only on the result described by
the SQL query.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"JXStern" <JXSternChangeX2R@.gte.net> wrote in message
news:gb88529oa6vkkdom9dgbtv9gfhhkh16u7e@.4ax.com...
> On Thu, 27 Apr 2006 16:52:04 -0400, "Timothy Ross"
> <ross_timothy@.hotmail.com> wrote:
>>I have been told there is a command that will re-order my primary keys
>>sequentially so that I can view them in Enterprise Manager in the correct
>>order - it has something to do with INDEX on the column, but I haven't
>>found
>>any information on how to accomplish his.
> If you have a clustered index (or primary key) on the table, then the
> physical and logical order will be the same.
> But even then, a select statement without an order-by does not seem to
> guarantee things will display in order. Just why not, I do not really
> understand. May have to do with reuse of freed pages and order of
> insertion, so the logical and physical *page* order are not the same,
> irrespective of the logical and physical *row* orders.
> Josh
>sql

Primary Key problems

Hi there,

I just tried to apply a set of primary keys to a table and after a
very long time (like an hour or more) i got this error message ...

Unable to create index 'PK_master_data'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]CREATE
UNIQUE INDEX terminated because a duplicate key was found for index ID
1. Most significant primary key is '2050500'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not create
constraint. See previous errors.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
terminated.

.... i am new to sqlserver ... is this saying to me that i have a
duplicate record? because when i query the recordset for duplicate
records i get none!

please help ASAP.

Thanks

Mogitcumming@.smorgonsteel.com.au (mogi) wrote in message news:<d1729549.0401272220.49ea5ee6@.posting.google.com>...
> Hi there,
> I just tried to apply a set of primary keys to a table and after a
> very long time (like an hour or more) i got this error message ...
> Unable to create index 'PK_master_data'.
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]CREATE
> UNIQUE INDEX terminated because a duplicate key was found for index ID
> 1. Most significant primary key is '2050500'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not create
> constraint. See previous errors.
> [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
> terminated.
> ... i am new to sqlserver ... is this saying to me that i have a
> duplicate record? because when i query the recordset for duplicate
> records i get none!
> please help ASAP.
> Thanks
> Mogi

Yes, there are duplicates. How are you querying the recordset for
them? A query like this should find them:

select PrimaryKeyColumn, count(*)
from dbo.MyTable
group by PrimaryKeyColumn
having count(*) > 1

Simon

PRIMARY filegroup is full?

Error Message
- Task reported failure on execution (SQL DTS). Could not allocate space for
object 'TABLE_EMPLOYEE' in database 'Employee' because the 'PRIMARY
filegroup is full.
SQL Server Info
- SQL Server 2000 Standard Edition
- Intel Xeon 3.06 GHz
- 60 GB HDD
Database Properties
- Size 2,426.69 MB
- Space available 1,047.60 MB
- Data files is automatically grow file and unrestricted file growth
- Transaction Log is automatically grow file and unrestricted file growth
- Filegroups is PRIMARY
Please help.Sam wrote:
> Error Message
> - Task reported failure on execution (SQL DTS). Could not allocate
> space for object 'TABLE_EMPLOYEE' in database 'Employee' because the
> 'PRIMARY filegroup is full.
> SQL Server Info
> - SQL Server 2000 Standard Edition
> - Intel Xeon 3.06 GHz
> - 60 GB HDD
> Database Properties
> - Size 2,426.69 MB
> - Space available 1,047.60 MB
> - Data files is automatically grow file and unrestricted file growth
> - Transaction Log is automatically grow file and unrestricted file
> growth
> - Filegroups is PRIMARY
> Please help.
Could you be running a very large task using DTS that is causing the log
file and data file growth to fill up that last gigbyte of space? Can you
move the log to another drive with more space? How big is the log now?
Can you backup the database or truncate the log file if it's too large?
--
David G.|||The data file (employee.mdf) is 1,872 MB.
The transactiona log (employee.ldf) is 556MB.
"David G." <david_nospam@.nospam.com> wrote in message
news:eGF$l40gEHA.3348@.TK2MSFTNGP12.phx.gbl...
> Sam wrote:
>> Error Message
>> - Task reported failure on execution (SQL DTS). Could not allocate
>> space for object 'TABLE_EMPLOYEE' in database 'Employee' because the
>> 'PRIMARY filegroup is full.
>> SQL Server Info
>> - SQL Server 2000 Standard Edition
>> - Intel Xeon 3.06 GHz
>> - 60 GB HDD
>> Database Properties
>> - Size 2,426.69 MB
>> - Space available 1,047.60 MB
>> - Data files is automatically grow file and unrestricted file growth
>> - Transaction Log is automatically grow file and unrestricted file
>> growth
>> - Filegroups is PRIMARY
>> Please help.
> Could you be running a very large task using DTS that is causing the log
> file and data file growth to fill up that last gigbyte of space? Can you
> move the log to another drive with more space? How big is the log now?
> Can you backup the database or truncate the log file if it's too large?
> --
> David G.
>|||sometime files doesn't grow fast enough, so you get this "database is full" message. I suggest you
pre-allocate storage (also good for performance reasons).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Sam" <cybersam88@.hotmail.com> wrote in message news:u7mxWB0gEHA.2984@.tk2msftngp13.phx.gbl...
> Error Message
> - Task reported failure on execution (SQL DTS). Could not allocate space for
> object 'TABLE_EMPLOYEE' in database 'Employee' because the 'PRIMARY
> filegroup is full.
> SQL Server Info
> - SQL Server 2000 Standard Edition
> - Intel Xeon 3.06 GHz
> - 60 GB HDD
> Database Properties
> - Size 2,426.69 MB
> - Space available 1,047.60 MB
> - Data files is automatically grow file and unrestricted file growth
> - Transaction Log is automatically grow file and unrestricted file growth
> - Filegroups is PRIMARY
> Please help.
>|||Notice that SQL Server 2000 is only permitted 2GB per database.
Therefore, the database shrinked and able to update via SQL DTS.
Could it add more data files into single database so that each of it consist
2GB?
Please advise.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OrPpO22gEHA.216@.tk2msftngp13.phx.gbl...
> sometime files doesn't grow fast enough, so you get this "database is
full" message. I suggest you
> pre-allocate storage (also good for performance reasons).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Sam" <cybersam88@.hotmail.com> wrote in message
news:u7mxWB0gEHA.2984@.tk2msftngp13.phx.gbl...
> > Error Message
> > - Task reported failure on execution (SQL DTS). Could not allocate space
for
> > object 'TABLE_EMPLOYEE' in database 'Employee' because the 'PRIMARY
> > filegroup is full.
> >
> > SQL Server Info
> > - SQL Server 2000 Standard Edition
> > - Intel Xeon 3.06 GHz
> > - 60 GB HDD
> >
> > Database Properties
> > - Size 2,426.69 MB
> > - Space available 1,047.60 MB
> > - Data files is automatically grow file and unrestricted file growth
> > - Transaction Log is automatically grow file and unrestricted file
growth
> > - Filegroups is PRIMARY
> >
> > Please help.
> >
> >
>|||SQL Server support about 1 million TB size for database. Each file can be 32 TB.
However, MSDE has max size of 2GB for data (transaction log not included). Sam doesn't appear to be
running MSDE as data size is already over 2GB.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Sam" <cybersam88@.hotmail.com> wrote in message news:uJOd3n4gEHA.1392@.TK2MSFTNGP11.phx.gbl...
> Notice that SQL Server 2000 is only permitted 2GB per database.
> Therefore, the database shrinked and able to update via SQL DTS.
> Could it add more data files into single database so that each of it consist
> 2GB?
> Please advise.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:OrPpO22gEHA.216@.tk2msftngp13.phx.gbl...
> > sometime files doesn't grow fast enough, so you get this "database is
> full" message. I suggest you
> > pre-allocate storage (also good for performance reasons).
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Sam" <cybersam88@.hotmail.com> wrote in message
> news:u7mxWB0gEHA.2984@.tk2msftngp13.phx.gbl...
> > > Error Message
> > > - Task reported failure on execution (SQL DTS). Could not allocate space
> for
> > > object 'TABLE_EMPLOYEE' in database 'Employee' because the 'PRIMARY
> > > filegroup is full.
> > >
> > > SQL Server Info
> > > - SQL Server 2000 Standard Edition
> > > - Intel Xeon 3.06 GHz
> > > - 60 GB HDD
> > >
> > > Database Properties
> > > - Size 2,426.69 MB
> > > - Space available 1,047.60 MB
> > > - Data files is automatically grow file and unrestricted file growth
> > > - Transaction Log is automatically grow file and unrestricted file
> growth
> > > - Filegroups is PRIMARY
> > >
> > > Please help.
> > >
> > >
> >
> >
>|||I'm using SQL Server 2000 Standard Edition and how much the size of database
(MDF)?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eK5e8A5gEHA.3992@.TK2MSFTNGP11.phx.gbl...
> SQL Server support about 1 million TB size for database. Each file can be
> 32 TB.
> However, MSDE has max size of 2GB for data (transaction log not included).
> Sam doesn't appear to be
> running MSDE as data size is already over 2GB.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Sam" <cybersam88@.hotmail.com> wrote in message
> news:uJOd3n4gEHA.1392@.TK2MSFTNGP11.phx.gbl...
>> Notice that SQL Server 2000 is only permitted 2GB per database.
>> Therefore, the database shrinked and able to update via SQL DTS.
>> Could it add more data files into single database so that each of it
>> consist
>> 2GB?
>> Please advise.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in
>> message news:OrPpO22gEHA.216@.tk2msftngp13.phx.gbl...
>> > sometime files doesn't grow fast enough, so you get this "database is
>> full" message. I suggest you
>> > pre-allocate storage (also good for performance reasons).
>> >
>> > --
>> > Tibor Karaszi, SQL Server MVP
>> > http://www.karaszi.com/sqlserver/default.asp
>> > http://www.solidqualitylearning.com/
>> >
>> >
>> > "Sam" <cybersam88@.hotmail.com> wrote in message
>> news:u7mxWB0gEHA.2984@.tk2msftngp13.phx.gbl...
>> > > Error Message
>> > > - Task reported failure on execution (SQL DTS). Could not allocate
>> > > space
>> for
>> > > object 'TABLE_EMPLOYEE' in database 'Employee' because the 'PRIMARY
>> > > filegroup is full.
>> > >
>> > > SQL Server Info
>> > > - SQL Server 2000 Standard Edition
>> > > - Intel Xeon 3.06 GHz
>> > > - 60 GB HDD
>> > >
>> > > Database Properties
>> > > - Size 2,426.69 MB
>> > > - Space available 1,047.60 MB
>> > > - Data files is automatically grow file and unrestricted file growth
>> > > - Transaction Log is automatically grow file and unrestricted file
>> growth
>> > > - Filegroups is PRIMARY
>> > >
>> > > Please help.
>> > >
>> > >
>> >
>> >
>>
>|||In SQL Server 2000 Standard Edition, max size for an mdf file is 32 TB.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Sam" <cybersam88@.hotmail.com> wrote in message news:eBe7WmBhEHA.3612@.TK2MSFTNGP12.phx.gbl...
> I'm using SQL Server 2000 Standard Edition and how much the size of database
> (MDF)?
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:eK5e8A5gEHA.3992@.TK2MSFTNGP11.phx.gbl...
> > SQL Server support about 1 million TB size for database. Each file can be
> > 32 TB.
> >
> > However, MSDE has max size of 2GB for data (transaction log not included).
> > Sam doesn't appear to be
> > running MSDE as data size is already over 2GB.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Sam" <cybersam88@.hotmail.com> wrote in message
> > news:uJOd3n4gEHA.1392@.TK2MSFTNGP11.phx.gbl...
> >> Notice that SQL Server 2000 is only permitted 2GB per database.
> >> Therefore, the database shrinked and able to update via SQL DTS.
> >>
> >> Could it add more data files into single database so that each of it
> >> consist
> >> 2GB?
> >>
> >> Please advise.
> >>
> >>
> >> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> >> in
> >> message news:OrPpO22gEHA.216@.tk2msftngp13.phx.gbl...
> >> > sometime files doesn't grow fast enough, so you get this "database is
> >> full" message. I suggest you
> >> > pre-allocate storage (also good for performance reasons).
> >> >
> >> > --
> >> > Tibor Karaszi, SQL Server MVP
> >> > http://www.karaszi.com/sqlserver/default.asp
> >> > http://www.solidqualitylearning.com/
> >> >
> >> >
> >> > "Sam" <cybersam88@.hotmail.com> wrote in message
> >> news:u7mxWB0gEHA.2984@.tk2msftngp13.phx.gbl...
> >> > > Error Message
> >> > > - Task reported failure on execution (SQL DTS). Could not allocate
> >> > > space
> >> for
> >> > > object 'TABLE_EMPLOYEE' in database 'Employee' because the 'PRIMARY
> >> > > filegroup is full.
> >> > >
> >> > > SQL Server Info
> >> > > - SQL Server 2000 Standard Edition
> >> > > - Intel Xeon 3.06 GHz
> >> > > - 60 GB HDD
> >> > >
> >> > > Database Properties
> >> > > - Size 2,426.69 MB
> >> > > - Space available 1,047.60 MB
> >> > > - Data files is automatically grow file and unrestricted file growth
> >> > > - Transaction Log is automatically grow file and unrestricted file
> >> growth
> >> > > - Filegroups is PRIMARY
> >> > >
> >> > > Please help.
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
>

Primary filegroup is full.

I seem to be having problems with a very simple install of MSDE on a
Windows 2000 Server. When attempting to add new records, I receive
the message "Could not allocate space for object 'MyTable' in database
'MyDatabase' because the 'PRIMARY' filegroup is full."

I have dealt with countless issues like this in the past and they have
been easily resolved due to max limit of MSDE, trans log full, or the
hard drive where the database is stored is full. None of these appear
to be the case in this instance. The system has been working fine for
about a year.

The Master database is 11 MB. MyDatabase is 33 MB. The log files are
both under 1 MB. I have 730 MB of storage available on the drive
where the database is stored.

I downloaded MSDE off of Microsoft's website and installed with the
following switches: BLANKSAPWD=1 SECURITYMODE=SQL. I create a user
in MSDE that is the DBO for MyDatabase. Other than that, I make no
changes to the default installation.Giadis (lonewolf3557@.hotmail.com) writes:
> I seem to be having problems with a very simple install of MSDE on a
> Windows 2000 Server. When attempting to add new records, I receive
> the message "Could not allocate space for object 'MyTable' in database
> 'MyDatabase' because the 'PRIMARY' filegroup is full."
> I have dealt with countless issues like this in the past and they have
> been easily resolved due to max limit of MSDE, trans log full, or the
> hard drive where the database is stored is full. None of these appear
> to be the case in this instance. The system has been working fine for
> about a year.
> The Master database is 11 MB. MyDatabase is 33 MB. The log files are
> both under 1 MB. I have 730 MB of storage available on the drive
> where the database is stored.

Have you verified with sp_helpdb that the database has "Unlimited" in
maxsize and 10% in Growth? These are values in the second result set.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

'PRIMARY' filegroup is full

Hi,
In our development server, when we tried to insert some large data we had
this error message -
.......................
SQL error description: [Microsoft][ODBC SQL Server Driver][SQL Server]Could
not allocate space for object '<TABLE NAME>' in database '<DATABASE>' because
the 'PRIMARY' filegroup is full.
.......................
The file property 'Automatically grow file' is selected for both data and
log file. Again maxsize is unlimited with growth set to 10% for both files.
How can I resolve this issue? Can someone let me know please.
Many thanks in advance,
Harish Mohanbabu
MBS Axapta - MVP
http://www.harishm.com/
Harish
Are you sure there is enough disk space?
If you are, it is probably during the insertion autogow feature kicks in and
you've got the error.
Try update statistics and not inserting a large amount of data, instead
divide the transaction into a small one
"Harish Mohanbabu" <Axapta@.online.nospam> wrote in message
news:3D9837CC-C9FE-4773-9145-601C1C4F2A98@.microsoft.com...
> Hi,
> In our development server, when we tried to insert some large data we had
> this error message -
> ......................
> SQL error description: [Microsoft][ODBC SQL Server Driver][SQL
> Server]Could
> not allocate space for object '<TABLE NAME>' in database '<DATABASE>'
> because
> the 'PRIMARY' filegroup is full.
> ......................
> The file property 'Automatically grow file' is selected for both data and
> log file. Again maxsize is unlimited with growth set to 10% for both
> files.
> How can I resolve this issue? Can someone let me know please.
> Many thanks in advance,
> Harish Mohanbabu
> --
> MBS Axapta - MVP
> http://www.harishm.com/
|||Hi Uri,
Thanks for your response.
Well - there is plenty of hard disk space (approx 50 GB). And I am afraid I
can't break the data any further than this.
BTW, I just tried increasing space allowed to the data file. Do you think
this will make any difference? Meanwhile I will try to do the import once
again and see how it goes.
Regards,
Harish Mohanbabu
MBS Axapta - MVP
http://www.harishm.com/
"Uri Dimant" wrote:

> Harish
> Are you sure there is enough disk space?
> If you are, it is probably during the insertion autogow feature kicks in and
> you've got the error.
> Try update statistics and not inserting a large amount of data, instead
> divide the transaction into a small one
|||After increasing the space allowed, I tried pushing quite some volume of
data. Looks like this did the trick. Now it is working fine again!
Harish Mohanbabu
MBS Axapta - MVP
http://www.harishm.com/
"Harish Mohanbabu" wrote:

> Hi Uri,
> Thanks for your response.
> Well - there is plenty of hard disk space (approx 50 GB). And I am afraid I
> can't break the data any further than this.
> BTW, I just tried increasing space allowed to the data file. Do you think
> this will make any difference? Meanwhile I will try to do the import once
> again and see how it goes.
> Regards,
> Harish Mohanbabu
> --
> MBS Axapta - MVP
> http://www.harishm.com/
|||If you get a timeout during autogrow, the autogrow that had occurred will be rolled back. End result
is that it appears that autogrow doesn't work.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Harish Mohanbabu" <Axapta@.online.nospam> wrote in message
news:10C9E60A-4823-44B3-9D28-0B1172B8627F@.microsoft.com...[vbcol=seagreen]
> After increasing the space allowed, I tried pushing quite some volume of
> data. Looks like this did the trick. Now it is working fine again!
> Harish Mohanbabu
> --
> MBS Axapta - MVP
> http://www.harishm.com/
> "Harish Mohanbabu" wrote:
|||Hello,
Based on my research, generally this error occurs when the amount of time
SQL server was taking to expand the file exceeded the allowed time built-in
and thus the
error. We can resolve the issue by setting the increment to be larger or
increase the database data file.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

'PRIMARY' filegroup is full

Hi,
In our development server, when we tried to insert some large data we had
this error message -
......................
SQL error description: [Microsoft][ODBC SQL Server Driver][SQL S
erver]Could
not allocate space for object '<TABLE NAME>' in database '<DATABASE>' becaus
e
the 'PRIMARY' filegroup is full.
......................
The file property 'Automatically grow file' is selected for both data and
log file. Again maxsize is unlimited with growth set to 10% for both files.
How can I resolve this issue? Can someone let me know please.
Many thanks in advance,
Harish Mohanbabu
--
MBS Axapta - MVP
http://www.harishm.com/Harish
Are you sure there is enough disk space?
If you are, it is probably during the insertion autogow feature kicks in and
you've got the error.
Try update statistics and not inserting a large amount of data, instead
divide the transaction into a small one
"Harish Mohanbabu" <Axapta@.online.nospam> wrote in message
news:3D9837CC-C9FE-4773-9145-601C1C4F2A98@.microsoft.com...
> Hi,
> In our development server, when we tried to insert some large data we had
> this error message -
> ......................
> SQL error description: [Microsoft][ODBC SQL Server Driver][SQL
> Server]Could
> not allocate space for object '<TABLE NAME>' in database '<DATABASE>'
> because
> the 'PRIMARY' filegroup is full.
> ......................
> The file property 'Automatically grow file' is selected for both data and
> log file. Again maxsize is unlimited with growth set to 10% for both
> files.
> How can I resolve this issue? Can someone let me know please.
> Many thanks in advance,
> Harish Mohanbabu
> --
> MBS Axapta - MVP
> http://www.harishm.com/|||Hi Uri,
Thanks for your response.
Well - there is plenty of hard disk space (approx 50 GB). And I am afraid I
can't break the data any further than this.
BTW, I just tried increasing space allowed to the data file. Do you think
this will make any difference? Meanwhile I will try to do the import once
again and see how it goes.
Regards,
Harish Mohanbabu
--
MBS Axapta - MVP
http://www.harishm.com/
"Uri Dimant" wrote:

> Harish
> Are you sure there is enough disk space?
> If you are, it is probably during the insertion autogow feature kicks in a
nd
> you've got the error.
> Try update statistics and not inserting a large amount of data, instead
> divide the transaction into a small one|||After increasing the space allowed, I tried pushing quite some volume of
data. Looks like this did the trick. Now it is working fine again!
Harish Mohanbabu
--
MBS Axapta - MVP
http://www.harishm.com/
"Harish Mohanbabu" wrote:

> Hi Uri,
> Thanks for your response.
> Well - there is plenty of hard disk space (approx 50 GB). And I am afraid
I
> can't break the data any further than this.
> BTW, I just tried increasing space allowed to the data file. Do you think
> this will make any difference? Meanwhile I will try to do the import once
> again and see how it goes.
> Regards,
> Harish Mohanbabu
> --
> MBS Axapta - MVP
> http://www.harishm.com/|||If you get a timeout during autogrow, the autogrow that had occurred will be
rolled back. End result
is that it appears that autogrow doesn't work.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Harish Mohanbabu" <Axapta@.online.nospam> wrote in message
news:10C9E60A-4823-44B3-9D28-0B1172B8627F@.microsoft.com...[vbcol=seagreen]
> After increasing the space allowed, I tried pushing quite some volume of
> data. Looks like this did the trick. Now it is working fine again!
> Harish Mohanbabu
> --
> MBS Axapta - MVP
> http://www.harishm.com/
> "Harish Mohanbabu" wrote:
>|||Hello,
Based on my research, generally this error occurs when the amount of time
SQL server was taking to expand the file exceeded the allowed time built-in
and thus the
error. We can resolve the issue by setting the increment to be larger or
increase the database data file.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

'PRIMARY' filegroup is full

Hi,
In our development server, when we tried to insert some large data we had
this error message -
......................
SQL error description: [Microsoft][ODBC SQL Server Driver][SQL Server]Could
not allocate space for object '<TABLE NAME>' in database '<DATABASE>' because
the 'PRIMARY' filegroup is full.
......................
The file property 'Automatically grow file' is selected for both data and
log file. Again maxsize is unlimited with growth set to 10% for both files.
How can I resolve this issue? Can someone let me know please.
Many thanks in advance,
Harish Mohanbabu
--
MBS Axapta - MVP
http://www.harishm.com/Harish
Are you sure there is enough disk space?
If you are, it is probably during the insertion autogow feature kicks in and
you've got the error.
Try update statistics and not inserting a large amount of data, instead
divide the transaction into a small one
"Harish Mohanbabu" <Axapta@.online.nospam> wrote in message
news:3D9837CC-C9FE-4773-9145-601C1C4F2A98@.microsoft.com...
> Hi,
> In our development server, when we tried to insert some large data we had
> this error message -
> ......................
> SQL error description: [Microsoft][ODBC SQL Server Driver][SQL
> Server]Could
> not allocate space for object '<TABLE NAME>' in database '<DATABASE>'
> because
> the 'PRIMARY' filegroup is full.
> ......................
> The file property 'Automatically grow file' is selected for both data and
> log file. Again maxsize is unlimited with growth set to 10% for both
> files.
> How can I resolve this issue? Can someone let me know please.
> Many thanks in advance,
> Harish Mohanbabu
> --
> MBS Axapta - MVP
> http://www.harishm.com/|||Hi Uri,
Thanks for your response.
Well - there is plenty of hard disk space (approx 50 GB). And I am afraid I
can't break the data any further than this.
BTW, I just tried increasing space allowed to the data file. Do you think
this will make any difference? Meanwhile I will try to do the import once
again and see how it goes.
Regards,
Harish Mohanbabu
--
MBS Axapta - MVP
http://www.harishm.com/
"Uri Dimant" wrote:
> Harish
> Are you sure there is enough disk space?
> If you are, it is probably during the insertion autogow feature kicks in and
> you've got the error.
> Try update statistics and not inserting a large amount of data, instead
> divide the transaction into a small one|||After increasing the space allowed, I tried pushing quite some volume of
data. Looks like this did the trick. Now it is working fine again!
Harish Mohanbabu
--
MBS Axapta - MVP
http://www.harishm.com/
"Harish Mohanbabu" wrote:
> Hi Uri,
> Thanks for your response.
> Well - there is plenty of hard disk space (approx 50 GB). And I am afraid I
> can't break the data any further than this.
> BTW, I just tried increasing space allowed to the data file. Do you think
> this will make any difference? Meanwhile I will try to do the import once
> again and see how it goes.
> Regards,
> Harish Mohanbabu
> --
> MBS Axapta - MVP
> http://www.harishm.com/|||If you get a timeout during autogrow, the autogrow that had occurred will be rolled back. End result
is that it appears that autogrow doesn't work.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Harish Mohanbabu" <Axapta@.online.nospam> wrote in message
news:10C9E60A-4823-44B3-9D28-0B1172B8627F@.microsoft.com...
> After increasing the space allowed, I tried pushing quite some volume of
> data. Looks like this did the trick. Now it is working fine again!
> Harish Mohanbabu
> --
> MBS Axapta - MVP
> http://www.harishm.com/
> "Harish Mohanbabu" wrote:
>> Hi Uri,
>> Thanks for your response.
>> Well - there is plenty of hard disk space (approx 50 GB). And I am afraid I
>> can't break the data any further than this.
>> BTW, I just tried increasing space allowed to the data file. Do you think
>> this will make any difference? Meanwhile I will try to do the import once
>> again and see how it goes.
>> Regards,
>> Harish Mohanbabu
>> --
>> MBS Axapta - MVP
>> http://www.harishm.com/|||Hello,
Based on my research, generally this error occurs when the amount of time
SQL server was taking to expand the file exceeded the allowed time built-in
and thus the
error. We can resolve the issue by setting the increment to be larger or
increase the database data file.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Primary File Group Full

Weird. I have an Agent job that populates some warehouse data every night. It's been working fine for over a year. Then it fails with a message that thePRIMARY file group is full. The database is set to Simple recovery, automatic, unrestricted growth by 10% for both the log file and the data file. The drive it's on has 96GB free. The data file is 1.5GB and the log is 2MB and there's not very much fluctuation in the amoutn of data going into it.

Anybody have an idea why that would happen?

Thanks for any insight,
Pete

You're probably timing out when it hits the autogrow. As ageneral rule, you should never rely on auto-growth! Instead, keepyour databases a lot bigger than you think you'll need. And setthe auto-grow rate to a very small amount (maybe 5-10 megs, some amountthat can grow within a few seconds). You have 96 GB free on thedrive -- why not set your databases to 10 or 20 GB?
And make sure you keep an eye on them. Keep growing them as they fill up.

|||

That's what I suspected since all the settings appear correct and the only activity in the job is just a huge number of inserts. I figured that at the point of needing to grow, there's a pile-up of inserts trying to happen. The problem with increasing the size significantly is that it's anything but the most important database on that server and I wouldn't want to limit the others just for this one. I can give it a little boost, though. Thanks for the help.

Pete

|||At the least, set a smaller auto-grow threshold so that it won't haveto wait -- it should take very little time to grow 5 or 10 megs. Note that this can contribute to fragmentation, which is why I suggestgrowing manually, in much larger chunks.

Preview Error

Hi all,

I am all the time receiving this arror message:

TITLE: Microsoft Report Designer

A connection cannot be made to the database.
Set and test the connection string.

ADDITIONAL INFORMATION:

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)

What should i do?

Thanks

Hi,

you are trying to logon with your datasource object as a SQL Server login, but your SQL Server doesn′t accept mixed (this includes SQL Server as well as Windows) authentication. So either switch your server to mixed authentication or switch your datasource objects security context to Windows (Integrated) Authentication.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de