Showing posts with label access. Show all posts
Showing posts with label access. Show all posts

Friday, March 23, 2012

MSP_CUBE tables not updating with current data

Hi there,

I have recently been put into a role working with Project Server Web Access and OLAP cubes. Am experiencing trouble displaying current data in the Portfolio Analyzer in Web Access.

After adding and deleting data, inlcuding projects and resources, the updates are not reflecting when analysing the cube data. I have successfully reprocessed the cube from the Analysis Manager but still does not show current data.

When looking at the MSP_CUBE_* tables in SQL Manager, these tables directly reflect the data displayed in the cube. ie. The non-current data.

Is there a specific way to update these tables with the current data from the ProjectServer tables ?

Thanks in advance,

Ben

Updating this source data is really a Project Server issue rather than an Analysis Services one. There might be some people here that use both, but you would be better off asking in a Project/ProjectServer focused forum or newsgroup.sql

mso9.dll

Hello everyone! This is my first post so please bear with me. We have
recently re-vamped an Access application such that in each of our 5 locations
a local SQL server receives published updates from our main office server.
Remote servers also send their local updates to the master and they are in
turn propogated to all of the other remote servers. The new design works
great except for one annoying bug we have been chasing for two weeks:
"Faulting application msaccess.exe, version 9.0.0.2719, faulting module
mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user gets the
error, they hit close and it terminates Access. If they move the error off
the screen and continue working the application continues. They have
discovered this and have been doing so but the fact that the error appears
must be fixed. If anyone can point me in the right direction it would be
muchly appreciated. Thanks in advance!
- Mark
mweber@.warrenlumber.com
Hi Mark,
That's pretty good information for your first post - it
always help when people post the steps related to the
problem, the exact error message (that's a big one), etc.
mso9.dll is an Office 2000 dll and the error is with
Microsoft Access (msaccess.exe). So you are probably better
off posting this in one of the access newsgroups. You can
try
microsoft.public.access.setupconfig
or the link to the web interface (watch out for line wrap on
the link) is:
http://support.microsoft.com/newsgro...-us;newsgroups
-Sue
On Thu, 9 Sep 2004 06:53:09 -0700, "Mark Weber"
<MarkWeber@.discussions.microsoft.com> wrote:

>Hello everyone! This is my first post so please bear with me. We have
>recently re-vamped an Access application such that in each of our 5 locations
>a local SQL server receives published updates from our main office server.
>Remote servers also send their local updates to the master and they are in
>turn propogated to all of the other remote servers. The new design works
>great except for one annoying bug we have been chasing for two weeks:
>"Faulting application msaccess.exe, version 9.0.0.2719, faulting module
>mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user gets the
>error, they hit close and it terminates Access. If they move the error off
>the screen and continue working the application continues. They have
>discovered this and have been doing so but the fact that the error appears
>must be fixed. If anyone can point me in the right direction it would be
>muchly appreciated. Thanks in advance!
>- Mark
>mweber@.warrenlumber.com
|||Thanks very much for the reply Sue! I have posted it there and hopefully
someone can help us since the error is choking us!
Take care,
- Mark
"Sue Hoegemeier" wrote:

> Hi Mark,
> That's pretty good information for your first post - it
> always help when people post the steps related to the
> problem, the exact error message (that's a big one), etc.
> mso9.dll is an Office 2000 dll and the error is with
> Microsoft Access (msaccess.exe). So you are probably better
> off posting this in one of the access newsgroups. You can
> try
> microsoft.public.access.setupconfig
> or the link to the web interface (watch out for line wrap on
> the link) is:
> http://support.microsoft.com/newsgro...-us;newsgroups
> -Sue
> On Thu, 9 Sep 2004 06:53:09 -0700, "Mark Weber"
> <MarkWeber@.discussions.microsoft.com> wrote:
>
>

Friday, March 9, 2012

Msft Access, SQL Server support for Volume ShadowCopy Service (VSS)

Can anyone point me at some reference material on Microsoft Access' support
for the Volume ShadowCopy Service in WinXP Pro and Win2003 Server, please?
I am particularly interested in any information on backup of open databases
and whether the standard Microsoft OS software-based snapshot copy support
provides more than "crash-consitent" backup support (i.e., VSS "Writer"
support) for Access / SQL databases at various software release levels.
If Access doesn't support VSS, can anyone tell me whether MSDE (aka SQL
Server Lite) has VSS "Writer" support? What versions of SQL Server
provide VSS support for open databases?
Please respond to the newsgroup. Thanks in advance for any assistance.
KenThis is a multi-part message in MIME format.
--020502030000090800080205
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Ken L wrote:
> Can anyone point me at some reference material on Microsoft Access' support
> for the Volume ShadowCopy Service in WinXP Pro and Win2003 Server, please?
> I am particularly interested in any information on backup of open databases
> and whether the standard Microsoft OS software-based snapshot copy support
> provides more than "crash-consitent" backup support (i.e., VSS "Writer"
> support) for Access / SQL databases at various software release levels.
> If Access doesn't support VSS, can anyone tell me whether MSDE (aka SQL
> Server Lite) has VSS "Writer" support? What versions of SQL Server
> provide VSS support for open databases?
> Please respond to the newsgroup. Thanks in advance for any assistance.
> Ken
>
>
I don't know about Access, but maybe this link can help you with MS SQL
Server
http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlwriter.mspx
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--020502030000090800080205
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Ken L wrote:
<blockquote cite="miduXbWtwFoGHA.4232@.TK2MSFTNGP02.phx.gbl" type="cite">
<pre wrap="">Can anyone point me at some reference material on Microsoft Access' support
for the Volume ShadowCopy Service in WinXP Pro and Win2003 Server, please?
I am particularly interested in any information on backup of open databases
and whether the standard Microsoft OS software-based snapshot copy support
provides more than "crash-consitent" backup support (i.e., VSS "Writer"
support) for Access / SQL databases at various software release levels.
If Access doesn't support VSS, can anyone tell me whether MSDE (aka SQL
Server Lite) has VSS "Writer" support? What versions of SQL Server
provide VSS support for open databases?
Please respond to the newsgroup. Thanks in advance for any assistance.
Ken
</pre>
</blockquote>
<font size="-1"><font face="Arial">I don't know about Access, but maybe
this link can help you with MS SQL Server<br>
<br>
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlwriter.mspx</a><br>">http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlwriter.mspx">http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlwriter.mspx</a><br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--020502030000090800080205--

Wednesday, March 7, 2012

MSDTC unable to go online

Hi,
I have a problem starting my MSDTC.
I have enable network DTC access (following the instructions in MS KB
817064) on two of my servers before I clustered them. The DTC services run
well. After that, I configured my servers in cluster Node A and B
(Active/Passive). The DTC immediately failed to start. I carried on and
configured my MSDTC resources (following the instructions in MS KB 301600) on
Node A. The other resources like IP, Physical disk, Network name able to
bring online except for DTC.
What is happening? I have tried my best to follow all instructions as
closely as possible. I seems to be struck. Still have to install SQL 2005
but now spend days to resolve the MSDTC issue. Please kindly help me!
Thanks a lot in advance!
Received error like
MS DTC was unable to start because the installation was not configured to
run on a cluster. Please create a MS DTC resource through cluster
administrator. Error Specifics:
d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:534, Pid: 3192,
CmdLine: C:\WINDOWS\system32\msdtc.exe
Could not start the MS DTC Transaction Manager.
MS DTC Transaction Manager start failed. LogInit returned error 0x3.
Dear Shann Lim,
Have a look at this KB http://support.microsoft.com/kb/867520
and let us know if that solved your problem
good luck,
Edwin.
"Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message
news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
> Hi,
> I have a problem starting my MSDTC.
> I have enable network DTC access (following the instructions in MS KB
> 817064) on two of my servers before I clustered them. The DTC services
run
> well. After that, I configured my servers in cluster Node A and B
> (Active/Passive). The DTC immediately failed to start. I carried on and
> configured my MSDTC resources (following the instructions in MS KB 301600)
on
> Node A. The other resources like IP, Physical disk, Network name able to
> bring online except for DTC.
> What is happening? I have tried my best to follow all instructions as
> closely as possible. I seems to be struck. Still have to install SQL
2005
> but now spend days to resolve the MSDTC issue. Please kindly help me!
> Thanks a lot in advance!
> Received error like
> MS DTC was unable to start because the installation was not configured to
> run on a cluster. Please create a MS DTC resource through cluster
> administrator. Error Specifics:
> d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:534, Pid:
3192,
> CmdLine: C:\WINDOWS\system32\msdtc.exe
> Could not start the MS DTC Transaction Manager.
> MS DTC Transaction Manager start failed. LogInit returned error 0x3.
>
>
>
>
|||Microsoft has a fix that I have used several times. Free from PSS. Only the web page for version 6 & 7 are not on the net today.
Google shows this though:
Availability of the Windows Server 2003 Post-Service Pack 1 COM+ ...897667 (http://support.microsoft.com/kb/897667/) Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...
support.microsoft.com/kb/921981 - Similar pages
Could be because SP2 is right around the corner now...
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
> Hi,
> I have a problem starting my MSDTC.
> I have enable network DTC access (following the instructions in MS KB
> 817064) on two of my servers before I clustered them. The DTC services run
> well. After that, I configured my servers in cluster Node A and B
> (Active/Passive). The DTC immediately failed to start. I carried on and
> configured my MSDTC resources (following the instructions in MS KB 301600) on
> Node A. The other resources like IP, Physical disk, Network name able to
> bring online except for DTC.
> What is happening? I have tried my best to follow all instructions as
> closely as possible. I seems to be struck. Still have to install SQL 2005
> but now spend days to resolve the MSDTC issue. Please kindly help me!
> Thanks a lot in advance!
> Received error like
> MS DTC was unable to start because the installation was not configured to
> run on a cluster. Please create a MS DTC resource through cluster
> administrator. Error Specifics:
> d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:534, Pid: 3192,
> CmdLine: C:\WINDOWS\system32\msdtc.exe
> Could not start the MS DTC Transaction Manager.
> MS DTC Transaction Manager start failed. LogInit returned error 0x3.
>
>
>
>
|||Hi,
I appreciate all the helps.
But may I noe where to d/l the COM+ patch?
Thank you.
"Rodney R. Fournier [MVP]" wrote:
[vbcol=seagreen]
> Microsoft has a fix that I have used several times. Free from PSS. Only the web page for version 6 & 7 are not on the net today.
> Google shows this though:
> Availability of the Windows Server 2003 Post-Service Pack 1 COM+ ...897667 (http://support.microsoft.com/kb/897667/) Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...
> support.microsoft.com/kb/921981 - Similar pages
>
> Could be because SP2 is right around the corner now...
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
|||Hi,
Sorry. I think I forgotten to include that I am using Win2k3 SP 1 for my
nodes. THe articles given by Mr Fournier and Mr Mierlo seems to be for
Win2k. Is it applicable for my case?
Thanks again.
"Rodney R. Fournier [MVP]" wrote:
[vbcol=seagreen]
> Microsoft has a fix that I have used several times. Free from PSS. Only the web page for version 6 & 7 are not on the net today.
> Google shows this though:
> Availability of the Windows Server 2003 Post-Service Pack 1 COM+ ...897667 (http://support.microsoft.com/kb/897667/) Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...
> support.microsoft.com/kb/921981 - Similar pages
>
> Could be because SP2 is right around the corner now...
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
|||Dear Shann Lim,
http://support.microsoft.com/kb/897667
is for Windows 2003
HTH,
Edwin.
"Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message
news:D3B191E6-503E-445A-8B0D-20109E5D1E7F@.microsoft.com...[vbcol=seagreen]
> Hi,
> Sorry. I think I forgotten to include that I am using Win2k3 SP 1 for my
> nodes. THe articles given by Mr Fournier and Mr Mierlo seems to be for
> Win2k. Is it applicable for my case?
> Thanks again.
> "Rodney R. Fournier [MVP]" wrote:
the web page for version 6 & 7 are not on the net today.[vbcol=seagreen]
....897667 (http://support.microsoft.com/kb/897667/) Availability of Windows
Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...[vbcol=seagreen]
news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...[vbcol=seagreen]
services run[vbcol=seagreen]
and[vbcol=seagreen]
301600) on[vbcol=seagreen]
to[vbcol=seagreen]
2005[vbcol=seagreen]
to[vbcol=seagreen]
Pid: 3192,[vbcol=seagreen]

MSDTC on server 'SERVER_NAME' is unavailable

Hi
I have two stored procedures that use a linked server to access an Access
database from SQL Server 2000.
The first takes no input:
CREATE PROCEDURE GetModules
AS
INSERT INTO datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime) SELECT * FROM
OPENQUERY(ProjAForcBCase0,'select * from datCase')
GO
This procedure runs fine and does exactly as expected.
The second parameterises the linked server name (the idea being that these
will be created dynamically in code) so that it can be passed in to the
stored procedure.
CREATE PROCEDURE GetModulesDynamic
@.LinkedServer nvarchar(4000)
AS
DECLARE @.TSQL nvarchar(4000)
DECLARE @.OPENQUERY nvarchar(4000)
SET @.OPENQUERY = 'SELECT * FROM OPENQUERY('+ @.LinkedServer + ','''
SET @.TSQL = 'select * from datCase'')'
Insert into datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime)
EXEC(@.OPENQUERY+@.TSQL)
GO
However if I run this second stored procedure I am met with the error
message "MSDTC on server 'SERVER_NAME' is unavailable".
Both these stored procedures were executed on my PC (win 2K) using a local
SQL Server 2000 instance and a localo access database. As such I do not
understand why I should require MSDTC for the second procedure and not for
the first.
Any explanation would be extremely useful.
Also can MSDTC be installed on Win 2K and if so where can I get it from?
Thanks
TomHave just dicovered that I didn't have DTC running (had been looking for a
service called MSDTC as defined in the error message)
As such this now works as expected for both procedures, but if anyone knows
why it worked without DTC for the first procedure and not the second I would
be interested in an explanation.
"TomPearson" wrote:

> Hi
> I have two stored procedures that use a linked server to access an Access
> database from SQL Server 2000.
> The first takes no input:
> CREATE PROCEDURE GetModules
> AS
> INSERT INTO datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
> UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime) SELECT * FROM
> OPENQUERY(ProjAForcBCase0,'select * from datCase')
> GO
> This procedure runs fine and does exactly as expected.
> The second parameterises the linked server name (the idea being that these
> will be created dynamically in code) so that it can be passed in to the
> stored procedure.
> CREATE PROCEDURE GetModulesDynamic
> @.LinkedServer nvarchar(4000)
> AS
> DECLARE @.TSQL nvarchar(4000)
> DECLARE @.OPENQUERY nvarchar(4000)
> SET @.OPENQUERY = 'SELECT * FROM OPENQUERY('+ @.LinkedServer + ','''
> SET @.TSQL = 'select * from datCase'')'
> Insert into datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
> UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime)
> EXEC(@.OPENQUERY+@.TSQL)
> GO
> However if I run this second stored procedure I am met with the error
> message "MSDTC on server 'SERVER_NAME' is unavailable".
> Both these stored procedures were executed on my PC (win 2K) using a local
> SQL Server 2000 instance and a localo access database. As such I do not
> understand why I should require MSDTC for the second procedure and not for
> the first.
> Any explanation would be extremely useful.
> Also can MSDTC be installed on Win 2K and if so where can I get it from?
> Thanks
> Tom|||Most likely because in the second procedure, you used an
insert exec which would promote the transaction to a
distributed transaction. The first procedure used an insert
select so was a local transaction.
-Sue
On Mon, 31 Jan 2005 07:45:03 -0800, "TomPearson"
<TomPearson@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Have just dicovered that I didn't have DTC running (had been looking for a
>service called MSDTC as defined in the error message)
>As such this now works as expected for both procedures, but if anyone knows
>why it worked without DTC for the first procedure and not the second I woul
d
>be interested in an explanation.
>"TomPearson" wrote:
>

MSDTC on server 'SERVER_NAME' is unavailable

Hi
I have two stored procedures that use a linked server to access an Access
database from SQL Server 2000.
The first takes no input:
CREATE PROCEDURE GetModules
AS
INSERT INTO datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime) SELECT * FROM
OPENQUERY(ProjAForcBCase0,'select * from datCase')
GO
This procedure runs fine and does exactly as expected.
The second parameterises the linked server name (the idea being that these
will be created dynamically in code) so that it can be passed in to the
stored procedure.
CREATE PROCEDURE GetModulesDynamic
@.LinkedServer nvarchar(4000)
AS
DECLARE @.TSQL nvarchar(4000)
DECLARE @.OPENQUERY nvarchar(4000)
SET @.OPENQUERY = 'SELECT * FROM OPENQUERY('+ @.LinkedServer + ','''
SET @.TSQL = 'select * from datCase'')'
Insert into datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime)
EXEC(@.OPENQUERY+@.TSQL)
GO
However if I run this second stored procedure I am met with the error
message "MSDTC on server 'SERVER_NAME' is unavailable".
Both these stored procedures were executed on my PC (win 2K) using a local
SQL Server 2000 instance and a localo access database. As such I do not
understand why I should require MSDTC for the second procedure and not for
the first.
Any explanation would be extremely useful.
Also can MSDTC be installed on Win 2K and if so where can I get it from?
Thanks
Tom
Have just dicovered that I didn't have DTC running (had been looking for a
service called MSDTC as defined in the error message)
As such this now works as expected for both procedures, but if anyone knows
why it worked without DTC for the first procedure and not the second I would
be interested in an explanation.
"TomPearson" wrote:

> Hi
> I have two stored procedures that use a linked server to access an Access
> database from SQL Server 2000.
> The first takes no input:
> CREATE PROCEDURE GetModules
> AS
> INSERT INTO datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
> UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime) SELECT * FROM
> OPENQUERY(ProjAForcBCase0,'select * from datCase')
> GO
> This procedure runs fine and does exactly as expected.
> The second parameterises the linked server name (the idea being that these
> will be created dynamically in code) so that it can be passed in to the
> stored procedure.
> CREATE PROCEDURE GetModulesDynamic
> @.LinkedServer nvarchar(4000)
> AS
> DECLARE @.TSQL nvarchar(4000)
> DECLARE @.OPENQUERY nvarchar(4000)
> SET @.OPENQUERY = 'SELECT * FROM OPENQUERY('+ @.LinkedServer + ','''
> SET @.TSQL = 'select * from datCase'')'
> Insert into datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
> UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime)
> EXEC(@.OPENQUERY+@.TSQL)
> GO
> However if I run this second stored procedure I am met with the error
> message "MSDTC on server 'SERVER_NAME' is unavailable".
> Both these stored procedures were executed on my PC (win 2K) using a local
> SQL Server 2000 instance and a localo access database. As such I do not
> understand why I should require MSDTC for the second procedure and not for
> the first.
> Any explanation would be extremely useful.
> Also can MSDTC be installed on Win 2K and if so where can I get it from?
> Thanks
> Tom
|||Most likely because in the second procedure, you used an
insert exec which would promote the transaction to a
distributed transaction. The first procedure used an insert
select so was a local transaction.
-Sue
On Mon, 31 Jan 2005 07:45:03 -0800, "TomPearson"
<TomPearson@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Have just dicovered that I didn't have DTC running (had been looking for a
>service called MSDTC as defined in the error message)
>As such this now works as expected for both procedures, but if anyone knows
>why it worked without DTC for the first procedure and not the second I would
>be interested in an explanation.
>"TomPearson" wrote:

MSDTC on server 'SERVER_NAME' is unavailable

Hi
I have two stored procedures that use a linked server to access an Access
database from SQL Server 2000.
The first takes no input:
CREATE PROCEDURE GetModules
AS
INSERT INTO datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime) SELECT * FROM
OPENQUERY(ProjAForcBCase0,'select * from datCase')
GO
This procedure runs fine and does exactly as expected.
The second parameterises the linked server name (the idea being that these
will be created dynamically in code) so that it can be passed in to the
stored procedure.
CREATE PROCEDURE GetModulesDynamic
@.LinkedServer nvarchar(4000)
AS
DECLARE @.TSQL nvarchar(4000)
DECLARE @.OPENQUERY nvarchar(4000)
SET @.OPENQUERY = 'SELECT * FROM OPENQUERY('+ @.LinkedServer + ','''
SET @.TSQL = 'select * from datCase'')'
Insert into datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime)
EXEC(@.OPENQUERY+@.TSQL)
GO
However if I run this second stored procedure I am met with the error
message "MSDTC on server 'SERVER_NAME' is unavailable".
Both these stored procedures were executed on my PC (win 2K) using a local
SQL Server 2000 instance and a localo access database. As such I do not
understand why I should require MSDTC for the second procedure and not for
the first.
Any explanation would be extremely useful.
Also can MSDTC be installed on Win 2K and if so where can I get it from?
Thanks
TomHave just dicovered that I didn't have DTC running (had been looking for a
service called MSDTC as defined in the error message)
As such this now works as expected for both procedures, but if anyone knows
why it worked without DTC for the first procedure and not the second I would
be interested in an explanation.
"TomPearson" wrote:
> Hi
> I have two stored procedures that use a linked server to access an Access
> database from SQL Server 2000.
> The first takes no input:
> CREATE PROCEDURE GetModules
> AS
> INSERT INTO datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
> UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime) SELECT * FROM
> OPENQUERY(ProjAForcBCase0,'select * from datCase')
> GO
> This procedure runs fine and does exactly as expected.
> The second parameterises the linked server name (the idea being that these
> will be created dynamically in code) so that it can be passed in to the
> stored procedure.
> CREATE PROCEDURE GetModulesDynamic
> @.LinkedServer nvarchar(4000)
> AS
> DECLARE @.TSQL nvarchar(4000)
> DECLARE @.OPENQUERY nvarchar(4000)
> SET @.OPENQUERY = 'SELECT * FROM OPENQUERY('+ @.LinkedServer + ','''
> SET @.TSQL = 'select * from datCase'')'
> Insert into datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
> UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime)
> EXEC(@.OPENQUERY+@.TSQL)
> GO
> However if I run this second stored procedure I am met with the error
> message "MSDTC on server 'SERVER_NAME' is unavailable".
> Both these stored procedures were executed on my PC (win 2K) using a local
> SQL Server 2000 instance and a localo access database. As such I do not
> understand why I should require MSDTC for the second procedure and not for
> the first.
> Any explanation would be extremely useful.
> Also can MSDTC be installed on Win 2K and if so where can I get it from?
> Thanks
> Tom|||Most likely because in the second procedure, you used an
insert exec which would promote the transaction to a
distributed transaction. The first procedure used an insert
select so was a local transaction.
-Sue
On Mon, 31 Jan 2005 07:45:03 -0800, "TomPearson"
<TomPearson@.discussions.microsoft.com> wrote:
>Have just dicovered that I didn't have DTC running (had been looking for a
>service called MSDTC as defined in the error message)
>As such this now works as expected for both procedures, but if anyone knows
>why it worked without DTC for the first procedure and not the second I would
>be interested in an explanation.
>"TomPearson" wrote:
>> Hi
>> I have two stored procedures that use a linked server to access an Access
>> database from SQL Server 2000.
>> The first takes no input:
>> CREATE PROCEDURE GetModules
>> AS
>> INSERT INTO datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
>> UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime) SELECT * FROM
>> OPENQUERY(ProjAForcBCase0,'select * from datCase')
>> GO
>> This procedure runs fine and does exactly as expected.
>> The second parameterises the linked server name (the idea being that these
>> will be created dynamically in code) so that it can be passed in to the
>> stored procedure.
>> CREATE PROCEDURE GetModulesDynamic
>> @.LinkedServer nvarchar(4000)
>> AS
>> DECLARE @.TSQL nvarchar(4000)
>> DECLARE @.OPENQUERY nvarchar(4000)
>> SET @.OPENQUERY = 'SELECT * FROM OPENQUERY('+ @.LinkedServer + ','''
>> SET @.TSQL = 'select * from datCase'')'
>> Insert into datCase( CaseNumber, DateCreated, DateLastRun, VisoObject,
>> UserVBA, VisoDiagram, CF, CaseDescription, LastRunTime)
>> EXEC(@.OPENQUERY+@.TSQL)
>> GO
>> However if I run this second stored procedure I am met with the error
>> message "MSDTC on server 'SERVER_NAME' is unavailable".
>> Both these stored procedures were executed on my PC (win 2K) using a local
>> SQL Server 2000 instance and a localo access database. As such I do not
>> understand why I should require MSDTC for the second procedure and not for
>> the first.
>> Any explanation would be extremely useful.
>> Also can MSDTC be installed on Win 2K and if so where can I get it from?
>> Thanks
>> Tom

Monday, February 20, 2012

MSDN Subscription Level for latest Yukon CTP

I'm working on some research that requires me to have access to the
latest CTP of Yukon, and I know it's available via MSDN subscription.
Can anyone tell me the minimum subscription level required to have
download access to the CTP?
Thanks
AllenSearch for SQL ServerT 2005 within
http://msdn.microsoft.com/subscript...ackinglist.aspx
It looks like it is included with MSDN Professional.
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:825fv05697ud46c5iqrm63r9gl8fhep73e@.
4ax.com...
> I'm working on some research that requires me to have access to the
> latest CTP of Yukon, and I know it's available via MSDN subscription.
> Can anyone tell me the minimum subscription level required to have
> download access to the CTP?
> Thanks
> Allen|||Thanks, Kieth, but in the shipment lists in all levels it only shows
Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
is available for download on the web site at least at the Universal
level. I'm looking to find out the minimum level at which it's
available.
Allen
On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
<sqlguy.back2u@.comcast.net> wrote:

>Search for SQL ServerT 2005 within
>http://msdn.microsoft.com/subscript...ackinglist.aspx
>It looks like it is included with MSDN Professional.|||My point is:
If it ships with version x of the MSDN Subscription then it should be
available via the download center.
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:lm6fv0h1d1r4mdjmjeiedsro5g2nbe9jnp@.
4ax.com...
> Thanks, Kieth, but in the shipment lists in all levels it only shows
> Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
> is available for download on the web site at least at the Universal
> level. I'm looking to find out the minimum level at which it's
> available.
> Allen
> On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
> <sqlguy.back2u@.comcast.net> wrote:
>
>|||Keith Kratochvil wrote:

>My point is:
>If it ships with version x of the MSDN Subscription then it should be
>available via the download center.
>
>
Yes, but the converse is not true. The download center provides much more
than what is shipped. The CTP builds of SQL Server, not the Beta releases,
are what the poster asked about, and they are not included in any MSDN
shipments, so the shipment lists won't help answer the question.
I believe the two CTP builds released so far are available to all
MSDN subscribers, regardless of subscription level. At least that's
what it says at
http://www.microsoft.com/presspass/...erLowCostPR.asp
I haven't heard anyone complain that they are an MSDN
subscriber but couldn't get the CTP, either. For the record,
the December CTP of the Express version (the SQL engine
with some limitations and no tools) is available to anyone,
MSDN subscriber or not, here:
http://lab.msdn.microsoft.com/express/sql/
Steve Kass
Drew University|||Thanks
Keith|||Thanks, Steve. That linked helped a lot.
Allen
On Wed, 26 Jan 2005 09:35:31 -0500, Steve Kass <skass@.drew.edu> wrote:

>
>Keith Kratochvil wrote:
>
>Yes, but the converse is not true. The download center provides much more
>than what is shipped. The CTP builds of SQL Server, not the Beta releases,
>are what the poster asked about, and they are not included in any MSDN
>shipments, so the shipment lists won't help answer the question.
>I believe the two CTP builds released so far are available to all
>MSDN subscribers, regardless of subscription level. At least that's
>what it says at
>http://www.microsoft.com/presspass/...om/express/sql/
>Steve Kass
>Drew University

MSDN Subscription Level for latest Yukon CTP

I'm working on some research that requires me to have access to the
latest CTP of Yukon, and I know it's available via MSDN subscription.
Can anyone tell me the minimum subscription level required to have
download access to the CTP?
Thanks
Allen
Search for SQL ServerT 2005 within
http://msdn.microsoft.com/subscripti...ckinglist.aspx
It looks like it is included with MSDN Professional.
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:825fv05697ud46c5iqrm63r9gl8fhep73e@.4ax.com...
> I'm working on some research that requires me to have access to the
> latest CTP of Yukon, and I know it's available via MSDN subscription.
> Can anyone tell me the minimum subscription level required to have
> download access to the CTP?
> Thanks
> Allen
|||Thanks, Kieth, but in the shipment lists in all levels it only shows
Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
is available for download on the web site at least at the Universal
level. I'm looking to find out the minimum level at which it's
available.
Allen
On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
<sqlguy.back2u@.comcast.net> wrote:

>Search for SQL ServerT 2005 within
>http://msdn.microsoft.com/subscripti...ckinglist.aspx
>It looks like it is included with MSDN Professional.
|||My point is:
If it ships with version x of the MSDN Subscription then it should be
available via the download center.
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:lm6fv0h1d1r4mdjmjeiedsro5g2nbe9jnp@.4ax.com...
> Thanks, Kieth, but in the shipment lists in all levels it only shows
> Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
> is available for download on the web site at least at the Universal
> level. I'm looking to find out the minimum level at which it's
> available.
> Allen
> On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
> <sqlguy.back2u@.comcast.net> wrote:
>
|||Keith Kratochvil wrote:

>My point is:
>If it ships with version x of the MSDN Subscription then it should be
>available via the download center.
>
>
Yes, but the converse is not true. The download center provides much more
than what is shipped. The CTP builds of SQL Server, not the Beta releases,
are what the poster asked about, and they are not included in any MSDN
shipments, so the shipment lists won't help answer the question.
I believe the two CTP builds released so far are available to all
MSDN subscribers, regardless of subscription level. At least that's
what it says at
http://www.microsoft.com/presspass/p...rLowCostPR.asp
I haven't heard anyone complain that they are an MSDN
subscriber but couldn't get the CTP, either. For the record,
the December CTP of the Express version (the SQL engine
with some limitations and no tools) is available to anyone,
MSDN subscriber or not, here:
http://lab.msdn.microsoft.com/express/sql/
Steve Kass
Drew University
|||Thanks
Keith
|||Thanks, Steve. That linked helped a lot.
Allen
On Wed, 26 Jan 2005 09:35:31 -0500, Steve Kass <skass@.drew.edu> wrote:

>
>Keith Kratochvil wrote:
>Yes, but the converse is not true. The download center provides much more
>than what is shipped. The CTP builds of SQL Server, not the Beta releases,
>are what the poster asked about, and they are not included in any MSDN
>shipments, so the shipment lists won't help answer the question.
>I believe the two CTP builds released so far are available to all
>MSDN subscribers, regardless of subscription level. At least that's
>what it says at
>http://www.microsoft.com/presspass/p...rLowCostPR.asp
>I haven't heard anyone complain that they are an MSDN
>subscriber but couldn't get the CTP, either. For the record,
>the December CTP of the Express version (the SQL engine
>with some limitations and no tools) is available to anyone,
>MSDN subscriber or not, here:
>http://lab.msdn.microsoft.com/express/sql/
>Steve Kass
>Drew University

MSDN Subscription Level for latest Yukon CTP

I'm working on some research that requires me to have access to the
latest CTP of Yukon, and I know it's available via MSDN subscription.
Can anyone tell me the minimum subscription level required to have
download access to the CTP?
Thanks
AllenSearch for SQL ServerT 2005 within
http://msdn.microsoft.com/subscriptions/index/packinglist.aspx
It looks like it is included with MSDN Professional.
--
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:825fv05697ud46c5iqrm63r9gl8fhep73e@.4ax.com...
> I'm working on some research that requires me to have access to the
> latest CTP of Yukon, and I know it's available via MSDN subscription.
> Can anyone tell me the minimum subscription level required to have
> download access to the CTP?
> Thanks
> Allen|||Thanks, Kieth, but in the shipment lists in all levels it only shows
Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
is available for download on the web site at least at the Universal
level. I'm looking to find out the minimum level at which it's
available.
Allen
On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
<sqlguy.back2u@.comcast.net> wrote:
>Search for SQL ServerT 2005 within
>http://msdn.microsoft.com/subscriptions/index/packinglist.aspx
>It looks like it is included with MSDN Professional.|||My point is:
If it ships with version x of the MSDN Subscription then it should be
available via the download center.
--
Keith
"Allen White" <amwhite@.oco.net> wrote in message
news:lm6fv0h1d1r4mdjmjeiedsro5g2nbe9jnp@.4ax.com...
> Thanks, Kieth, but in the shipment lists in all levels it only shows
> Beta 2 of SQL Server 2005, and I know that the CTP (Beta 3, currently)
> is available for download on the web site at least at the Universal
> level. I'm looking to find out the minimum level at which it's
> available.
> Allen
> On Wed, 26 Jan 2005 07:12:38 -0600, "Keith Kratochvil"
> <sqlguy.back2u@.comcast.net> wrote:
> >Search for SQL ServerT 2005 within
> >http://msdn.microsoft.com/subscriptions/index/packinglist.aspx
> >It looks like it is included with MSDN Professional.
>|||Keith Kratochvil wrote:
>My point is:
>If it ships with version x of the MSDN Subscription then it should be
>available via the download center.
>
>
Yes, but the converse is not true. The download center provides much more
than what is shipped. The CTP builds of SQL Server, not the Beta releases,
are what the poster asked about, and they are not included in any MSDN
shipments, so the shipment lists won't help answer the question.
I believe the two CTP builds released so far are available to all
MSDN subscribers, regardless of subscription level. At least that's
what it says at
http://www.microsoft.com/presspass/press/2004/dec04/12-03ServerLowCostPR.asp
I haven't heard anyone complain that they are an MSDN
subscriber but couldn't get the CTP, either. For the record,
the December CTP of the Express version (the SQL engine
with some limitations and no tools) is available to anyone,
MSDN subscriber or not, here:
http://lab.msdn.microsoft.com/express/sql/
Steve Kass
Drew University|||Thanks
--
Keith|||Thanks, Steve. That linked helped a lot.
Allen
On Wed, 26 Jan 2005 09:35:31 -0500, Steve Kass <skass@.drew.edu> wrote:
>
>Keith Kratochvil wrote:
>>My point is:
>>If it ships with version x of the MSDN Subscription then it should be
>>available via the download center.
>>
>Yes, but the converse is not true. The download center provides much more
>than what is shipped. The CTP builds of SQL Server, not the Beta releases,
>are what the poster asked about, and they are not included in any MSDN
>shipments, so the shipment lists won't help answer the question.
>I believe the two CTP builds released so far are available to all
>MSDN subscribers, regardless of subscription level. At least that's
>what it says at
>http://www.microsoft.com/presspass/press/2004/dec04/12-03ServerLowCostPR.asp
>I haven't heard anyone complain that they are an MSDN
>subscriber but couldn't get the CTP, either. For the record,
>the December CTP of the Express version (the SQL engine
>with some limitations and no tools) is available to anyone,
>MSDN subscriber or not, here:
>http://lab.msdn.microsoft.com/express/sql/
>Steve Kass
>Drew University