Showing posts with label save. Show all posts
Showing posts with label save. Show all posts

Monday, March 19, 2012

Can't save view - linked server

Our customer has an external SQL server on which they want to make a
lookup into a table/view.
I have setup a Linked server and retrieve data from the linked server.
Example:
EXEC sp_addlinkedserver
@.server = 'NPRSQL',
@.srvproduct = 'SQLServer OLEDB Provider',
@.provider = 'SQLOLEDB',
@.datasrc = 'SQL01'
Go
SELECT *
FROM NPRSQL.DTS.dbo.ItemView
However I can "create" the view, get the data, but when I try to save
the view I get the following error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
operation could
not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a
distributed transaction.[Microsoft][ODBC SQL Server Driver][SQL
Server]
[OLE/DB
provider returned message: New transaction cannot enlist in the
specified transaction
coordinator.]
How can it be that I can get the data but not save the view?
I have tried to make a similarly scenario on the Northwind database,
create a view on the linked server and the "call" this view via a view
on my local server with the same result.
/refdkHi
see this link
http://support.microsoft.com/kb/839279
try this first and let us know
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1181027684.578393.61140@.o5g2000hsb.googlegroups.com...
> Our customer has an external SQL server on which they want to make a
> lookup into a table/view.
> I have setup a Linked server and retrieve data from the linked server.
> Example:
> EXEC sp_addlinkedserver
> @.server = 'NPRSQL',
> @.srvproduct = 'SQLServer OLEDB Provider',
> @.provider = 'SQLOLEDB',
> @.datasrc = 'SQL01'
> Go
> SELECT *
> FROM NPRSQL.DTS.dbo.ItemView
> However I can "create" the view, get the data, but when I try to save
> the view I get the following error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
> operation could
> not be performed because the OLE DB provider 'SQLOLEDB' was unable to
> begin a
> distributed transaction.[Microsoft][ODBC SQL Server Driver][SQ
L
> Server]
> [OLE/DB
> provider returned message: New transaction cannot enlist in the
> specified transaction
> coordinator.]
> How can it be that I can get the data but not save the view?
> I have tried to make a similarly scenario on the Northwind database,
> create a view on the linked server and the "call" this view via a view
> on my local server with the same result.
>
> /refdk
>|||I had already done most of the stuff in the kb-issue. However, I have
now completed every step but the error persists.
/refdk|||Hi
Can you post the view statement
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1181109437.668792.166410@.q75g2000hsh.googlegroups.com...
>I had already done most of the stuff in the kb-issue. However, I have
> now completed every step but the error persists.
> /refdk
>|||SELECT dbo.Hornsh=F8j$Item.No_ AS [No], dbo.Hornsh=F8j
$Item.Description, dbo.Hornsh=F8j$Item.[Unit Price], SUM(dbo.[Hornsh
=F8j
$Item Ledger Entry].Quantity)
AS Quantity
FROM dbo.Hornsh=F8j$Item INNER JOIN
dbo.[Hornsh=F8j$Item Ledger Entry] ON dbo.Hornsh=F8j
$Item.No_ =3D dbo.[Hornsh=F8j$Item Ledger Entry].[Item No_]
GROUP BY dbo.Hornsh=F8j$Item.No_, dbo.Hornsh=F8j$Item.Description,
dbo.Hornsh=F8j$Item.[Unit Price]|||> How can it be that I can get the data but not save the view?
Are you trying to create the view inside of a transaction? Why is it going
through ODBC/OLEDB? Shouldn't you be creating the view in a query window
connected to that server, instead of trying to create the view through your
app via the linked server? (Well, that's how I would do it, anyway.)

Can't save view - linked server

Our customer has an external SQL server on which they want to make a
lookup into a table/view.
I have setup a Linked server and retrieve data from the linked server.
Example:
EXEC sp_addlinkedserver
@.server = 'NPRSQL',
@.srvproduct = 'SQLServer OLEDB Provider',
@.provider = 'SQLOLEDB',
@.datasrc = 'SQL01'
Go
SELECT *
FROM NPRSQL.DTS.dbo.ItemView
However I can "create" the view, get the data, but when I try to save
the view I get the following error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
operation could
not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a
distributed transaction.[Microsoft][ODBC SQL Server Driver][SQL
Server]
[OLE/DB
provider returned message: New transaction cannot enlist in the
specified transaction
coordinator.]
How can it be that I can get the data but not save the view?
I have tried to make a similarly scenario on the Northwind database,
create a view on the linked server and the "call" this view via a view
on my local server with the same result.
/refdkHi
see this link
http://support.microsoft.com/kb/839279
try this first and let us know
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1181027684.578393.61140@.o5g2000hsb.googlegroups.com...
> Our customer has an external SQL server on which they want to make a
> lookup into a table/view.
> I have setup a Linked server and retrieve data from the linked server.
> Example:
> EXEC sp_addlinkedserver
> @.server = 'NPRSQL',
> @.srvproduct = 'SQLServer OLEDB Provider',
> @.provider = 'SQLOLEDB',
> @.datasrc = 'SQL01'
> Go
> SELECT *
> FROM NPRSQL.DTS.dbo.ItemView
> However I can "create" the view, get the data, but when I try to save
> the view I get the following error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
> operation could
> not be performed because the OLE DB provider 'SQLOLEDB' was unable to
> begin a
> distributed transaction.[Microsoft][ODBC SQL Server Driver][SQL
> Server]
> [OLE/DB
> provider returned message: New transaction cannot enlist in the
> specified transaction
> coordinator.]
> How can it be that I can get the data but not save the view?
> I have tried to make a similarly scenario on the Northwind database,
> create a view on the linked server and the "call" this view via a view
> on my local server with the same result.
>
> /refdk
>|||I had already done most of the stuff in the kb-issue. However, I have
now completed every step but the error persists.
/refdk|||Hi
Can you post the view statement
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1181109437.668792.166410@.q75g2000hsh.googlegroups.com...
>I had already done most of the stuff in the kb-issue. However, I have
> now completed every step but the error persists.
> /refdk
>|||SELECT dbo.Hornsh=F8j$Item.No_ AS [No], dbo.Hornsh=F8j
$Item.Description, dbo.Hornsh=F8j$Item.[Unit Price], SUM(dbo.[Hornsh=F8j
$Item Ledger Entry].Quantity)
AS Quantity
FROM dbo.Hornsh=F8j$Item INNER JOIN
dbo.[Hornsh=F8j$Item Ledger Entry] ON dbo.Hornsh=F8j
$Item.No_ =3D dbo.[Hornsh=F8j$Item Ledger Entry].[Item No_]
GROUP BY dbo.Hornsh=F8j$Item.No_, dbo.Hornsh=F8j$Item.Description,
dbo.Hornsh=F8j$Item.[Unit Price]|||> How can it be that I can get the data but not save the view?
Are you trying to create the view inside of a transaction? Why is it going
through ODBC/OLEDB? Shouldn't you be creating the view in a query window
connected to that server, instead of trying to create the view through your
app via the linked server? (Well, that's how I would do it, anyway.)

Can't save view - linked server

Our customer has an external SQL server on which they want to make a
lookup into a table/view.
I have setup a Linked server and retrieve data from the linked server.
Example:
EXEC sp_addlinkedserver
@.server = 'NPRSQL',
@.srvproduct = 'SQLServer OLEDB Provider',
@.provider = 'SQLOLEDB',
@.datasrc = 'SQL01'
Go
SELECT *
FROM NPRSQL.DTS.dbo.ItemView
However I can "create" the view, get the data, but when I try to save
the view I get the following error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
operation could
not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a
distributed transaction.[Microsoft][ODBC SQL Server Driver][SQL
Server]
[OLE/DB
provider returned message: New transaction cannot enlist in the
specified transaction
coordinator.]
How can it be that I can get the data but not save the view?
I have tried to make a similarly scenario on the Northwind database,
create a view on the linked server and the "call" this view via a view
on my local server with the same result.
/refdk
I had already done most of the stuff in the kb-issue. However, I have
now completed every step but the error persists.
/refdk
|||SELECT dbo.Hornshj$Item.No_ AS [No], dbo.Hornshj
$Item.Description, dbo.Hornshj$Item.[Unit Price], SUM(dbo.[Hornshj
$Item Ledger Entry].Quantity)
AS Quantity
FROM dbo.Hornshj$Item INNER JOIN
dbo.[Hornshj$Item Ledger Entry] ON dbo.Hornshj
$Item.No_ = dbo.[Hornshj$Item Ledger Entry].[Item No_]
GROUP BY dbo.Hornshj$Item.No_, dbo.Hornshj$Item.Description,
dbo.Hornshj$Item.[Unit Price]
|||> How can it be that I can get the data but not save the view?
Are you trying to create the view inside of a transaction? Why is it going
through ODBC/OLEDB? Shouldn't you be creating the view in a query window
connected to that server, instead of trying to create the view through your
app via the linked server? (Well, that's how I would do it, anyway.)

Can't save Server names in "Object Explorer"

In Management Studio, under Registered Servers, I double-click a server name (could be sql 2000 or sql 2005 server) and it apperars in "Object Explorer" where I can work with it. I click the "Save All" button in Management Studio, exit Studio, and re-start Studio. When I do, I find that all the servers I placed under "Object Explorer" are now missing and I need to go through the "double-click the registered server" ritual again. And again, and again.

What am I doing wrong here? Why don't the servers "stick" in Object Explorer?

TIA

barkingdog

P.S. I have Sql 2005 SP1 installed on my box.

When the server is listed under Object Explorer you've got an active connection to that server. You probably don't want to open active connections to each of your servers every time you run Management Studio.

If you don't already have the window open, go to the View menu and open up the Registered Servers window. I keep that one open, and double-click a server in that window when I need to connect to perform some maintenance on the server. It pops right up in the Object Explorer window and I'm ready to work.

|||>>>

When the server is listed under Object Explorer you've got an active connection to that server.

Thanks for the reply. It makes sense but I sure didn't think of it myself.

Three barks and a tail wave

Barkingdog

Can't Save Report Parameters

I have looked at the SOAP method of integration as well as the URL method,
and it is just not possible to save report parameters as selected by the
user! The only way you can save them is if you re-invent your own parameter
inputs! And keep in mind that a complete integration solution should be able
to accept any possible combination of report parameters!
I think this is another oversight in the design of this product from
microsoft. They have specially designed ways to cache report data, saving
history, etc... But what about the more common case of wanting fresh data
for the same parameters? I am amazed that they did not think of this...
Is there anything like this in the works for version 2... Yes?
Please tell me yes :-]
MalikLet me also clarify that the difficulty here is getting the parameter input
from the user.
If I already know what parameters I want to run the report for, there is no
problem.
The problem is, the user can change them and then re-run the report, and I
have no idea
what parameters are currently in the report being displayed!
Malik
"Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
news:uL2wf3OiEHA.536@.TK2MSFTNGP11.phx.gbl...
> I have looked at the SOAP method of integration as well as the URL method,
> and it is just not possible to save report parameters as selected by the
> user! The only way you can save them is if you re-invent your own
parameter
> inputs! And keep in mind that a complete integration solution should be
able
> to accept any possible combination of report parameters!
> I think this is another oversight in the design of this product from
> microsoft. They have specially designed ways to cache report data, saving
> history, etc... But what about the more common case of wanting fresh data
> for the same parameters? I am amazed that they did not think of this...
> Is there anything like this in the works for version 2... Yes?
> Please tell me yes :-]
> Malik
>
>|||Donovan,
Thanks very much for your report. This is exactly the kind of solution I
need, although there are still a few problems.
I thought of doing it this way, but I am trying to fully integrate SQL RS
with our Web Application. I don't want to have to explain to our customers
that in order to design reports for use with our application you have to
always have those extra data sources present along with code to retrieve the
parameters. This puts the onus on the report developer to be a coder rather
than me taking care of the whole solution myself.
I suppose I could come up with some kind of template report that our
customers can start with, and that would make this a workable solution for
us. I am going over your report in more detail to see what I can learn from
it.
Your help has been quite valuable for my project, and I really appreciate
you sending the report!
Thank you very much indeed,
Malik
"Donovan R. Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
news:u8UcIjjiEHA.348@.tk2msftngp13.phx.gbl...
> Take a look at the attached report for help. It goes against the pubs
sample database and requires
> a SQL script to be run on the db prior to use.
> --
> Thanks.
> Donovan R. Smith
> Software Test Lead
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> news:ekCjdEPiEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > Let me also clarify that the difficulty here is getting the parameter
input
> > from the user.
> >
> > If I already know what parameters I want to run the report for, there is
no
> > problem.
> >
> > The problem is, the user can change them and then re-run the report, and
I
> > have no idea
> > what parameters are currently in the report being displayed!
> >
> > Malik
> >
> > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > news:uL2wf3OiEHA.536@.TK2MSFTNGP11.phx.gbl...
> > > I have looked at the SOAP method of integration as well as the URL
method,
> > > and it is just not possible to save report parameters as selected by
the
> > > user! The only way you can save them is if you re-invent your own
> > parameter
> > > inputs! And keep in mind that a complete integration solution should
be
> > able
> > > to accept any possible combination of report parameters!
> > >
> > > I think this is another oversight in the design of this product from
> > > microsoft. They have specially designed ways to cache report data,
saving
> > > history, etc... But what about the more common case of wanting fresh
data
> > > for the same parameters? I am amazed that they did not think of
this...
> > >
> > > Is there anything like this in the works for version 2... Yes?
> > >
> > > Please tell me yes :-]
> > >
> > > Malik
> > >
> > >
> > >
> >
> >
>
>|||If the web application provided it's own parameter prompting area and passed along that data to our
Report Viewer then you could build this logic into your web application instead of relying on RS to
do it.
--
Thanks.
Donovan R. Smith
Software Test Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
"Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
news:OBI3I2piEHA.3320@.TK2MSFTNGP11.phx.gbl...
> Donovan,
> Thanks very much for your report. This is exactly the kind of solution I
> need, although there are still a few problems.
> I thought of doing it this way, but I am trying to fully integrate SQL RS
> with our Web Application. I don't want to have to explain to our customers
> that in order to design reports for use with our application you have to
> always have those extra data sources present along with code to retrieve the
> parameters. This puts the onus on the report developer to be a coder rather
> than me taking care of the whole solution myself.
> I suppose I could come up with some kind of template report that our
> customers can start with, and that would make this a workable solution for
> us. I am going over your report in more detail to see what I can learn from
> it.
> Your help has been quite valuable for my project, and I really appreciate
> you sending the report!
> Thank you very much indeed,
> Malik
> "Donovan R. Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
> news:u8UcIjjiEHA.348@.tk2msftngp13.phx.gbl...
> > Take a look at the attached report for help. It goes against the pubs
> sample database and requires
> > a SQL script to be run on the db prior to use.
> >
> > --
> > Thanks.
> >
> > Donovan R. Smith
> > Software Test Lead
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > news:ekCjdEPiEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > > Let me also clarify that the difficulty here is getting the parameter
> input
> > > from the user.
> > >
> > > If I already know what parameters I want to run the report for, there is
> no
> > > problem.
> > >
> > > The problem is, the user can change them and then re-run the report, and
> I
> > > have no idea
> > > what parameters are currently in the report being displayed!
> > >
> > > Malik
> > >
> > > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > > news:uL2wf3OiEHA.536@.TK2MSFTNGP11.phx.gbl...
> > > > I have looked at the SOAP method of integration as well as the URL
> method,
> > > > and it is just not possible to save report parameters as selected by
> the
> > > > user! The only way you can save them is if you re-invent your own
> > > parameter
> > > > inputs! And keep in mind that a complete integration solution should
> be
> > > able
> > > > to accept any possible combination of report parameters!
> > > >
> > > > I think this is another oversight in the design of this product from
> > > > microsoft. They have specially designed ways to cache report data,
> saving
> > > > history, etc... But what about the more common case of wanting fresh
> data
> > > > for the same parameters? I am amazed that they did not think of
> this...
> > > >
> > > > Is there anything like this in the works for version 2... Yes?
> > > >
> > > > Please tell me yes :-]
> > > >
> > > > Malik
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
>|||Yes, I could write my own code to take care of parameter input, which would
have to do the following:
- prompt for any combination of parameters
- include default values and available values, with queried available
values in a drop-down list
- validate all parameter data types entered, null and blank values
- correctly take hidden parameters from the URL when they are passed
This would have to be robust enough for any report that my customers can
design to work with my web app.
I don't want to be lazy, but since RS already does all of this, I don't want
to re-invent the wheel.
I think it would be much easier for someone who already knows what
parameters are in the reports. In my scenario, our customers will expect to
just open a SQL RS report from our web app. They may design their own, or
get reports from elsewhere. It is a full integration.
I am still very much in design mode (although I should have finished long
ago :-) so I am quite open to suggestions.
Thanks again for your help.
Malik
"Donovan R. Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
news:eCLqPftiEHA.3896@.TK2MSFTNGP15.phx.gbl...
> If the web application provided it's own parameter prompting area and
passed along that data to our
> Report Viewer then you could build this logic into your web application
instead of relying on RS to
> do it.
> --
> Thanks.
> Donovan R. Smith
> Software Test Lead
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> news:OBI3I2piEHA.3320@.TK2MSFTNGP11.phx.gbl...
> > Donovan,
> >
> > Thanks very much for your report. This is exactly the kind of solution I
> > need, although there are still a few problems.
> >
> > I thought of doing it this way, but I am trying to fully integrate SQL
RS
> > with our Web Application. I don't want to have to explain to our
customers
> > that in order to design reports for use with our application you have to
> > always have those extra data sources present along with code to retrieve
the
> > parameters. This puts the onus on the report developer to be a coder
rather
> > than me taking care of the whole solution myself.
> >
> > I suppose I could come up with some kind of template report that our
> > customers can start with, and that would make this a workable solution
for
> > us. I am going over your report in more detail to see what I can learn
from
> > it.
> >
> > Your help has been quite valuable for my project, and I really
appreciate
> > you sending the report!
> >
> > Thank you very much indeed,
> > Malik
> >
> > "Donovan R. Smith [MSFT]" <donovans@.online.microsoft.com> wrote in
message
> > news:u8UcIjjiEHA.348@.tk2msftngp13.phx.gbl...
> > > Take a look at the attached report for help. It goes against the pubs
> > sample database and requires
> > > a SQL script to be run on the db prior to use.
> > >
> > > --
> > > Thanks.
> > >
> > > Donovan R. Smith
> > > Software Test Lead
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > > news:ekCjdEPiEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > > > Let me also clarify that the difficulty here is getting the
parameter
> > input
> > > > from the user.
> > > >
> > > > If I already know what parameters I want to run the report for,
there is
> > no
> > > > problem.
> > > >
> > > > The problem is, the user can change them and then re-run the report,
and
> > I
> > > > have no idea
> > > > what parameters are currently in the report being displayed!
> > > >
> > > > Malik
> > > >
> > > > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > > > news:uL2wf3OiEHA.536@.TK2MSFTNGP11.phx.gbl...
> > > > > I have looked at the SOAP method of integration as well as the URL
> > method,
> > > > > and it is just not possible to save report parameters as selected
by
> > the
> > > > > user! The only way you can save them is if you re-invent your own
> > > > parameter
> > > > > inputs! And keep in mind that a complete integration solution
should
> > be
> > > > able
> > > > > to accept any possible combination of report parameters!
> > > > >
> > > > > I think this is another oversight in the design of this product
from
> > > > > microsoft. They have specially designed ways to cache report data,
> > saving
> > > > > history, etc... But what about the more common case of wanting
fresh
> > data
> > > > > for the same parameters? I am amazed that they did not think of
> > this...
> > > > >
> > > > > Is there anything like this in the works for version 2... Yes?
> > > > >
> > > > > Please tell me yes :-]
> > > > >
> > > > > Malik
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>

Can't save package to Server (No description found)

I'm getting an error, "No description found", when trying to save my package to the SQL Server (2005).

It was created under the Sept. CTP (SQL 2005) and the matching BI tools, which saved fine. But now with the RTM version I'm getting this error when saving.

I'm in the process of trying different variations, i.e. saving from Sept CTP to current server.... Unforetunately I have clients in next week for training, so I have to find a quick fix or reload the Sept. CTP for training

Anybody else have this issue?

f.y.i.
I'm getting the same error when trying to save maintenance plans on the server.

Versions:
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

Sounds like something is missing, which was not required in Sep CTP, but is now mandatory for RTM. I would expect the RTM tools to fix this. Open the package with the RTM tools (BIDS), and save it again. The reload with upgrade option from the context menu within the solution explorer would also be worth a go.

What method are you using to save to SQL Server?

I have taken plenty of Sep CTP Packages and used them in RTM tools and saved to SQL, but I have worked on them first in BIDS.

|||After building a package and debugging, I'd just use the "Save Copy As" to save it to the server.

I verified it was just my machine. From the server itself and other machines in the office, I could save fine.

I had to re-image my machine so I could get back to work. Everything works fine now.

Checking versions before and after showed the same versions across the board.

Thanks for any suggestions.|||

You did listed the version of IS components.
The error you reported is consistent with older CTP.

|||

I believe it might be due to not having a Visio Service Patch:

http://support.microsoft.com/kb/922546/en-us

Can't save package to Server (No description found)

I'm getting an error, "No description found", when trying to save my package to the SQL Server (2005).

It was created under the Sept. CTP (SQL 2005) and the matching BI tools, which saved fine. But now with the RTM version I'm getting this error when saving.

I'm in the process of trying different variations, i.e. saving from Sept CTP to current server.... Unforetunately I have clients in next week for training, so I have to find a quick fix or reload the Sept. CTP for training

Anybody else have this issue?

f.y.i.
I'm getting the same error when trying to save maintenance plans on the server.

Versions:
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

Sounds like something is missing, which was not required in Sep CTP, but is now mandatory for RTM. I would expect the RTM tools to fix this. Open the package with the RTM tools (BIDS), and save it again. The reload with upgrade option from the context menu within the solution explorer would also be worth a go.

What method are you using to save to SQL Server?

I have taken plenty of Sep CTP Packages and used them in RTM tools and saved to SQL, but I have worked on them first in BIDS.

|||After building a package and debugging, I'd just use the "Save Copy As" to save it to the server.

I verified it was just my machine. From the server itself and other machines in the office, I could save fine.

I had to re-image my machine so I could get back to work. Everything works fine now.

Checking versions before and after showed the same versions across the board.

Thanks for any suggestions.|||

You did listed the version of IS components.
The error you reported is consistent with older CTP.

|||

I believe it might be due to not having a Visio Service Patch:

http://support.microsoft.com/kb/922546/en-us

Can't save or compile package (insufficient memory)

When I compile or save a SSiS package in the SQL Server Business Intelligence Development Studio I get the error

Failure saving package. (Microsoft Visual Studio)

Insufficient memory to continue the execution of the program.

Sometimes, if I wait longer time, the package can suddenly be saved.

I have 2 GB of RAM und over 15 GB of free space on my disk. Thus, there should be anough space to save the package.

What should I do to resolve this problem? It seems to be a bug.

To splitt the package would not be a solution.

How large is the package, and what version of Visual Studio are you running?

Cant save my stored procedure using VS2005

Hi!

I'm using VS2005 and trying to save my very simple stored procedure.
The error message "Invalid object name 'dbo.xxxxx' just pop's up.

The SP is written through the Server Explorer > Stored Procedures > Add new... etc.
Using SQL server 2000.

Don't think this has to do with the SP-code but here it is:

ALTER PROCEDUREdbo.KontrollUnikPersNr
@.PersNrnvarchar(50) =null OUTPUT
AS
SELECT@.PersNr = PersNrFROMUserWHEREPersNr = @.PersNr
RETURN@.@.ROWCOUNT

Thanx i advance for any help!

Looks like you are trying to ALTER a proc that does not exist. Try changing the ALTER to CREATE and see if it helps.

Also, I dont understand what you are trying to return from the stored proc - the rowcount or the value from the database?

|||

Thanx a lot!

I changed the Alter to Create and it works... didn't have to think of the in VS2003.

I'm returning the rowcount to see if there is any Users with the specific values that has to be unique in my user database table.

Thanks a lot again!Smile

|||

If you just need the count you could do it like this:

ALTER PROCEDURE dbo.KontrollUnikPersNr@.PersNrvarchar(50) =NULL,@.countint OUTPUTASBEGINSET NOCOUNT ONSELECT @.count =count(*)FROMUserWHERE PersNr = @.PersNrSET NOCOUNT OFFEND

|||

Hm, did'nt think of that... nice.

Thanx a lot again... let me know if I can help you with any tricky stuff.. erhm... Wink

Cant SAVE a view

HI,
Whats wring with the followng views? I can view the results if i run the
view without saving; but when try to save the view, I get error .
View1:
SELECT COUNT(*)
FROM dbo.Cingular_AllMin MINUS
SELECT MDN
FROM Testallmatches
VIEW2:
SELECT COUNT(*)
FROM dbo.Cingular_AllMin MINUS
SELECT mdn
FROM Testallmatches INNER JOIN
Cingular_AllMin ON
Cingular_AllMin.previousmin = Testallmatches.mdn OR
Cingular_AllMin.currentmin = Testallmatches.mdn
Error:
ODBC error: [Microdoft][odbc sql server driver][sql server] Incorrect syntax
near keyword 'SELECT'.
Please help.
Thanks
pmudMINUS is not valid T-SQL.
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:29AC1DA5-6153-4F9E-A053-330DEFA9B583@.microsoft.com...
> HI,
> Whats wring with the followng views? I can view the results if i run the
> view without saving; but when try to save the view, I get error .
> View1:
> SELECT COUNT(*)
> FROM dbo.Cingular_AllMin MINUS
> SELECT MDN
> FROM Testallmatches
> VIEW2:
> SELECT COUNT(*)
> FROM dbo.Cingular_AllMin MINUS
> SELECT mdn
> FROM Testallmatches INNER JOIN
> Cingular_AllMin ON
> Cingular_AllMin.previousmin = Testallmatches.mdn OR
> Cingular_AllMin.currentmin = Testallmatches.mdn
> Error:
> ODBC error: [Microdoft][odbc sql server driver][sql server] Incorrect
> syntax
> near keyword 'SELECT'.
> Please help.
> Thanks
> --
> pmud|||Hi Aaron,
Is there a way I can get around this problem?
Thanks
--
pmud
"Aaron Bertrand [SQL Server MVP]" wrote:

> MINUS is not valid T-SQL.
>
> "pmud" <pmud@.discussions.microsoft.com> wrote in message
> news:29AC1DA5-6153-4F9E-A053-330DEFA9B583@.microsoft.com...
>
>|||Can you show table structure, sample data, and desired results, so we can
understand what "this problem" is?
http://www.aspfaq.com/5006
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:82899AA1-B1BC-4B46-8D7B-10D9583614EB@.microsoft.com...
> Hi Aaron,
> Is there a way I can get around this problem?
> Thanks
> --
> pmud
>
> "Aaron Bertrand [SQL Server MVP]" wrote:
>

Friday, February 24, 2012

can't modify table in SMS...timeout expired?

Hi: I'm trying to add a field to a table by modifying it in Management
Studio. I'm running SQLSMS locally on the server.
When I try to save the table I get an error
"Post-Save Notifications...
[table name]
- Unable to modify table.
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding."
The table currently has 5454 rows in it.
geek-y-guy (noone@.nowhere.org) writes:
> Hi: I'm trying to add a field to a table by modifying it in Management
> Studio. I'm running SQLSMS locally on the server.
That is a very dangerous function, which has serious bugs and shortcomings.
I strongly recommend to use ALTER TABLE statements to change your tables.
Or, at the very least, never, I say NEVER, save directly to implement
a change, but always generate a script and perform these modifications:
o Remove all BEGIN and COMMIT TRANSACTION except for the first and last.
o Wrap all batches in IF @.@.trancount > 0 BEGIN ... END
o Change all WITH NOCHECK to WITH CHECK.
And be very careful to check that the script only include the
changes you want to make. There are bugs that can cause discarded
changes to be includd.

> When I try to save the table I get an error
> "Post-Save Notifications...
> [table name]
> - Unable to modify table.
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding."
> The table currently has 5454 rows in it.
Under Tools->Options there is a timeout for the Designers you can
change, if you insist on using that function. But if you run the script
from a query window,the timeout is not an issue.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Thursday, February 16, 2012

Can't install SSIS on an XP machine

Hi all,

Why would I not be able to install SSIS on an XP machine? The option is grayed out. As a matter of fact, all the options are grayed out, save for the client tools.

I'm using the September CTP.

Thanks in advance,
Anthony Rizzo, MCSE, MCDBAWhat SKU or Edition are you attempting to install?
Which options are grayed out?
Was SSIS already installed on this machine?|||It's SQL 2005 September CTP. I don't know the SKU or edition. It's build 9.00.1314.

Every single installation option is grayed out except the last option, which is Client Tools.

SSIS has never been installed on this machine before.

Thanks!
Anthony|||Sept CTP came on 2 disks. The second disk only had client tools on it. Is it possible that's what you have?

-Jamie|||I don't have media for the CTP. I downloaded the files from the CTP website. My users are attempting to install SQL via a share.|||The Enterprise Edition of SQL Server 2005 requires "Server" edition of OS (Windows 2000 or 2003 Server) for SQL/AS/RS/IS, and only allows to install Workstation Components on XP. All other editions fully support XP. I suggest downloading Developer edition if you need it on XP machine.|||Thanks! I'll download Developer today and see if that helps.