Showing posts with label sp1. Show all posts
Showing posts with label sp1. Show all posts

Monday, March 26, 2012

PP: New Features in SQL 2005

Hi Folks
Now that we have SQL 2005 SP1 released, does anybody here know where
can we get information on what is coming in SP2? In this discussion
group, I remember somebody mentioning about "Generating Individual SQL
File for each DB Object from Management Studio", as a feature planned
for SP2, like-wise what other features are planned.
Any idea?
This is just out of curiosity:)
Thanks
PPHi
This is documented at
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124561
Although it is mentioned as being in SP2, at this point in time I doubt if
anyone would give you a finalized list of it's content!
John
"prabhupr@.hotmail.com" wrote:
> Hi Folks
> Now that we have SQL 2005 SP1 released, does anybody here know where
> can we get information on what is coming in SP2? In this discussion
> group, I remember somebody mentioning about "Generating Individual SQL
> File for each DB Object from Management Studio", as a feature planned
> for SP2, like-wise what other features are planned.
> Any idea?
> This is just out of curiosity:)
> Thanks
> PP
>

PP: New Features in SQL 2005

Hi Folks
Now that we have SQL 2005 SP1 released, does anybody here know where
can we get information on what is coming in SP2? In this discussion
group, I remember somebody mentioning about "Generating Individual SQL
File for each DB Object from Management Studio", as a feature planned
for SP2, like-wise what other features are planned.
Any idea?
This is just out of curiosity
Thanks
PPHi
This is documented at
https://connect.microsoft.com/SQLSe...=1245
61
Although it is mentioned as being in SP2, at this point in time I doubt if
anyone would give you a finalized list of it's content!
John
"prabhupr@.hotmail.com" wrote:

> Hi Folks
> Now that we have SQL 2005 SP1 released, does anybody here know where
> can we get information on what is coming in SP2? In this discussion
> group, I remember somebody mentioning about "Generating Individual SQL
> File for each DB Object from Management Studio", as a feature planned
> for SP2, like-wise what other features are planned.
> Any idea?
> This is just out of curiosity
> Thanks
> PP
>

Tuesday, March 20, 2012

Post SP1 troubles

Access 2003 + Sp1 + adp + ADO 2.8 + SQL Server 2000.
A perfectly working form with subform from two inner joined tables now is
giving me annoying messages when inserting records in the master table.
"Cannot insert a non-null value into a timestamp column. Use INSERT with a
column list or with a default of NULL for the timestamp column."
There's nothing done programmatically, all data bound to form's controls
(obvoiusly not the timestamp field).
Help!
I would use Profiler to determine the exact SQL being passed to the server.
The message is probably correct and the app is probably trying to do what
the message says it is preventing.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Atlas" <atlaspeak@.my-deja.com> wrote in message
news:10guprqnccn2g2b@.news.supernews.com...
> Access 2003 + Sp1 + adp + ADO 2.8 + SQL Server 2000.
> A perfectly working form with subform from two inner joined tables now is
> giving me annoying messages when inserting records in the master table.
> "Cannot insert a non-null value into a timestamp column. Use INSERT with a
> column list or with a default of NULL for the timestamp column."
> There's nothing done programmatically, all data bound to form's controls
> (obvoiusly not the timestamp field).
> Help!
>

Post SP1 troubles

Access 2003 + Sp1 + adp + ADO 2.8 + SQL Server 2000.
A perfectly working form with subform from two inner joined tables now is
giving me annoying messages when inserting records in the master table.
"Cannot insert a non-null value into a timestamp column. Use INSERT with a
column list or with a default of NULL for the timestamp column."
There's nothing done programmatically, all data bound to form's controls
(obvoiusly not the timestamp field).
Help!I would use Profiler to determine the exact SQL being passed to the server.
The message is probably correct and the app is probably trying to do what
the message says it is preventing.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Atlas" <atlaspeak@.my-deja.com> wrote in message
news:10guprqnccn2g2b@.news.supernews.com...
> Access 2003 + Sp1 + adp + ADO 2.8 + SQL Server 2000.
> A perfectly working form with subform from two inner joined tables now is
> giving me annoying messages when inserting records in the master table.
> "Cannot insert a non-null value into a timestamp column. Use INSERT with a
> column list or with a default of NULL for the timestamp column."
> There's nothing done programmatically, all data bound to form's controls
> (obvoiusly not the timestamp field).
> Help!
>

Post SP1 troubles

Access 2003 + Sp1 + adp + ADO 2.8 + SQL Server 2000.
A perfectly working form with subform from two inner joined tables now is
giving me annoying messages when inserting records in the master table.
"Cannot insert a non-null value into a timestamp column. Use INSERT with a
column list or with a default of NULL for the timestamp column."
There's nothing done programmatically, all data bound to form's controls
(obvoiusly not the timestamp field).
Help!I would use Profiler to determine the exact SQL being passed to the server.
The message is probably correct and the app is probably trying to do what
the message says it is preventing.
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Atlas" <atlaspeak@.my-deja.com> wrote in message
news:10guprqnccn2g2b@.news.supernews.com...
> Access 2003 + Sp1 + adp + ADO 2.8 + SQL Server 2000.
> A perfectly working form with subform from two inner joined tables now is
> giving me annoying messages when inserting records in the master table.
> "Cannot insert a non-null value into a timestamp column. Use INSERT with a
> column list or with a default of NULL for the timestamp column."
> There's nothing done programmatically, all data bound to form's controls
> (obvoiusly not the timestamp field).
> Help!
>

post SP1 hotfix

Just curious, I'm reading about the SQL Server 2005 post SP1 hotfix and it looks like you need to install the packages in order:

SQL Server

Analysis Services

Integration Services

Notification Services

Reporting Services

Tools

My desktop is configured as an Analysis Services and Integration Services instance, but without the SQL Server proper components installed. What should my install order be? Does important note 3 about SMO and SQL-DMO still apply?

Thanks,

Keehan

What document do you refer to?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Sorry 'bout that:

http://support.microsoft.com/kb/918222

Cheers,

Keehan

|||

If you didnt install SQL Server relational engine, you should be fine with installing hotfix packges for installed components only.

Looks SQL-DMO issue only applies if you have SQL Server relational engine installed.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.