Internet integration: design

Showing posts with label design. Show all posts

Friday, March 30, 2012

Invisible controls durig runtime

Hi,
Do you know why when I run my ssis packages in the dev machine, the diagrams are not visible during run time.
I can design the package but not sure why when I start the package, the diagrams in the control flow can not be viewed.
Please note that if I do this on the server, I can see the diagrams during run time.

Thanks

The controls or the diagram indicating the control/data flows? You change nouns between the subject and the body of this post. ("controls" versus "diagrams")

If the latter, are you sure you don't just need to scroll to the left, up, down, or to the right to see them?|||

Hi,

I mean the controls such as flat file source, ...

Thanks

Wednesday, March 28, 2012

Inventory Stock, Triggers vs Views/SP

Hello..

I am designing a Database Application that covers Inventory System. And I am now in a dilemma of chosing which design to track Inventory stock better, in performance, reliability, and error free?

1st Design

PRODUCT TABLE
ItemID
ItemName
Price
QtyOnHand
..and other unique info of the product..

SALES TABLE
SalesID
Date
...etc...

SALESDETAIL TABLE
SalesID
ItemID
QtySold
Price

PURCHASE TABLE
PurchaseID
Date
...etc...

PURCHASEDETAIL TABLE
PurchaseID
ItemID
QtyPurchase
Price
...etc...

and similar design with SALESRETURN+DETAIL, PURCHASERETURN+DETAIL, ADJUSTMENT+DETAIL

Tracking Inventory stock is done by using (update, insert and delete) triggers in each of the DETAILS to update the QtyOnHand in the PRODUCT TABLE

2nd Design

PRODUCT TABLE
ItemID
ItemName
Price
...etc...

INVENTORY TABLE
ItemID
QtyBegin
...etc...

SALES TABLE
SalesID
Date
...etc...

SALESDETAIL TABLE
SalesID
ItemID
QtySold
Price
...etc...

and similar design with PURCHASE+DETAIL, SALESRETURN+DETAIL, PURCHASERETURN+DETAIL, ADJUSTMENT+DETAIL

The later design does not hold QtyOnHand, but only save QtyBegin instead. To get the QtyOnHand, it uses views/stored procedure with Union Query, so it looks like this:

QtyOnHand = QtyBegin + Sum(QtySold) + Sum(QtyPurchase) + Sum(QtySalesReturn) + ......

And at the end of a accounting period, the calculation of the QtyOnHand will be the QtyBegin of the next accounting period.

According to you guys, which way is better in PERFORMANCE, RELIABILITY, ERROR FREE, and why? What are the pros and cons of these two?

Thanks a lot.Hi

I would suggest to have design 2 as my option. Performance without reliability is of no use. There is no meaning in giving a wrong information to the user.

In the first design, you are storing the stock of each item whenever there is a movement of the product, either inward or outward. As per your design, let us assume, initially you are having a product, Product A, with no stock. Now you make a purchase on 01/23/2007 for quantity 50. Now the QtyOnHand will have value 50. Suppose you make a sales on 01/25/2007 for 30, as per your design you will update the QtyonHand field, which will now become 20. Now, if I need to get the stock of Product A on 01/04/2007, I cannot use the value in the field QtyonHand, which will be wrong. In this case it will be 20. But actually it must be 50. So we need to calculate the stock by adding the inwards and deducting the outwards. Also if you allow backdate billing, stock updation will become a serious issue.

In the second design, I accept that the performance will be lesser than the first one. But by careful designing that can also be solved. For eg, having a seperate table which contains a date field, Product key and QtyonHand fields. For each purchase, sales and other product movement transactions, you can update this table for each day. There can be several other methods as well. If you come across please intimate me as well.

with regards

Abdur Raoof M|||For what it's worth...
No matter which solution you choose, don't forget to leave room to account for stock transactions that are not
related to sales and receipts, such as damage or shrink.
Invariably, Beginning inventory-sales+purchases<>actual ending inventory.|||@.Abdul Raoof

I very much agree that the 2nd one is far more reliable, but I am still wondering how much more do I have to pay for the reliability? I have done the 2nd one before, and the difference to load the 'item' table without calculating qty compared to load a view that calculates the QtyOnHand with many tables related (although there are only 2 tables with more than 30000 rows) is about 1 sec.

And thanks for minding me the problem of the 1st design, never thought of that before.

@.RedNeckGeek
I think I have included Adjustment Table if that's what you mean?
Beginning inventory-sales+purchases-adjustment = actual ending inventory :)

Thank you Guys.

Anyone? Please... feel free to comment...

Monday, March 19, 2012

Invalid cursor state?

quote:

> I am trying to make design changes to a SQL table i just created and I

keep

quote:

> getting this error:
> 'Drug_Alcohol' table
> - Unable to modify table.
> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> It says in books online that this error can be caused if the sql server

runs

quote:

> out of resources while attempting to save. The database I created is new
> and the file size is still only 4megs. I tried increasing the size, but I
> still get the error.
> Does anyone know what might be happening? The only way I can make changes
> to a table now is to recreate a new table with the updated changes and
> delete the old one. I am running SQL server 2000 with service pack 3a.
>

|||The table has 5 columns:
Drug_AlcoholID int 4
DriverID int 4 Allow Nulls
PullDate smalldatetime 4
Pulltype int 4 Allow Nulls
Results char 20 Allow Nulls
I just created the table and there is no data in it.
I get the error if I try to uncheck allow nulls, change the first field to
an identity field, delete a column, or try to add a new column.
I am using Enterprise Manager so I do not see the ALTER TABLE statement.|||Has your local Enterprise Manager (assuming client tools only) been updated
to SP3? Is it even SQL Server 2000? Make sure both client and server are
the same version. Is SQL Server in the correct compatibility mode? You
might have problems changing table properties like that through a 2000 GUI
(which can issue ALTER TABLE calls under the covers) if the underlying
database is actually in 6.5 mode, for example.
Open Query Analyzer, connect to the server, and run:
EXEC sp_dbcmptlevel 'database_name'
This should be in 70 or 80, or else you won't be able to issue many commands
resembling ALTER TABLE.
What operating system are you on locally? What type of authentication are
you using (SQL or Windows)? See http://support.microsoft.com/?id=243292
Also, if you are on a Win9x platform and are using Windows authentication,
you might consider using SQL authentication instead.
Was this database created by upsizing from Access?
Might also see http://support.microsoft.com/?id=821334
Also, most of these operations can and should be handled in Query Analyzer
(ALTER TABLE, EXEC sp_rename, etc). That way you can save your scripts,
check them into source safe, but more meaningful errors when they break,
etc.
Adding the IDENTITY property to an existing column is quite a bit of work...
the database has to make a duplicate table, copy all the rows, drop the old
table, and rename the new one, and keep the table off-limits to all other
processes throughout the task. I suggest if you want IDENTITY you decide so
up front, before the table has data in it...
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"REB" <russ@.bjorgaard.com> wrote in message
news:#76622R5DHA.564@.TK2MSFTNGP10.phx.gbl...

quote:

> The table has 5 columns:
> Drug_AlcoholID int 4
> DriverID int 4 Allow Nulls
> PullDate smalldatetime 4
> Pulltype int 4 Allow Nulls
> Results char 20 Allow Nulls
> I just created the table and there is no data in it.
> I get the error if I try to uncheck allow nulls, change the first field to
> an identity field, delete a column, or try to add a new column.
> I am using Enterprise Manager so I do not see the ALTER TABLE statement.
>

|||Thanks for the response. Using Query analyzer to make the table changes
works just fine (I just had to learn the syntax). Enterprise Manager was
installed with my SQL Server 2000 Standard edition on my test server, which
is running windows server 2003. I have SP3a installed.
Is there a seperate download to update the Enterprise Manager? When I look
under help it says my version of Enterprise Manager is 8.0|||I have been getting the same problem, too. Our scenario:
Server:
Windows Server 2003
SQL 2000 SP3a
MDAC 2.8 with KB832483 hotfix installed
Client 1:
XP Pro SP1a
MDAC 2.8 with KB832483 hotfix installed
Client 2:
XP Home SP1a
MDAC 2.8 (no hotfix installed)
(Also tried Enterprise Manager from server console)
When trying to add column, delete column, or uncheck allow nulls through Ent
erprise Manager, I get the same "Invalid Cursor State" message. This happen
s when performing these operations on any table in any database on the serve
r. However, executing a sc
ript through Query Analyzer to perform these functions causes not problems.
On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any o
f these problems.
Regarding the 2003 server, I have verified the following:
Compatibility level of all databases is 80
Connecting to server using SQL or Windows Authentication makes no difference
Connecting using sa or a variety of db admin users makes no difference
No databases were upsized from Access (in fact, all DBs and objects were cre
ated within the last two months from either EM or QA)
My last successful attempt to perform the above operations was Jan 27. The
only configuation change to the server was Jan 29 to install the KB832483 ho
tfix. The next attempt to perform these operations was today and had the pr
oblems indicated above.
I also:
1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and got
error
2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and g
ot error
3) Reinstalled KB832483 hotfix on Client 1, attempted operation from Client
1 and got error
4) Reinstalled KB832483 hotfix on Server, attempted operation from Client 1
and got error
This is a development server, so I[m open to trying something radical if nee
ded. Any other suggestions?
John|||What Version of SQL Server do you have? 8.00.760(SP3)?
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:815C57B0-77A9-4102-A772-D3849A599DD0@.microsoft.com...

quote:

> I have been getting the same problem, too. Our scenario:
> Server:
> Windows Server 2003
> SQL 2000 SP3a
> MDAC 2.8 with KB832483 hotfix installed
> Client 1:
> XP Pro SP1a
> MDAC 2.8 with KB832483 hotfix installed
> Client 2:
> XP Home SP1a
> MDAC 2.8 (no hotfix installed)
> (Also tried Enterprise Manager from server console)
>
> When trying to add column, delete column, or uncheck allow nulls through

Enterprise Manager, I get the same "Invalid Cursor State" message. This
happens when performing these operations on any table in any database on the
server. However, executing a script through Query Analyzer to perform these
functions causes not problems.

quote:

> On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any

of these problems.

quote:

> Regarding the 2003 server, I have verified the following:
> Compatibility level of all databases is 80
> Connecting to server using SQL or Windows Authentication makes no

difference

quote:

> Connecting using sa or a variety of db admin users makes no difference
> No databases were upsized from Access (in fact, all DBs and objects were

created within the last two months from either EM or QA)

quote:

>
> My last successful attempt to perform the above operations was Jan 27.

The only configuation change to the server was Jan 29 to install the
KB832483 hotfix. The next attempt to perform these operations was today and
had the problems indicated above.

quote:

> I also:
> 1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and

got error

quote:

> 2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and

got error

quote:

> 3) Reinstalled KB832483 hotfix on Client 1, attempted operation from

Client 1 and got error

quote:

> 4) Reinstalled KB832483 hotfix on Server, attempted operation from Client

1 and got error

quote:

>
> This is a development server, so I[m open to trying something radical if

needed. Any other suggestions?

quote:

> John

|||What is the level of SQL Server on the clients (they should be at the same
SP level as the server)? Why have you not updated client 2 with the MDAC
hotfix?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:815C57B0-77A9-4102-A772-D3849A599DD0@.microsoft.com...

quote:

> I have been getting the same problem, too. Our scenario:
> Server:
> Windows Server 2003
> SQL 2000 SP3a
> MDAC 2.8 with KB832483 hotfix installed
> Client 1:
> XP Pro SP1a
> MDAC 2.8 with KB832483 hotfix installed
> Client 2:
> XP Home SP1a
> MDAC 2.8 (no hotfix installed)
> (Also tried Enterprise Manager from server console)
>
> When trying to add column, delete column, or uncheck allow nulls through

quote:

> On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any

of these problems.

quote:

> Regarding the 2003 server, I have verified the following:
> Compatibility level of all databases is 80
> Connecting to server using SQL or Windows Authentication makes no

difference

quote:

> Connecting using sa or a variety of db admin users makes no difference
> No databases were upsized from Access (in fact, all DBs and objects were

created within the last two months from either EM or QA)

quote:

>
> My last successful attempt to perform the above operations was Jan 27.

The only configuation change to the server was Jan 29 to install the
KB832483 hotfix. The next attempt to perform these operations was today and
had the problems indicated above.

quote:

> I also:
> 1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and

got error

quote:

> 2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and

got error

quote:

> 3) Reinstalled KB832483 hotfix on Client 1, attempted operation from

Client 1 and got error

quote:

> 4) Reinstalled KB832483 hotfix on Server, attempted operation from Client

1 and got error

quote:

>
> This is a development server, so I[m open to trying something radical if

needed. Any other suggestions?

quote:

> John

|||SP3 (8.00.859) is installed on the 2003 server, SP3 (8.00.760) on the SQL Se
rver Developer on Client 1. Both Client 1 and Client 2 have SP3a applied to
the client tools, also.
Client 2 belongs to a user who does not regularly keep up with MDAC updates;
therefore, the hotfix was not installed. I wanted to attempt the operation
s on Client 2 to help rule out wheter the hotfix may have caused the problem
on Client 1.
I forgot to mention that we also installed Reporting Services on the 2003 se
rver on the 29th. I e-mailed this question to MS and they didn't think that
installation caused this problem. I can't find a cross-reference to determ
ine how the 2003 server got
8.00.859, so I suspect this is due to installing Reporting Services. I'm do
ubting whether uninstalling Reporting Services would get that server back to
8.00.760.
Any ideas?|||>> I can't find a cross-reference to determine how the 2003 server got
8.00.859, so I suspect this is due to installing Reporting Services.
No, this has nothing to do with RS. 859 is the most recent *publicly*
available hotfix that I'm aware of. See
http://support.microsoft.com/?kbid=821334
You can trace specific version #s here:
http://www.aspfaq.com/2160
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

Invalid cursor state?

I am trying to make design changes to a SQL table i just created and I keep
getting this error:
'Drug_Alcohol' table
- Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
It says in books online that this error can be caused if the sql server runs
out of resources while attempting to save. The database I created is new
and the file size is still only 4megs. I tried increasing the size, but I
still get the error.
Does anyone know what might be happening? The only way I can make changes
to a table now is to recreate a new table with the updated changes and
delete the old one. I am running SQL server 2000 with service pack 3a.Maybe you could show the current structure of the table, sample data, and
the ALTER TABLE statement.
Or, we could guess all day...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"REB" <russ@.bjorgaard.com> wrote in message
news:#VKtrpR5DHA.504@.TK2MSFTNGP11.phx.gbl...
> I am trying to make design changes to a SQL table i just created and I
keep
> getting this error:
> 'Drug_Alcohol' table
> - Unable to modify table.
> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> It says in books online that this error can be caused if the sql server
runs
> out of resources while attempting to save. The database I created is new
> and the file size is still only 4megs. I tried increasing the size, but I
> still get the error.
> Does anyone know what might be happening? The only way I can make changes
> to a table now is to recreate a new table with the updated changes and
> delete the old one. I am running SQL server 2000 with service pack 3a.
>|||The table has 5 columns:
Drug_AlcoholID int 4
DriverID int 4 Allow Nulls
PullDate smalldatetime 4
Pulltype int 4 Allow Nulls
Results char 20 Allow Nulls
I just created the table and there is no data in it.
I get the error if I try to uncheck allow nulls, change the first field to
an identity field, delete a column, or try to add a new column.
I am using Enterprise Manager so I do not see the ALTER TABLE statement.|||Has your local Enterprise Manager (assuming client tools only) been updated
to SP3? Is it even SQL Server 2000? Make sure both client and server are
the same version. Is SQL Server in the correct compatibility mode? You
might have problems changing table properties like that through a 2000 GUI
(which can issue ALTER TABLE calls under the covers) if the underlying
database is actually in 6.5 mode, for example.
Open Query Analyzer, connect to the server, and run:
EXEC sp_dbcmptlevel 'database_name'
This should be in 70 or 80, or else you won't be able to issue many commands
resembling ALTER TABLE.
What operating system are you on locally? What type of authentication are
you using (SQL or Windows)? See http://support.microsoft.com/?id=243292
Also, if you are on a Win9x platform and are using Windows authentication,
you might consider using SQL authentication instead.
Was this database created by upsizing from Access?
Might also see http://support.microsoft.com/?id=821334
Also, most of these operations can and should be handled in Query Analyzer
(ALTER TABLE, EXEC sp_rename, etc). That way you can save your scripts,
check them into source safe, but more meaningful errors when they break,
etc.
Adding the IDENTITY property to an existing column is quite a bit of work...
the database has to make a duplicate table, copy all the rows, drop the old
table, and rename the new one, and keep the table off-limits to all other
processes throughout the task. I suggest if you want IDENTITY you decide so
up front, before the table has data in it...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"REB" <russ@.bjorgaard.com> wrote in message
news:#76622R5DHA.564@.TK2MSFTNGP10.phx.gbl...
> The table has 5 columns:
> Drug_AlcoholID int 4
> DriverID int 4 Allow Nulls
> PullDate smalldatetime 4
> Pulltype int 4 Allow Nulls
> Results char 20 Allow Nulls
> I just created the table and there is no data in it.
> I get the error if I try to uncheck allow nulls, change the first field to
> an identity field, delete a column, or try to add a new column.
> I am using Enterprise Manager so I do not see the ALTER TABLE statement.
>|||Thanks for the response. Using Query analyzer to make the table changes
works just fine (I just had to learn the syntax). Enterprise Manager was
installed with my SQL Server 2000 Standard edition on my test server, which
is running windows server 2003. I have SP3a installed.
Is there a seperate download to update the Enterprise Manager? When I look
under help it says my version of Enterprise Manager is 8.0|||I have been getting the same problem, too. Our scenario
Server
Windows Server 200
SQL 2000 SP3
MDAC 2.8 with KB832483 hotfix installe
Client 1
XP Pro SP1
MDAC 2.8 with KB832483 hotfix installe
Client 2
XP Home SP1
MDAC 2.8 (no hotfix installed
(Also tried Enterprise Manager from server console
When trying to add column, delete column, or uncheck allow nulls through Enterprise Manager, I get the same "Invalid Cursor State" message. This happens when performing these operations on any table in any database on the server. However, executing a script through Query Analyzer to perform these functions causes not problems
On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any of these problems
Regarding the 2003 server, I have verified the following
Compatibility level of all databases is 8
Connecting to server using SQL or Windows Authentication makes no differenc
Connecting using sa or a variety of db admin users makes no differenc
No databases were upsized from Access (in fact, all DBs and objects were created within the last two months from either EM or QA
My last successful attempt to perform the above operations was Jan 27. The only configuation change to the server was Jan 29 to install the KB832483 hotfix. The next attempt to perform these operations was today and had the problems indicated above
I also
1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and got erro
2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and got erro
3) Reinstalled KB832483 hotfix on Client 1, attempted operation from Client 1 and got erro
4) Reinstalled KB832483 hotfix on Server, attempted operation from Client 1 and got erro
This is a development server, so I[m open to trying something radical if needed. Any other suggestions
John|||What Version of SQL Server do you have? 8.00.760(SP3)?
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:815C57B0-77A9-4102-A772-D3849A599DD0@.microsoft.com...
> I have been getting the same problem, too. Our scenario:
> Server:
> Windows Server 2003
> SQL 2000 SP3a
> MDAC 2.8 with KB832483 hotfix installed
> Client 1:
> XP Pro SP1a
> MDAC 2.8 with KB832483 hotfix installed
> Client 2:
> XP Home SP1a
> MDAC 2.8 (no hotfix installed)
> (Also tried Enterprise Manager from server console)
>
> When trying to add column, delete column, or uncheck allow nulls through
Enterprise Manager, I get the same "Invalid Cursor State" message. This
happens when performing these operations on any table in any database on the
server. However, executing a script through Query Analyzer to perform these
functions causes not problems.
> On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any
of these problems.
> Regarding the 2003 server, I have verified the following:
> Compatibility level of all databases is 80
> Connecting to server using SQL or Windows Authentication makes no
difference
> Connecting using sa or a variety of db admin users makes no difference
> No databases were upsized from Access (in fact, all DBs and objects were
created within the last two months from either EM or QA)
>
> My last successful attempt to perform the above operations was Jan 27.
The only configuation change to the server was Jan 29 to install the
KB832483 hotfix. The next attempt to perform these operations was today and
had the problems indicated above.
> I also:
> 1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and
got error
> 2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and
got error
> 3) Reinstalled KB832483 hotfix on Client 1, attempted operation from
Client 1 and got error
> 4) Reinstalled KB832483 hotfix on Server, attempted operation from Client
1 and got error
>
> This is a development server, so I[m open to trying something radical if
needed. Any other suggestions?
> John|||What is the level of SQL Server on the clients (they should be at the same
SP level as the server)? Why have you not updated client 2 with the MDAC
hotfix?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:815C57B0-77A9-4102-A772-D3849A599DD0@.microsoft.com...
> I have been getting the same problem, too. Our scenario:
> Server:
> Windows Server 2003
> SQL 2000 SP3a
> MDAC 2.8 with KB832483 hotfix installed
> Client 1:
> XP Pro SP1a
> MDAC 2.8 with KB832483 hotfix installed
> Client 2:
> XP Home SP1a
> MDAC 2.8 (no hotfix installed)
> (Also tried Enterprise Manager from server console)
>
> When trying to add column, delete column, or uncheck allow nulls through
Enterprise Manager, I get the same "Invalid Cursor State" message. This
happens when performing these operations on any table in any database on the
server. However, executing a script through Query Analyzer to perform these
functions causes not problems.
> On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any
of these problems.
> Regarding the 2003 server, I have verified the following:
> Compatibility level of all databases is 80
> Connecting to server using SQL or Windows Authentication makes no
difference
> Connecting using sa or a variety of db admin users makes no difference
> No databases were upsized from Access (in fact, all DBs and objects were
created within the last two months from either EM or QA)
>
> My last successful attempt to perform the above operations was Jan 27.
The only configuation change to the server was Jan 29 to install the
KB832483 hotfix. The next attempt to perform these operations was today and
had the problems indicated above.
> I also:
> 1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and
got error
> 2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and
got error
> 3) Reinstalled KB832483 hotfix on Client 1, attempted operation from
Client 1 and got error
> 4) Reinstalled KB832483 hotfix on Server, attempted operation from Client
1 and got error
>
> This is a development server, so I[m open to trying something radical if
needed. Any other suggestions?
> John|||SP3 (8.00.859) is installed on the 2003 server, SP3 (8.00.760) on the SQL Server Developer on Client 1. Both Client 1 and Client 2 have SP3a applied to the client tools, also
Client 2 belongs to a user who does not regularly keep up with MDAC updates; therefore, the hotfix was not installed. I wanted to attempt the operations on Client 2 to help rule out wheter the hotfix may have caused the problem on Client 1
I forgot to mention that we also installed Reporting Services on the 2003 server on the 29th. I e-mailed this question to MS and they didn't think that installation caused this problem. I can't find a cross-reference to determine how the 2003 server got 8.00.859, so I suspect this is due to installing Reporting Services. I'm doubting whether uninstalling Reporting Services would get that server back to 8.00.760
Any ideas?|||>> I can't find a cross-reference to determine how the 2003 server got
8.00.859, so I suspect this is due to installing Reporting Services.
No, this has nothing to do with RS. 859 is the most recent *publicly*
available hotfix that I'm aware of. See
http://support.microsoft.com/?kbid=821334
You can trace specific version #s here:
http://www.aspfaq.com/2160
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Thanks for the info. I'll bookmark that page at aspfaq.com for future reference
Any other suggestions on the source of the "invalid cursor state" error?|||No, my post earlier summarized all of the reasons I'm aware of.
How about, instead of using Enterprise Manager to make DDL changes, you use
Query Analyzer?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:78B9B85C-061F-40C4-96D1-77BCEB249BC0@.microsoft.com...
> Thanks for the info. I'll bookmark that page at aspfaq.com for future
reference.
> Any other suggestions on the source of the "invalid cursor state" error?|||To me, Query Analyzer is an acceptable alternative. The use of this server will involve some users who need to learn the fundamentals of SQL Server. While doing DDL changes in Query Analyzer is no problem for me, the EM GUI sure would make their learning easier
I think we'll end up creating a support incident for this. Any other resources you would suggest I try before taking the plunge? I spent quite a while researching this on the Web myself and this newsgroup was the only place I found any help
Aaron, thanks again for all your assistance!|||I spoke with MS support over the last couple of days. They gave me instructions on how to get hotfix 876. It is not available for public release yet, so you'll need to call them and ask for a "grace incident" so they don't charge you for the support
Anyway, they'll send a link and a password to get your own copy of the fix
I installed the hotfix and it cleared up all the problems that I reported
Good luck!|||Thanks JSD, made a note in http://www.aspfaq.com/2515
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:72E54CEF-E2F2-40F5-9D96-72BF84A04191@.microsoft.com...
> I spoke with MS support over the last couple of days. They gave me
instructions on how to get hotfix 876. It is not available for public
release yet, so you'll need to call them and ask for a "grace incident" so
they don't charge you for the support.
> Anyway, they'll send a link and a password to get your own copy of the
fix.
> I installed the hotfix and it cleared up all the problems that I reported.
> Good luck!|||I am experiencing the same behavior. Any idea when a hotfix will be
available for this issue? If not, can someone please point me toward the
telephone number I need to use for free information on where to get the
hotfix? It is really aggrevating not being able to modify any tables ...
Thank you,
Michael Carr
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:OG4cuVp7DHA.2168@.TK2MSFTNGP12.phx.gbl...
> Thanks JSD, made a note in http://www.aspfaq.com/2515|||You can ask for fix 878.
http://support.microsoft.com/?kbid=831950
http://support.microsoft.com/?scid=fh;en-us;Prodoffer41a
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Michael Carr" <mcarr@.umich.edu> wrote in message
news:OtHSTcC$DHA.392@.TK2MSFTNGP12.phx.gbl...
> I am experiencing the same behavior. Any idea when a hotfix will be
> available for this issue? If not, can someone please point me toward the
> telephone number I need to use for free information on where to get the
> hotfix? It is really aggrevating not being able to modify any tables ...
> Thank you,
> Michael Carr
> "Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
> news:OG4cuVp7DHA.2168@.TK2MSFTNGP12.phx.gbl...
> > Thanks JSD, made a note in http://www.aspfaq.com/2515
>|||Hey thanks, that fixed it right up!
Michael Carr
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:#8zODhH$DHA.2592@.TK2MSFTNGP10.phx.gbl...
> You can ask for fix 878.
> http://support.microsoft.com/?kbid=831950
> http://support.microsoft.com/?scid=fh;en-us;Prodoffer41a

Wednesday, March 7, 2012

Introducing The Poorly Designed Management Studio

Since Microsoft has remove the ability for developers to design in
Access through ADPs in SQLS2005, I am going to begin my own discussion
on why the Management Studio is poorly designed for developers. If I
am in error on any of these points, please let me know because it could
greatly improve my shop's productivity.
#1. Let's look a the screen when creating a new table. Now I know
very few screens that are longer than they are wide. As a matter of
fact, I believe the industry is trending toward wide screens. When you
create a new table in Management Studio there are three columns,
"Column Name", "Data Type", and "Allow Nulls." Hmm, OK, three columns.
Let's look at all the wasted space on the screen to the right of the
three columns. Unless you are creating very very very very long column
names, this would be an ideal place to the "Column Properties." But
instead, it's stuck at the bottom, in a very small vertical scroll box
with huge column widths. Nice.
Many more to come...> #1. Let's look a the screen when creating a new table. Now I know
> very few screens that are longer than they are wide. As a matter of
> fact, I believe the industry is trending toward wide screens. When
> you
Real developers know the create table syntax and don't need A GUI. :)
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||Just reset your video display to 640x480 and you will see that the dialog
fills the screen quite nicely. :-P
"The Cornjerker" <addoty@.gmail.com> wrote in message
news:1142956268.004514.272830@.i39g2000cwa.googlegroups.com...
> Since Microsoft has remove the ability for developers to design in
> Access through ADPs in SQLS2005, I am going to begin my own discussion
> on why the Management Studio is poorly designed for developers. If I
> am in error on any of these points, please let me know because it could
> greatly improve my shop's productivity.
> #1. Let's look a the screen when creating a new table. Now I know
> very few screens that are longer than they are wide. As a matter of
> fact, I believe the industry is trending toward wide screens. When you
> create a new table in Management Studio there are three columns,
> "Column Name", "Data Type", and "Allow Nulls." Hmm, OK, three columns.
> Let's look at all the wasted space on the screen to the right of the
> three columns. Unless you are creating very very very very long column
> names, this would be an ideal place to the "Column Properties." But
> instead, it's stuck at the bottom, in a very small vertical scroll box
> with huge column widths. Nice.
> Many more to come...
>|||#2. Why do all 4 panes default to visible when I create a new view?
Why when I hide the results pane (because I don't need it until I
execute the view) and when I hide the SQL pane (because I'm not a "real
developer") do they re-appear the next time I create a new view? Is
there a setting I'm missing?|||#3. When designing a query and I type in "CASE WHEN fund = '0001' THEN
revenue_jan ELSE 0 END" as a column name I cannot select "Sum" from the
"Group By" drop-down list? I know it works because when I type it in
the SQL pane (like a "real developer") it works and shows up correctly
after I save the view.|||#4. Why can't I export a view or table to Excel?|||Yep, the query window is wide enough. :)
And clicking up a disaster is pretty much out of the question.
ML
http://milambda.blogspot.com/|||Real developers should be submitting schema change requests to the real
DBA(s) -- who also don't need a GUI. :-)

> Real developers know the create table syntax and don't need A GUI. :)|||If you are simply looking to grab the contents of a particular table:
select * from sometable
in the results pane, click the upper left shaded block (this will highlight
the entire result. ctrl+c
open a new xls and select a single cell on the sheet.
ctrl+v
even brings over the column headers (which I don't remember if it did in the
old QA or not).
HTH
--Tony
"The Cornjerker" wrote:

> #4. Why can't I export a view or table to Excel?
>|||I don't think that there is a persisted preference for these. I don't reall
y
use this feature, but after poking around with it a bit, having all the pane
s
there seemed kind of useful given the task at hand. I could also see how
being able to switch this to a tabbed configuration like you can with the
standard query windows might be preferrable.
--Tony
"The Cornjerker" wrote:

> #2. Why do all 4 panes default to visible when I create a new view?
> Why when I hide the results pane (because I don't need it until I
> execute the view) and when I hide the SQL pane (because I'm not a "real
> developer") do they re-appear the next time I create a new view? Is
> there a setting I'm missing?
>

Friday, March 30, 2012

Invisible controls durig runtime

Wednesday, March 28, 2012

Inventory Stock, Triggers vs Views/SP

Monday, March 19, 2012

Invalid cursor state?

Invalid cursor state?

Wednesday, March 7, 2012

Introducing The Poorly Designed Management Studio

Internet integration

Blog Archive

About Me