Showing posts with label docs. Show all posts
Showing posts with label docs. Show all posts

Sunday, February 19, 2012

Documentation Tools for SSB?

Does anyone know if there are automated documentation tools around that will produce docs for Service Broker objects?

Thanks,

AndrewM

There is no tool for documentation, but there is one for retrieving a more formal specification (Called service listing). It's called Service Listings Manager and Remus has contributed that to the code gallery. You might want to use that as a starting point to build a doc generator.

Friday, February 17, 2012

docs for 2003 enterprise cluster

Im looking for documentation that explains how to install SQL 2000
Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
running an install of Sage MMS 3.5 for SQL 2000 Server.
http://www.sage-eshop.com
Installing SQL2000 in a failover cluster is documented pretty well in SQL2000
Books Online under "Advanced Installation Options" and "Failover Clustering"
The content is not specific to Win2K3 or SAN. But as far as installing
SQL2000 itself is concerned whether it's Win2000 or Win2K3 or a shared disk
that is not presented from a SAN shouldn't matter. Configuring the cluster
itself at the OS level is different though. If you need to configure msdtc
yourself, read this KB article http://support.microsoft.com/?kbid=301600.
Linchi
"Scott" wrote:

> Im looking for documentation that explains how to install SQL 2000
> Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
> running an install of Sage MMS 3.5 for SQL 2000 Server.
> http://www.sage-eshop.com
>
>

docs for 2003 enterprise cluster

Im looking for documentation that explains how to install SQL 2000
Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
running an install of Sage MMS 3.5 for SQL 2000 Server.
---
http://www.sage-eshop.comInstalling SQL2000 in a failover cluster is documented pretty well in SQL200
0
Books Online under "Advanced Installation Options" and "Failover Clustering"
The content is not specific to Win2K3 or SAN. But as far as installing
SQL2000 itself is concerned whether it's Win2000 or Win2K3 or a shared disk
that is not presented from a SAN shouldn't matter. Configuring the cluster
itself at the OS level is different though. If you need to configure msdtc
yourself, read this KB article http://support.microsoft.com/?kbid=301600.
Linchi
"Scott" wrote:

> Im looking for documentation that explains how to install SQL 2000
> Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
> running an install of Sage MMS 3.5 for SQL 2000 Server.
> ---
> http://www.sage-eshop.com
>
>

docs for 2003 enterprise cluster

Im looking for documentation that explains how to install SQL 2000
Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
running an install of Sage MMS 3.5 for SQL 2000 Server.
---
http://www.sage-eshop.comInstalling SQL2000 in a failover cluster is documented pretty well in SQL2000
Books Online under "Advanced Installation Options" and "Failover Clustering"
The content is not specific to Win2K3 or SAN. But as far as installing
SQL2000 itself is concerned whether it's Win2000 or Win2K3 or a shared disk
that is not presented from a SAN shouldn't matter. Configuring the cluster
itself at the OS level is different though. If you need to configure msdtc
yourself, read this KB article http://support.microsoft.com/?kbid=301600.
Linchi
"Scott" wrote:
> Im looking for documentation that explains how to install SQL 2000
> Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
> running an install of Sage MMS 3.5 for SQL 2000 Server.
> ---
> http://www.sage-eshop.com
>
>

Tuesday, February 14, 2012

Docs files in FTDATA

Hi,
I have a SQL Server 2000 cluster, sp 3 in w2k.
When the catalog is reindexed, some documents appears in FTDATA folder. If I
delete the documents, then they reappear in the next indexing.
I'm thinking about to schedule a batch that cleanup this folder, because I
have the FTDATA in the Quorum drive, with no much free space.
Why this is? How can I avoid it?
qwalgrande
What do you mean by documents? Can you open these documents in Word or
notepad?
These documents will be extracted by the indexing process, but on my non
clustered system they are cleaned up.
Some files will remain which are used my mssearch to track where it is in
the indexing process. You shouldn't touch these files.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"qwalgrande" <qwalgrande*nospam*@.yahoo.es> wrote in message
news:6131ACD4-A717-48D6-AC63-4F2FE43B7CA5@.microsoft.com...
> Hi,
> I have a SQL Server 2000 cluster, sp 3 in w2k.
> When the catalog is reindexed, some documents appears in FTDATA folder. If
I
> delete the documents, then they reappear in the next indexing.
> I'm thinking about to schedule a batch that cleanup this folder, because I
> have the FTDATA in the Quorum drive, with no much free space.
> Why this is? How can I avoid it?
> --
> qwalgrande
|||one more point - exactly which subdirectory of ftdata do these files exist
in.
It could be possible that they are eithre configuration files or the actual
index/catalog files themselves.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%238ZUxJKoEHA.2340@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> What do you mean by documents? Can you open these documents in Word or
> notepad?
> These documents will be extracted by the indexing process, but on my non
> clustered system they are cleaned up.
> Some files will remain which are used my mssearch to track where it is in
> the indexing process. You shouldn't touch these files.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "qwalgrande" <qwalgrande*nospam*@.yahoo.es> wrote in message
> news:6131ACD4-A717-48D6-AC63-4F2FE43B7CA5@.microsoft.com...
If[vbcol=seagreen]
> I
I
>
|||Hello, Hilary.
I will try to explain it better. These "documents" are the documents that I
had inserted in my indexed image column. In the population, the documents
"pass" for the folder and quickly disappear, but a few documents stay in the
folder and don't cleaned up.
The directory is FTDATA, no subdirectories. I have tried in a nonclustered
server too, whit the same result. Could you help me?
Thanks in advanced.
"Hilary Cotter" wrote:

> one more point - exactly which subdirectory of ftdata do these files exist
> in.
> It could be possible that they are eithre configuration files or the actual
> index/catalog files themselves.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%238ZUxJKoEHA.2340@.TK2MSFTNGP11.phx.gbl...
> If
> I
>
>
|||qwalgrande,
The behavior you are seeing is by design, except for the document files not
being deleted, I *believe* has be acknowledged as a bug by Microsoft and may
(or may not) be fixed in the next Service Pack (SP4) for SQL Sever 2000.
This issue was discovered about a year ago on this newsgroup and the
non-delete of the files acknowledged as a bug by Microsoft, but alas we were
not provided with an actual bug number for tracking purposes. Hopefully,
this will be addressed in the next Service Pack (SP4) for SQL Sever 2000.
Regards,
John
"qwalgrande" <qwalgrande*nospam*@.yahoo.es> wrote in message
news:054B35B9-15F1-4BDF-A193-D03638EA71CC@.microsoft.com...
> Hello, Hilary.
> I will try to explain it better. These "documents" are the documents that
I
> had inserted in my indexed image column. In the population, the documents
> "pass" for the folder and quickly disappear, but a few documents stay in
the[vbcol=seagreen]
> folder and don't cleaned up.
> The directory is FTDATA, no subdirectories. I have tried in a nonclustered
> server too, whit the same result. Could you help me?
> Thanks in advanced.
> "Hilary Cotter" wrote:
exist[vbcol=seagreen]
actual[vbcol=seagreen]
non[vbcol=seagreen]
in[vbcol=seagreen]
folder.[vbcol=seagreen]
because[vbcol=seagreen]