may I push a subscription to a server while that 'machine' is running the
application which is accessing the database?
You can, but its not advisable. When you send your subscription the data in
the tables is replaced unless you are doing the nosync option. This
replacement can involve dropping the table and recreating it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:e8qmPZP%23EHA.1392@.tk2msftngp13.phx.gbl...
> may I push a subscription to a server while that 'machine' is running the
> application which is accessing the database?
>
Showing posts with label running. Show all posts
Showing posts with label running. Show all posts
Monday, March 26, 2012
Wednesday, March 21, 2012
Purchasing And Licensing
If we own two standard edition SQL Server licenses that we can use for Report Services and a SQL Server running on another server, how does the report server recognize I have a valid license? The setup doesn't ask for any sort of license key... we don't want to install SQL server on our actual report server.
Also, how do I buy Report Services Standard Edition? I have an MSDN Universal subscription and have downloaded the developer edition, but it's time for me to use this tool in production.
-kind regards, Brian Parkerthe installation doesn't ask for any license information, and you don't have
to install sql server on your report server.
I'm not sure if RS really validates any licensing information. but the
license is the Microsoft document.
To Get RS Standard edition, go to the SQL Server web site, fill the form and
Microsoft send the RS CD Rom.
"Brian Parker" <BrianParker@.discussions.microsoft.com> a écrit dans le
message de news:C76B1A30-2238-4B3F-83E1-EBA902952969@.microsoft.com...
> If we own two standard edition SQL Server licenses that we can use for
Report Services and a SQL Server running on another server, how does the
report server recognize I have a valid license? The setup doesn't ask for
any sort of license key... we don't want to install SQL server on our
actual report server.
> Also, how do I buy Report Services Standard Edition? I have an MSDN
Universal subscription and have downloaded the developer edition, but it's
time for me to use this tool in production.
> -kind regards, Brian Parker|||You will need to buy a SQL Standard license for your server that runs RS if
it separate from your existing SQL Server licensed server.
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
news:%23Rjwx7xdEHA.3664@.TK2MSFTNGP12.phx.gbl...
> the installation doesn't ask for any license information, and you don't
have
> to install sql server on your report server.
> I'm not sure if RS really validates any licensing information. but the
> license is the Microsoft document.
> To Get RS Standard edition, go to the SQL Server web site, fill the form
and
> Microsoft send the RS CD Rom.
> "Brian Parker" <BrianParker@.discussions.microsoft.com> a écrit dans le
> message de news:C76B1A30-2238-4B3F-83E1-EBA902952969@.microsoft.com...
> > If we own two standard edition SQL Server licenses that we can use for
> Report Services and a SQL Server running on another server, how does the
> report server recognize I have a valid license? The setup doesn't ask for
> any sort of license key... we don't want to install SQL server on our
> actual report server.
> >
> > Also, how do I buy Report Services Standard Edition? I have an MSDN
> Universal subscription and have downloaded the developer edition, but it's
> time for me to use this tool in production.
> >
> > -kind regards, Brian Parker
>
Also, how do I buy Report Services Standard Edition? I have an MSDN Universal subscription and have downloaded the developer edition, but it's time for me to use this tool in production.
-kind regards, Brian Parkerthe installation doesn't ask for any license information, and you don't have
to install sql server on your report server.
I'm not sure if RS really validates any licensing information. but the
license is the Microsoft document.
To Get RS Standard edition, go to the SQL Server web site, fill the form and
Microsoft send the RS CD Rom.
"Brian Parker" <BrianParker@.discussions.microsoft.com> a écrit dans le
message de news:C76B1A30-2238-4B3F-83E1-EBA902952969@.microsoft.com...
> If we own two standard edition SQL Server licenses that we can use for
Report Services and a SQL Server running on another server, how does the
report server recognize I have a valid license? The setup doesn't ask for
any sort of license key... we don't want to install SQL server on our
actual report server.
> Also, how do I buy Report Services Standard Edition? I have an MSDN
Universal subscription and have downloaded the developer edition, but it's
time for me to use this tool in production.
> -kind regards, Brian Parker|||You will need to buy a SQL Standard license for your server that runs RS if
it separate from your existing SQL Server licensed server.
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
news:%23Rjwx7xdEHA.3664@.TK2MSFTNGP12.phx.gbl...
> the installation doesn't ask for any license information, and you don't
have
> to install sql server on your report server.
> I'm not sure if RS really validates any licensing information. but the
> license is the Microsoft document.
> To Get RS Standard edition, go to the SQL Server web site, fill the form
and
> Microsoft send the RS CD Rom.
> "Brian Parker" <BrianParker@.discussions.microsoft.com> a écrit dans le
> message de news:C76B1A30-2238-4B3F-83E1-EBA902952969@.microsoft.com...
> > If we own two standard edition SQL Server licenses that we can use for
> Report Services and a SQL Server running on another server, how does the
> report server recognize I have a valid license? The setup doesn't ask for
> any sort of license key... we don't want to install SQL server on our
> actual report server.
> >
> > Also, how do I buy Report Services Standard Edition? I have an MSDN
> Universal subscription and have downloaded the developer edition, but it's
> time for me to use this tool in production.
> >
> > -kind regards, Brian Parker
>
Tuesday, March 20, 2012
pulling ntext values sql server 2005
hi,
i have a column of type ntext in the db, we're using that to allow
users to store essays they can enter. problem is when i'm running a
select on the ntext column, data seems to be getting cut off, isn't
ntext suppose to hold a lot of data, we wanted to allow them in a min
of 1500 chars, while everytime i do a
select len(max (convert(nvarchar(2000), essaytext)))
What tool are you using for this? If it's QA, you can adjust what it returns
via a setting.
>
>
>
What tool are you using for this? If it's QA, you can adjust what it returns
via a setting.
>
--
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com|||I think i found it, the stored proc doing the actual insert into the
table, was set to @.ESSAYTEXT varchar(200) for that column, we decided
to restrict it to 2000 chars, so changing it to @.ESSAYTEXT
varchar(2000), hopefully that's fix it, the varchar(200) explains the
max(len issue as well.
>
>
>
>
>
>
"phil2phil" <philtwophil@.yahoo.comwrote in message
news:1173717649.377685.103280@.h3g2000cwc.googlegro ups.com...
Yeah.. if you're only inserting 200.. ;-)
i have a column of type ntext in the db, we're using that to allow
users to store essays they can enter. problem is when i'm running a
select on the ntext column, data seems to be getting cut off, isn't
ntext suppose to hold a lot of data, we wanted to allow them in a min
of 1500 chars, while everytime i do a
select len(max (convert(nvarchar(2000), essaytext)))
just to see the max we one had it's always 200.
Thanks.
"phil2phil" <philtwophil@.yahoo.comwrote in message
news:1173714656.510142.22770@.v33g2000cwv.googlegro ups.com...
Quote:
Originally Posted by
hi,
i have a column of type ntext in the db, we're using that to allow
users to store essays they can enter. problem is when i'm running a
select on the ntext column, data seems to be getting cut off, isn't
ntext suppose to hold a lot of data, we wanted to allow them in a min
of 1500 chars, while everytime i do a
select len(max (convert(nvarchar(2000), essaytext)))
>
just to see the max we one had it's always 200.
>
Thanks.
>
What tool are you using for this? If it's QA, you can adjust what it returns
via a setting.
--
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com|||Hi,
I've tried both Sql sever 2000 QA and Sql server 2005 Management
Studio. For QA i set the Results Max chars to 8192 and in Management
studio i set the max chars per column for Text Retults to 8192 and for
Grid to Non XML 65535, but it's still not returning the full, and each
max length is always 200.
On Mar 12, 12:11 pm, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.comwrote:
Quote:
Originally Posted by
"phil2phil" <philtwop...@.yahoo.comwrote in message
>
news:1173714656.510142.22770@.v33g2000cwv.googlegro ups.com...
>
Quote:
Originally Posted by
hi,
i have a column of type ntext in the db, we're using that to allow
users to store essays they can enter. problem is when i'm running a
select on the ntext column, data seems to be getting cut off, isn't
ntext suppose to hold a lot of data, we wanted to allow them in a min
of 1500 chars, while everytime i do a
select len(max (convert(nvarchar(2000), essaytext)))
>
Quote:
Originally Posted by
just to see the max we one had it's always 200.
>
Quote:
Originally Posted by
Thanks.
>
What tool are you using for this? If it's QA, you can adjust what it returns
via a setting.
>
--
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com|||I think i found it, the stored proc doing the actual insert into the
table, was set to @.ESSAYTEXT varchar(200) for that column, we decided
to restrict it to 2000 chars, so changing it to @.ESSAYTEXT
varchar(2000), hopefully that's fix it, the varchar(200) explains the
max(len issue as well.
On Mar 12, 12:26 pm, "phil2phil" <philtwop...@.yahoo.comwrote:
Quote:
Originally Posted by
Hi,
I've tried both Sql sever 2000 QA and Sql server 2005 Management
Studio. For QA i set the Results Max chars to 8192 and in Management
studio i set the max chars per column for Text Retults to 8192 and for
Grid to Non XML 65535, but it's still not returning the full, and each
max length is always 200.
>
On Mar 12, 12:11 pm, "Greg D. Moore \(Strider\)"
>
<mooregr_deletet...@.greenms.comwrote:
Quote:
Originally Posted by
"phil2phil" <philtwop...@.yahoo.comwrote in message
>
Quote:
Originally Posted by
news:1173714656.510142.22770@.v33g2000cwv.googlegro ups.com...
>
Quote:
Originally Posted by
Quote:
Originally Posted by
hi,
i have a column of type ntext in the db, we're using that to allow
users to store essays they can enter. problem is when i'm running a
select on the ntext column, data seems to be getting cut off, isn't
ntext suppose to hold a lot of data, we wanted to allow them in a min
of 1500 chars, while everytime i do a
select len(max (convert(nvarchar(2000), essaytext)))
>
Quote:
Originally Posted by
Quote:
Originally Posted by
just to see the max we one had it's always 200.
>
Quote:
Originally Posted by
Quote:
Originally Posted by
Thanks.
>
Quote:
Originally Posted by
What tool are you using for this? If it's QA, you can adjust what it returns
via a setting.
>
Quote:
Originally Posted by
--
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com
"phil2phil" <philtwophil@.yahoo.comwrote in message
news:1173717649.377685.103280@.h3g2000cwc.googlegro ups.com...
Quote:
Originally Posted by
>I think i found it, the stored proc doing the actual insert into the
table, was set to @.ESSAYTEXT varchar(200) for that column, we decided
to restrict it to 2000 chars, so changing it to @.ESSAYTEXT
varchar(2000), hopefully that's fix it, the varchar(200) explains the
max(len issue as well.
>
Yeah.. if you're only inserting 200.. ;-)
(note that text fields sometimes are better handled with readtext/writetext.
But if you're moving to SQL 2005 any time I'd highly recommend varchar(max)
--
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com
Monday, March 12, 2012
Pull replication
I cannot get a pull merge replication to work.
The distributor is Win2000 running SQL 2000.
Subscribers are XP Pro running MSDE.
Agent command:
-Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
[SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode 0
-SubscriberLogin [sa] -SubscriberEncryptedPassword
[??????] -Distributor [DistSVR]
The errors:
Category:AGENT
Source: SubSVR
Number: 20084
Message: The process could not connect to Subscriber 'SubSVR'.
Category:SQLSERVER
Source: SubSVR
Number: 17
Message: SQL Server does not exist or access denied.
Thank you ver much.
This means your subscriber can't connect.
Log on to your subscriber machine and try to ping your publisher.
Also verify you can ping your subscriber using the host name SubSVR from
your subscriber. Also verify that your subscriber password is correct.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:C60CE48B-18A5-4C03-A034-5FF59E876951@.microsoft.com...
> I cannot get a pull merge replication to work.
> The distributor is Win2000 running SQL 2000.
> Subscribers are XP Pro running MSDE.
> Agent command:
> -Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
> [SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode
0
> -SubscriberLogin [sa] -SubscriberEncryptedPassword
> [??????] -Distributor [DistSVR]
> The errors:
> Category:AGENT
> Source: SubSVR
> Number: 20084
> Message: The process could not connect to Subscriber 'SubSVR'.
> Category:SQLSERVER
> Source: SubSVR
> Number: 17
> Message: SQL Server does not exist or access denied.
> Thank you ver much.
>
|||Thank you for your reply.
Subscriber PC name and SQL server name are different. It's the reason ?
Excuse me for the question: SubscriberLogin is the login to Subscriber or
Distributer ?
Thank you.
"Thang Long" wrote:
> I cannot get a pull merge replication to work.
> The distributor is Win2000 running SQL 2000.
> Subscribers are XP Pro running MSDE.
> Agent command:
> -Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
> [SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode 0
> -SubscriberLogin [sa] -SubscriberEncryptedPassword
> [??????] -Distributor [DistSVR]
> The errors:
> Category:AGENT
> Source: SubSVR
> Number: 20084
> Message: The process could not connect to Subscriber 'SubSVR'.
> Category:SQLSERVER
> Source: SubSVR
> Number: 17
> Message: SQL Server does not exist or access denied.
> Thank you ver much.
>
The distributor is Win2000 running SQL 2000.
Subscribers are XP Pro running MSDE.
Agent command:
-Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
[SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode 0
-SubscriberLogin [sa] -SubscriberEncryptedPassword
[??????] -Distributor [DistSVR]
The errors:
Category:AGENT
Source: SubSVR
Number: 20084
Message: The process could not connect to Subscriber 'SubSVR'.
Category:SQLSERVER
Source: SubSVR
Number: 17
Message: SQL Server does not exist or access denied.
Thank you ver much.
This means your subscriber can't connect.
Log on to your subscriber machine and try to ping your publisher.
Also verify you can ping your subscriber using the host name SubSVR from
your subscriber. Also verify that your subscriber password is correct.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:C60CE48B-18A5-4C03-A034-5FF59E876951@.microsoft.com...
> I cannot get a pull merge replication to work.
> The distributor is Win2000 running SQL 2000.
> Subscribers are XP Pro running MSDE.
> Agent command:
> -Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
> [SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode
0
> -SubscriberLogin [sa] -SubscriberEncryptedPassword
> [??????] -Distributor [DistSVR]
> The errors:
> Category:AGENT
> Source: SubSVR
> Number: 20084
> Message: The process could not connect to Subscriber 'SubSVR'.
> Category:SQLSERVER
> Source: SubSVR
> Number: 17
> Message: SQL Server does not exist or access denied.
> Thank you ver much.
>
|||Thank you for your reply.
Subscriber PC name and SQL server name are different. It's the reason ?
Excuse me for the question: SubscriberLogin is the login to Subscriber or
Distributer ?
Thank you.
"Thang Long" wrote:
> I cannot get a pull merge replication to work.
> The distributor is Win2000 running SQL 2000.
> Subscribers are XP Pro running MSDE.
> Agent command:
> -Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
> [SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode 0
> -SubscriberLogin [sa] -SubscriberEncryptedPassword
> [??????] -Distributor [DistSVR]
> The errors:
> Category:AGENT
> Source: SubSVR
> Number: 20084
> Message: The process could not connect to Subscriber 'SubSVR'.
> Category:SQLSERVER
> Source: SubSVR
> Number: 17
> Message: SQL Server does not exist or access denied.
> Thank you ver much.
>
Friday, March 9, 2012
Pubs and Northwind
I have MSDE 2000 installed but don't know how to connect to pubs or
northwind. Could anyone help? Running Svr 03
The sample databases do not come with the MSDE distribution. But, you can
download them from:
http://www.microsoft.com/sql/msde/downloads/default.asp
Jim
"glennTK" <glenntk@.gtkcomputer.com> wrote in message
news:%231NmrNSGFHA.3648@.TK2MSFTNGP09.phx.gbl...
>I have MSDE 2000 installed but don't know how to connect to pubs or
> northwind. Could anyone help? Running Svr 03
>
northwind. Could anyone help? Running Svr 03
The sample databases do not come with the MSDE distribution. But, you can
download them from:
http://www.microsoft.com/sql/msde/downloads/default.asp
Jim
"glennTK" <glenntk@.gtkcomputer.com> wrote in message
news:%231NmrNSGFHA.3648@.TK2MSFTNGP09.phx.gbl...
>I have MSDE 2000 installed but don't know how to connect to pubs or
> northwind. Could anyone help? Running Svr 03
>
Wednesday, March 7, 2012
Publisher is empty under Replication Monitor - Publisher.! But replication is still runnin
I have a wired situation..!
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..
You could try running sp_MSload_replication_status.
To investigate further I'd like to know if you see the publication under the
"Replication" folder and/or the "Publications" folder in the published
database.
Also, there was an issue with this prior to sp4
(http://support.microsoft.com/kb/814032) so please ensure that you've got
the latest sp.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:[vbcol=seagreen]
> Yes, I do see the publications under the Replication --> Publication
> tab. I can also confirm that the replication is working as it is
> pushing those updates to the subscriber. I am unable to run the
> sp_MSload_replication_status as it is returning the following error..
> Server: Msg 8152, Level 16, State 6, Procedure
> sp_MSload_replication_status, Line 19
> String or binary data would be truncated.
> The statement has been terminated.
> Thanks for the update. I would appreciate if you can help me figure out
> the issue...
> Thanks again..
>
> On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
|||I had finally figured out the issue... I changed the SQL Jobs
associated with the replication and when i changed back the sql job
names it appeared under my Replication monitor group window...
Query Builder wrote:[vbcol=seagreen]
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
>
> Query Builder wrote:
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..
You could try running sp_MSload_replication_status.
To investigate further I'd like to know if you see the publication under the
"Replication" folder and/or the "Publications" folder in the published
database.
Also, there was an issue with this prior to sp4
(http://support.microsoft.com/kb/814032) so please ensure that you've got
the latest sp.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:[vbcol=seagreen]
> Yes, I do see the publications under the Replication --> Publication
> tab. I can also confirm that the replication is working as it is
> pushing those updates to the subscriber. I am unable to run the
> sp_MSload_replication_status as it is returning the following error..
> Server: Msg 8152, Level 16, State 6, Procedure
> sp_MSload_replication_status, Line 19
> String or binary data would be truncated.
> The statement has been terminated.
> Thanks for the update. I would appreciate if you can help me figure out
> the issue...
> Thanks again..
>
> On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
|||I had finally figured out the issue... I changed the SQL Jobs
associated with the replication and when i changed back the sql job
names it appeared under my Replication monitor group window...
Query Builder wrote:[vbcol=seagreen]
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
>
> Query Builder wrote:
Publisher is empty under Replication Monitor - Publisher.! But replication is still runnin
I have a wired situation..!
sql jobs related to the replication. When I changed the name back to
what it was, and now I can see the replication tree under the
replication Monitor window...
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..Has anyone seen this issue? Any thoughts? Thanks in advance..
Query Builder wrote:
Quote:
Originally Posted by
I have a wired situation..!
>
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
>
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
>
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
>
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
>
All it says is (No Items)...
>
I would appreciate any help to correct this issue... Thanks in advance..
sql jobs related to the replication. When I changed the name back to
what it was, and now I can see the replication tree under the
replication Monitor window...
Query Builder wrote:
Quote:
Originally Posted by
Has anyone seen this issue? Any thoughts? Thanks in advance..
>
>
Query Builder wrote:
Quote:
Originally Posted by
I have a wired situation..!
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..
Publisher is empty under Replication Monitor - Publisher.! But replication is still runnin
I have a wired situation..!
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..You could try running sp_MSload_replication_status.
To investigate further I'd like to know if you see the publication under the
"Replication" folder and/or the "Publications" folder in the published
database.
Also, there was an issue with this prior to sp4
(http://support.microsoft.com/kb/814032) so please ensure that you've got
the latest sp.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Yes, I do see the publications under the Replication --> Publication
tab. I can also confirm that the replication is working as it is
pushing those updates to the subscriber. I am unable to run the
sp_MSload_replication_status as it is returning the following error..
Server: Msg 8152, Level 16, State 6, Procedure
sp_MSload_replication_status, Line 19
String or binary data would be truncated.
The statement has been terminated.
Thanks for the update. I would appreciate if you can help me figure out
the issue...
Thanks again..
On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> You could try running sp_MSload_replication_status.
> To investigate further I'd like to know if you see the publication under the
> "Replication" folder and/or the "Publications" folder in the published
> database.
> Also, there was an issue with this prior to sp4
> (http://support.microsoft.com/kb/814032) so please ensure that you've got
> the latest sp.
> Cheers,
> Paul Ibison SQL Server MVP,www.replicationanswers.com.|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:
> Yes, I do see the publications under the Replication --> Publication
> tab. I can also confirm that the replication is working as it is
> pushing those updates to the subscriber. I am unable to run the
> sp_MSload_replication_status as it is returning the following error..
> Server: Msg 8152, Level 16, State 6, Procedure
> sp_MSload_replication_status, Line 19
> String or binary data would be truncated.
> The statement has been terminated.
> Thanks for the update. I would appreciate if you can help me figure out
> the issue...
> Thanks again..
>
> On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> > You could try running sp_MSload_replication_status.
> > To investigate further I'd like to know if you see the publication under the
> > "Replication" folder and/or the "Publications" folder in the published
> > database.
> > Also, there was an issue with this prior to sp4
> > (http://support.microsoft.com/kb/814032) so please ensure that you've got
> > the latest sp.
> > Cheers,
> > Paul Ibison SQL Server MVP,www.replicationanswers.com.|||I had finally figured out the issue... I changed the SQL Jobs
associated with the replication and when i changed back the sql job
names it appeared under my Replication monitor group window...
Query Builder wrote:
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
>
> Query Builder wrote:
> > Yes, I do see the publications under the Replication --> Publication
> > tab. I can also confirm that the replication is working as it is
> > pushing those updates to the subscriber. I am unable to run the
> > sp_MSload_replication_status as it is returning the following error..
> >
> > Server: Msg 8152, Level 16, State 6, Procedure
> > sp_MSload_replication_status, Line 19
> > String or binary data would be truncated.
> > The statement has been terminated.
> >
> > Thanks for the update. I would appreciate if you can help me figure out
> > the issue...
> >
> > Thanks again..
> >
> >
> > On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> > > You could try running sp_MSload_replication_status.
> > > To investigate further I'd like to know if you see the publication under the
> > > "Replication" folder and/or the "Publications" folder in the published
> > > database.
> > > Also, there was an issue with this prior to sp4
> > > (http://support.microsoft.com/kb/814032) so please ensure that you've got
> > > the latest sp.
> > > Cheers,
> > > Paul Ibison SQL Server MVP,www.replicationanswers.com.
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..You could try running sp_MSload_replication_status.
To investigate further I'd like to know if you see the publication under the
"Replication" folder and/or the "Publications" folder in the published
database.
Also, there was an issue with this prior to sp4
(http://support.microsoft.com/kb/814032) so please ensure that you've got
the latest sp.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Yes, I do see the publications under the Replication --> Publication
tab. I can also confirm that the replication is working as it is
pushing those updates to the subscriber. I am unable to run the
sp_MSload_replication_status as it is returning the following error..
Server: Msg 8152, Level 16, State 6, Procedure
sp_MSload_replication_status, Line 19
String or binary data would be truncated.
The statement has been terminated.
Thanks for the update. I would appreciate if you can help me figure out
the issue...
Thanks again..
On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> You could try running sp_MSload_replication_status.
> To investigate further I'd like to know if you see the publication under the
> "Replication" folder and/or the "Publications" folder in the published
> database.
> Also, there was an issue with this prior to sp4
> (http://support.microsoft.com/kb/814032) so please ensure that you've got
> the latest sp.
> Cheers,
> Paul Ibison SQL Server MVP,www.replicationanswers.com.|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:
> Yes, I do see the publications under the Replication --> Publication
> tab. I can also confirm that the replication is working as it is
> pushing those updates to the subscriber. I am unable to run the
> sp_MSload_replication_status as it is returning the following error..
> Server: Msg 8152, Level 16, State 6, Procedure
> sp_MSload_replication_status, Line 19
> String or binary data would be truncated.
> The statement has been terminated.
> Thanks for the update. I would appreciate if you can help me figure out
> the issue...
> Thanks again..
>
> On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> > You could try running sp_MSload_replication_status.
> > To investigate further I'd like to know if you see the publication under the
> > "Replication" folder and/or the "Publications" folder in the published
> > database.
> > Also, there was an issue with this prior to sp4
> > (http://support.microsoft.com/kb/814032) so please ensure that you've got
> > the latest sp.
> > Cheers,
> > Paul Ibison SQL Server MVP,www.replicationanswers.com.|||I had finally figured out the issue... I changed the SQL Jobs
associated with the replication and when i changed back the sql job
names it appeared under my Replication monitor group window...
Query Builder wrote:
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
>
> Query Builder wrote:
> > Yes, I do see the publications under the Replication --> Publication
> > tab. I can also confirm that the replication is working as it is
> > pushing those updates to the subscriber. I am unable to run the
> > sp_MSload_replication_status as it is returning the following error..
> >
> > Server: Msg 8152, Level 16, State 6, Procedure
> > sp_MSload_replication_status, Line 19
> > String or binary data would be truncated.
> > The statement has been terminated.
> >
> > Thanks for the update. I would appreciate if you can help me figure out
> > the issue...
> >
> > Thanks again..
> >
> >
> > On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> > > You could try running sp_MSload_replication_status.
> > > To investigate further I'd like to know if you see the publication under the
> > > "Replication" folder and/or the "Publications" folder in the published
> > > database.
> > > Also, there was an issue with this prior to sp4
> > > (http://support.microsoft.com/kb/814032) so please ensure that you've got
> > > the latest sp.
> > > Cheers,
> > > Paul Ibison SQL Server MVP,www.replicationanswers.com.
Saturday, February 25, 2012
Publish A Report Services Report to SharePoint
OK... I'm running out of things to try.
I have SQL Server 2005 SP2 installed and Reporting Services Addin configured. I am trying to publish a report from BIDS to SharePoint... but a box continues to pop up asking me for credencials.
What am I doing wrong? I have reviewed all the web.config files as per an earlier post referenced, but I only see one entry in the config file for the location tag. However, I did see this tag in two config files... not certain if that is something I should be concerned with?
I'd really like to just get a sample report up on the Sharepoint Server so I can move forward.
Can anyone help?
You can always just upload the .RDL file directly into SharePoint using the SharePoint web UI. When RS integrates with SharePoint, we tell SharePoint to handle .RDL files as Report Server items, and it doesn't really matter whether they get into SharePoint through Report Designer, or through SharePoint web UI.
I'm afraid I can't help with the Report Designer issue. I'll pass this on to someone who might know about it.
|||Please check Inetpub\wwwroot\wss\VirtualDirectories\80\web.config|||What am I looking for when I go to Inetpub\wwwroot\wss\VirtualDirectories\80\web.config?
It does have one entry for location path=" _vti_bin...." as previously mentioned, a number of the web config files have this entry in it... but only once per file.
And just to clarify... I am using BIDS trying to deploy the report. The version of Visual Studio is: 8.0.50727.42.
|||I did that and surprisingly it worked... how does the report connect to the database? I did not upload or create a datasource? Well... actually I had manually created one in SharePoint in another library, but subsequently deleted it. The report still runs?|||Actually... I'll answer my own question... the first report used a custom data source... so that is why it worked. The second used a shared data source... it failed until I created the shared datasource|||I've been running into this, too. Brian Welcker's blog solved it.
http://blogs.msdn.com/bimusings/archive/2007/02/07/reporting-services-login-dialog-appears-when-deploying-to-moss-wss.aspx
Monday, February 20, 2012
ptotect against salmmers and worms
dear sir/amadam
i want ot protect my sql server what measures do i need to
take against slammers attacks or worms or viruses.as i
have running sql 2000 server.please help immediately
zahidMake sure you are running the latest service packs and security patches for
operating system and SQL Server. You could also take further steps to
strengthen your SQL Server, by locking down access. Sites like
SQLSecurity.com have pretty good information on this topic.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"zahid" <zahid_yahoo@.rediff.com> wrote in message
news:042901c3d04a$68dc9630$a401280a@.phx.gbl...
dear sir/amadam
i want ot protect my sql server what measures do i need to
take against slammers attacks or worms or viruses.as i
have running sql 2000 server.please help immediately
zahid
i want ot protect my sql server what measures do i need to
take against slammers attacks or worms or viruses.as i
have running sql 2000 server.please help immediately
zahidMake sure you are running the latest service packs and security patches for
operating system and SQL Server. You could also take further steps to
strengthen your SQL Server, by locking down access. Sites like
SQLSecurity.com have pretty good information on this topic.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"zahid" <zahid_yahoo@.rediff.com> wrote in message
news:042901c3d04a$68dc9630$a401280a@.phx.gbl...
dear sir/amadam
i want ot protect my sql server what measures do i need to
take against slammers attacks or worms or viruses.as i
have running sql 2000 server.please help immediately
zahid
PSSDIAG
Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:
> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:
> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
PSSDIAG
I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?
1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:
> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message that
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?
1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:
> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message that
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?
PSSDIAG
I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:
> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4
.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message th
at
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:
> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4
.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message th
at
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?
PSSDIAG
Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:
> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:
> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
PSSDIAG
I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:
> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message that
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:
> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message that
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?
PSSDIAG
Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:
> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:
> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
Subscribe to:
Posts (Atom)