I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev
"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
Showing posts with label across. Show all posts
Showing posts with label across. Show all posts
Friday, March 23, 2012
Frustrated with two clients that can't connect...
I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
Frustrated with two clients that can't connect...
I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
FrontPage/SharePoint Designer Search and Replace Fills Transaction
When we run a search and replace across all pages in one our web site (104
pages), my transaction log on the SQL Server grows by about 200 MB of space!
This has caused major system headaches - the transaction log fills, causes
IIS to fail, causing my clients using FP / SP Designer not to be able to save
the files they have opened / edited.
That database is 400MB in size while the Transaction Log is now over 6GB.
and the minimum Log is now 6GB too. We can't keep having this log grow
exponential like this.
Also - In the event log, I see that there a couple of 'webparts' that are
failing on the global search and replace: WSS 2.0 Error: Failing in loading
assemble Customer.WebParts, Version=1.0.2.4.
We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
using the latest versions of FrontPage and SharePoint Designer.
Thoughts?
After posting this, I started to search the WSS / Sharepoint forums (instead
of just SQL Server) and see that this is a common issue and found a variety
of ways to correct this.
Iza
"iZa" wrote:
> When we run a search and replace across all pages in one our web site (104
> pages), my transaction log on the SQL Server grows by about 200 MB of space!
> This has caused major system headaches - the transaction log fills, causes
> IIS to fail, causing my clients using FP / SP Designer not to be able to save
> the files they have opened / edited.
> That database is 400MB in size while the Transaction Log is now over 6GB.
> and the minimum Log is now 6GB too. We can't keep having this log grow
> exponential like this.
> Also - In the event log, I see that there a couple of 'webparts' that are
> failing on the global search and replace: WSS 2.0 Error: Failing in loading
> assemble Customer.WebParts, Version=1.0.2.4.
> We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
> using the latest versions of FrontPage and SharePoint Designer.
> Thoughts?
pages), my transaction log on the SQL Server grows by about 200 MB of space!
This has caused major system headaches - the transaction log fills, causes
IIS to fail, causing my clients using FP / SP Designer not to be able to save
the files they have opened / edited.
That database is 400MB in size while the Transaction Log is now over 6GB.
and the minimum Log is now 6GB too. We can't keep having this log grow
exponential like this.
Also - In the event log, I see that there a couple of 'webparts' that are
failing on the global search and replace: WSS 2.0 Error: Failing in loading
assemble Customer.WebParts, Version=1.0.2.4.
We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
using the latest versions of FrontPage and SharePoint Designer.
Thoughts?
After posting this, I started to search the WSS / Sharepoint forums (instead
of just SQL Server) and see that this is a common issue and found a variety
of ways to correct this.
Iza
"iZa" wrote:
> When we run a search and replace across all pages in one our web site (104
> pages), my transaction log on the SQL Server grows by about 200 MB of space!
> This has caused major system headaches - the transaction log fills, causes
> IIS to fail, causing my clients using FP / SP Designer not to be able to save
> the files they have opened / edited.
> That database is 400MB in size while the Transaction Log is now over 6GB.
> and the minimum Log is now 6GB too. We can't keep having this log grow
> exponential like this.
> Also - In the event log, I see that there a couple of 'webparts' that are
> failing on the global search and replace: WSS 2.0 Error: Failing in loading
> assemble Customer.WebParts, Version=1.0.2.4.
> We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
> using the latest versions of FrontPage and SharePoint Designer.
> Thoughts?
FrontPage/SharePoint Designer Search and Replace Fills Transaction
When we run a search and replace across all pages in one our web site (104
pages), my transaction log on the SQL Server grows by about 200 MB of space!
This has caused major system headaches - the transaction log fills, causes
IIS to fail, causing my clients using FP / SP Designer not to be able to save
the files they have opened / edited.
That database is 400MB in size while the Transaction Log is now over 6GB.
and the minimum Log is now 6GB too. We can't keep having this log grow
exponential like this.
Also - In the event log, I see that there a couple of 'webparts' that are
failing on the global search and replace: WSS 2.0 Error: Failing in loading
assemble Customer.WebParts, Version=1.0.2.4.
We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
using the latest versions of FrontPage and SharePoint Designer.
Thoughts?After posting this, I started to search the WSS / Sharepoint forums (instead
of just SQL Server) and see that this is a common issue and found a variety
of ways to correct this.
Iza
"iZa" wrote:
> When we run a search and replace across all pages in one our web site (104
> pages), my transaction log on the SQL Server grows by about 200 MB of space!
> This has caused major system headaches - the transaction log fills, causes
> IIS to fail, causing my clients using FP / SP Designer not to be able to save
> the files they have opened / edited.
> That database is 400MB in size while the Transaction Log is now over 6GB.
> and the minimum Log is now 6GB too. We can't keep having this log grow
> exponential like this.
> Also - In the event log, I see that there a couple of 'webparts' that are
> failing on the global search and replace: WSS 2.0 Error: Failing in loading
> assemble Customer.WebParts, Version=1.0.2.4.
> We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
> using the latest versions of FrontPage and SharePoint Designer.
> Thoughts?sql
pages), my transaction log on the SQL Server grows by about 200 MB of space!
This has caused major system headaches - the transaction log fills, causes
IIS to fail, causing my clients using FP / SP Designer not to be able to save
the files they have opened / edited.
That database is 400MB in size while the Transaction Log is now over 6GB.
and the minimum Log is now 6GB too. We can't keep having this log grow
exponential like this.
Also - In the event log, I see that there a couple of 'webparts' that are
failing on the global search and replace: WSS 2.0 Error: Failing in loading
assemble Customer.WebParts, Version=1.0.2.4.
We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
using the latest versions of FrontPage and SharePoint Designer.
Thoughts?After posting this, I started to search the WSS / Sharepoint forums (instead
of just SQL Server) and see that this is a common issue and found a variety
of ways to correct this.
Iza
"iZa" wrote:
> When we run a search and replace across all pages in one our web site (104
> pages), my transaction log on the SQL Server grows by about 200 MB of space!
> This has caused major system headaches - the transaction log fills, causes
> IIS to fail, causing my clients using FP / SP Designer not to be able to save
> the files they have opened / edited.
> That database is 400MB in size while the Transaction Log is now over 6GB.
> and the minimum Log is now 6GB too. We can't keep having this log grow
> exponential like this.
> Also - In the event log, I see that there a couple of 'webparts' that are
> failing on the global search and replace: WSS 2.0 Error: Failing in loading
> assemble Customer.WebParts, Version=1.0.2.4.
> We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
> using the latest versions of FrontPage and SharePoint Designer.
> Thoughts?sql
FrontPage/SharePoint Designer Search and Replace Fills Transaction
When we run a search and replace across all pages in one our web site (104
pages), my transaction log on the SQL Server grows by about 200 MB of space!
This has caused major system headaches - the transaction log fills, causes
IIS to fail, causing my clients using FP / SP Designer not to be able to sav
e
the files they have opened / edited.
That database is 400MB in size while the Transaction Log is now over 6GB.
and the minimum Log is now 6GB too. We can't keep having this log grow
exponential like this.
Also - In the event log, I see that there a couple of 'webparts' that are
failing on the global search and replace: WSS 2.0 Error: Failing in loading
assemble Customer.WebParts, Version=1.0.2.4.
We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
using the latest versions of FrontPage and SharePoint Designer.
Thoughts?After posting this, I started to search the WSS / Sharepoint forums (instead
of just SQL Server) and see that this is a common issue and found a variety
of ways to correct this.
Iza
"iZa" wrote:
> When we run a search and replace across all pages in one our web site (104
> pages), my transaction log on the SQL Server grows by about 200 MB of spac
e!
> This has caused major system headaches - the transaction log fills, causes
> IIS to fail, causing my clients using FP / SP Designer not to be able to s
ave
> the files they have opened / edited.
> That database is 400MB in size while the Transaction Log is now over 6GB.
> and the minimum Log is now 6GB too. We can't keep having this log grow
> exponential like this.
> Also - In the event log, I see that there a couple of 'webparts' that are
> failing on the global search and replace: WSS 2.0 Error: Failing in loadin
g
> assemble Customer.WebParts, Version=1.0.2.4.
> We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
> using the latest versions of FrontPage and SharePoint Designer.
> Thoughts?
pages), my transaction log on the SQL Server grows by about 200 MB of space!
This has caused major system headaches - the transaction log fills, causes
IIS to fail, causing my clients using FP / SP Designer not to be able to sav
e
the files they have opened / edited.
That database is 400MB in size while the Transaction Log is now over 6GB.
and the minimum Log is now 6GB too. We can't keep having this log grow
exponential like this.
Also - In the event log, I see that there a couple of 'webparts' that are
failing on the global search and replace: WSS 2.0 Error: Failing in loading
assemble Customer.WebParts, Version=1.0.2.4.
We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
using the latest versions of FrontPage and SharePoint Designer.
Thoughts?After posting this, I started to search the WSS / Sharepoint forums (instead
of just SQL Server) and see that this is a common issue and found a variety
of ways to correct this.
Iza
"iZa" wrote:
> When we run a search and replace across all pages in one our web site (104
> pages), my transaction log on the SQL Server grows by about 200 MB of spac
e!
> This has caused major system headaches - the transaction log fills, causes
> IIS to fail, causing my clients using FP / SP Designer not to be able to s
ave
> the files they have opened / edited.
> That database is 400MB in size while the Transaction Log is now over 6GB.
> and the minimum Log is now 6GB too. We can't keep having this log grow
> exponential like this.
> Also - In the event log, I see that there a couple of 'webparts' that are
> failing on the global search and replace: WSS 2.0 Error: Failing in loadin
g
> assemble Customer.WebParts, Version=1.0.2.4.
> We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
> using the latest versions of FrontPage and SharePoint Designer.
> Thoughts?
Sunday, February 26, 2012
Free Text Search across multiple tables
Anyone have any recommendations on how to bring together a search across multiple tables? Like I'd love to do a search where i searched for the product name, company name or tag all in one query (though all are in separate tables)... is that possible? Individually, it's easy, but combined it's very hard.You can join the tables and use like, but I should probably first take a look at the Free text search engine (but it depends on how the table looks like, how the search will be formed in the future, how much data the table has etc), take a look at the following site:http://www.databasejournal.com/features/mssql/article.php/3441981|||
actually, that's just it... i'm using the full text search engine, which generates catalogs per table. I'm not sure how to bring the table results together. so, for example:
Declare @.search nvarchar(100)select @.search ='apple'SELECT TOP 5 * FROM brands INNER JOIN (SELECT * from freetexttable (Brands,*,@.Search) ORDER BY [RANK] DESC) AS search ON brands.brandid = search.[KEY]SELECT TOP 5 * FROM products INNER JOIN (SELECT * from freetexttable (products,*,@.Search) ORDER BY [RANK] DESC) AS search ON products.productid = search.[KEY]SELECT TOP 5 * FROM companies INNER JOIN (SELECT * from freetexttable (companies,*,@.Search) ORDER BY [RANK] DESC) AS search ON companies.companyid = search.[KEY]
How do i bring these tables together and order them according to the closest match across the tables?|||
Hey,
Did you have any luck with this? I'm using SQL 2005, and I've done a bit of testing, but haven't got the expected results!
Thanks
Subscribe to:
Posts (Atom)