General network error. Check your network documentation

I've a merge replication over a ISDN router between two
SQL Server 2000 databases.
The job for synchronize always run at 0:00h every day.
Sometimes i'll get this errors messages:
The process could not make a generation at
the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error
number: -2147200994)
General network error. Check your network documentation.
(Source: MAILVXE (Data source); Error number: 11)
Communication link failure
(Source: MAILVXE (Data source); Error number: 0)
The merge process could not perform retention-based meta
data cleanup in database 'WinSGS'.
(Source: Merge Replication Provider (Agent); Error
number: -2147199467)
General network error. Check your network documentation.
(Source: MAILVXE (Data source); Error number: 11)
I've already set the agent profile for a slow link
connection, can someone help qith this?
These errors are likely to be transitory. Schedule your job to run every 10
minutes or have the job loop back to step one on failuer.
See if this clears the problem.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Nuno Higgs" <nunohiggs@.hotmail.com> wrote in message
news:00a601c494ff$4c705ca0$a401280a@.phx.gbl...
> I've a merge replication over a ISDN router between two
> SQL Server 2000 databases.
> The job for synchronize always run at 0:00h every day.
> Sometimes i'll get this errors messages:
> The process could not make a generation at
> the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error
> number: -2147200994)
> ----
> General network error. Check your network documentation.
> (Source: MAILVXE (Data source); Error number: 11)
> ----
> Communication link failure
> (Source: MAILVXE (Data source); Error number: 0)
> ----
> The merge process could not perform retention-based meta
> data cleanup in database 'WinSGS'.
> (Source: Merge Replication Provider (Agent); Error
> number: -2147199467)
> ----
> General network error. Check your network documentation.
> (Source: MAILVXE (Data source); Error number: 11)
> ----
> I've already set the agent profile for a slow link
> connection, can someone help qith this?
|||General Network Error often occurs when your CPU(s) are all pinned,
and the db won't accept any more connections.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:<#Dn7BgQlEHA.1476@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
> These errors are likely to be transitory. Schedule your job to run every 10
> minutes or have the job loop back to step one on failuer.
> See if this clears the problem.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Nuno Higgs" <nunohiggs@.hotmail.com> wrote in message
> news:00a601c494ff$4c705ca0$a401280a@.phx.gbl...
|||my experience is that you get the general network error when there is a
network problem. When the server is pegged I normally get timeout error
messages.
I could be wrong here, are you quite sure about this?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Douglas Tarr" <douglas.tarr@.gmail.com> wrote in message
news:c33eac8b.0409080834.686d0d43@.posting.google.c om...
> General Network Error often occurs when your CPU(s) are all pinned,
> and the db won't accept any more connections.
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:<#Dn7BgQlEHA.1476@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
10[vbcol=seagreen]
|||I often get both. It depends on "how pegged" the CPU is. If its at
99%, there's usually enough CPU to obtain new connections. The
timeouts happen when the query itself is run. However, if it is
totally pegged (to the point where i can't even access the box), i get
a general network error.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:<eSg3
$XtlEHA.2224@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
> my experience is that you get the general network error when there is a
> network problem. When the server is pegged I normally get timeout error
> messages.
> I could be wrong here, are you quite sure about this?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Douglas Tarr" <douglas.tarr@.gmail.com> wrote in message
> news:c33eac8b.0409080834.686d0d43@.posting.google.c om...
> news:<#Dn7BgQlEHA.1476@.tk2msftngp13.phx.gbl>...
> 10

General Network Error while backing up databases

Microsoft SQL Server 2000 - 8.00.780 (Intel X86)
Mar 3 2003 10:28:28
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Client is Windows XP SP 1
I have this intermittent problem when attempting to backup a database
from another machine. Each time SQL Server communicates back the
status of the backup, I get a general network error as follows:
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
My backup script is very simple, as I am just backing up a test
database:
BACKUP DATABASE Development
TO DISK = 'Development_2003_09_04.bak'
WITH STATS = 10
It is not a query timeout, because I checked. I also varied the STATS
parameter to smaller values and the connection breaks at different
times, as follows:
Disconnect@.15 seconds:
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
Disconnect@.9 seconds:
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
5 percent backed up.
Connection Broken
Disconnect@.4 seconds:
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
2 percent backed up.
Connection Broken
The SQL Server log only lists that the backup fails, but doesn't give
a reason. The event log also listed the backup failures but didn't
give any more information than the sql log. I did notice the
following error in the server's application log:
Event Type: Error
Event Source: MSSQLServer
Event Category: (8)
Event ID: 19011
Date: 9/4/2003
Time: 3:02:29 AM
User: N/A
Computer: DAEDALUS
Description:
SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip
[TCP/IP]) : Error 10013.
followed by this warning:
Event Type: Warning
Event Source: MSSQLServer
Event Category: (8)
Event ID: 19011
Date: 9/4/2003
Time: 3:02:30 AM
User: N/A
Computer: DAEDALUS
Description:
SuperSocket info: (SpnRegister) : Error 8344.
Ideas?
Brandon Lilly
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)"jeff" <jeff@.hotmail.com> wrote in message
news:217001c37318$11a76be0$a601280a@.phx.gbl...
> Looks like a permission issue. Try adding sql server
> startup account to local NT admin, restart sql server,
> connect using sysadmin or sa from the xp client, and issue
> backup command again.
I added the account to Builtin\Administrators and also to Domain
Admins to no avail. After stopping and starting SQL Server, the
backup command would still fail if run from my client, regardless of
whether I logged in as SA, or using windows authentication (I am the
domain admin).
I am able to backup a different database remotely, but it is very
small (< 3MB) as opposed to the development database which is about 1
GB. They have the same security.
Brandon
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)|||I don't know anything more on this. Try posting your
question to microsoft.public.win2000.networking group, or
to one of winsock progrrammers group.
Good luck.
>--Original Message--
>"jeff" <jeff@.hotmail.com> wrote in message
>news:217001c37318$11a76be0$a601280a@.phx.gbl...
>> Looks like a permission issue. Try adding sql server
>> startup account to local NT admin, restart sql server,
>> connect using sysadmin or sa from the xp client, and
issue
>> backup command again.
>I added the account to Builtin\Administrators and also to
Domain
>Admins to no avail. After stopping and starting SQL
Server, the
>backup command would still fail if run from my client,
regardless of
>whether I logged in as SA, or using windows
authentication (I am the
>domain admin).
>I am able to backup a different database remotely, but it
is very
>small (< 3MB) as opposed to the development database
which is about 1
>GB. They have the same security.
>Brandon
>--
>"In the beginning the universe was created. This has
made a lot of
>people very angry, and has been widely regarded as a bad
move." -
>Douglas Noel Adams (1952-2001)
>
>.
>|||Brandon,
I am a little confused as to what your actually trying to do. You state
your backing up to a remote server but your backup command does not show
that.
> BACKUP DATABASE Development
> TO DISK = 'Development_2003_09_04.bak'
> WITH STATS = 10
Actually it doesn't show a location at all. You should probably be using
UNC to specify the device if it's remote.
--
Andrew J. Kelly
SQL Server MVP
"Brandon Lilly" <brandon.lilly@.nospam_medevolve.com> wrote in message
news:epoqWBwcDHA.2436@.TK2MSFTNGP12.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.780 (Intel X86)
> Mar 3 2003 10:28:28
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
>
> Client is Windows XP SP 1
>
> I have this intermittent problem when attempting to backup a database
> from another machine. Each time SQL Server communicates back the
> status of the backup, I get a general network error as follows:
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
>
> My backup script is very simple, as I am just backing up a test
> database:
> BACKUP DATABASE Development
> TO DISK = 'Development_2003_09_04.bak'
> WITH STATS = 10
>
> It is not a query timeout, because I checked. I also varied the STATS
> parameter to smaller values and the connection breaks at different
> times, as follows:
> Disconnect@.15 seconds:
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
>
> Disconnect@.9 seconds:
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 5 percent backed up.
> Connection Broken
>
> Disconnect@.4 seconds:
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 2 percent backed up.
> Connection Broken
>
> The SQL Server log only lists that the backup fails, but doesn't give
> a reason. The event log also listed the backup failures but didn't
> give any more information than the sql log. I did notice the
> following error in the server's application log:
>
> Event Type: Error
> Event Source: MSSQLServer
> Event Category: (8)
> Event ID: 19011
> Date: 9/4/2003
> Time: 3:02:29 AM
> User: N/A
> Computer: DAEDALUS
> Description:
> SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip
> [TCP/IP]) : Error 10013.
> followed by this warning:
> Event Type: Warning
> Event Source: MSSQLServer
> Event Category: (8)
> Event ID: 19011
> Date: 9/4/2003
> Time: 3:02:30 AM
> User: N/A
> Computer: DAEDALUS
> Description:
> SuperSocket info: (SpnRegister) : Error 8344.
> Ideas?
>
> Brandon Lilly
> --
> "In the beginning the universe was created. This has made a lot of
> people very angry, and has been widely regarded as a bad move." -
> Douglas Noel Adams (1952-2001)
>|||OK, I see now.. It looks like your using named pipes, have you tried
connecting with tcp instead and see if that makes any difference?
--
Andrew J. Kelly
SQL Server MVP
"Brandon Lilly" <brandon.lilly@.nospam_medevolve.com> wrote in message
news:u5jcPl%23cDHA.2392@.TK2MSFTNGP10.phx.gbl...
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:Oji9ot7cDHA.2564@.TK2MSFTNGP09.phx.gbl...
> > I am a little confused as to what your actually trying to do. You
> state
> > your backing up to a remote server but your backup command does not
> show
> > that.
> > Actually it doesn't show a location at all. You should probably be
> using
> > UNC to specify the device if it's remote.
> I am backing up a remote server, meaning that I am not at that machine
> running query analyzer - I am at a client machine on the domain
> executing the backup script. I don't specify a location, because I am
> just wanting it to backup to the default location
> Sorry if my post was misleading.
> Brandon
> --
> "In the beginning the universe was created. This has made a lot of
> people very angry, and has been widely regarded as a bad move." -
> Douglas Noel Adams (1952-2001)
>

General design efficiency question

My general question is whether there is anything to be gained by having 50 tables in one database versus 5 tables each in 10 databases.

I have a number of different databases running on a server (SQL Server 2k). The different databases represent different functional groups, for instance car maintenance, cab reservation/dispatch, cab accounting, limo reservation/dispatch, limo accounting, etc. There is some crossover, for instance the cab dispatch system would look to car maintenance to validate the car number entered.

A friend who happens to be IT Director at the local university suggested that the server would run more efficiently if there was only one database, rather than the roughly 12 I have now. His belief is that each separate database carries a certain amount of overhead, and combining them into one would be advantageous.

Is he all wet, or would there be gains to be made?

TIAThere would be gains. It is just a matter of whether you would notice them. I have never tested the scenario, so I have no actual numbers. Personally, I would favor the single database approach, for permissions administration reasons. A user only needs permissions on a stored procedure and not the underlying tables, IF all of the tables it accesses are in the same database. Same for views.

Now, suppose you want to restore the 10 databases back to a point in time just before your temp deleted a pile of data in "some tables". Do you want to do 10 separate restores, one?

I am sure some of the other folks here can come up with other examples, if they tried.|||He's right for the wrong reasons.

I don't think you would get a performance boost from combining the databases. You could make arguments for either increased efficiency or decreased efficiency either way.

But...from a data management standpoint it makes administrative sense to combine the databases if they reference eachother for lookup values or cross-database queries. From you limited description of the situation, I would recommend combining them.|||Thanks for your thoughts. I guess I'll look at going through the effort.|||I read the first line and fell off my barstoo...um office chair

My general question is whether there is anything to be gained by having 50 tables in one database versus 5 tables each in 10 databases.

Are you kidding? Ever hear of maintenance?

I have a number of different databases running on a server (SQL Server 2k). The different databases represent different functional groups, for instance car maintenance, cab reservation/dispatch, cab accounting, limo reservation/dispatch, limo accounting, etc. There is some crossover, for instance the cab dispatch system would look to car maintenance to validate the car number entered.

A friend who happens to be IT Director at the local university suggested that the server would run more efficiently if there was only one database, rather than the roughly 12 I have now. His belief is that each separate database carries a certain amount of overhead, and combining them into one would be advantageous.

Is he all wet, or would there be gains to be made?

TIA

I like the cut of his gib...are all the tables named differently? Also, what about the apps? Would they be hard to port?|||Putting objects in different databases will allow you more flexibility in terms of allocating data and log files. (IE if you have to use primary for select into reasons, you can more easily manage it with multiple databases). Also, depending on your backup requirements you may be able to set some databases to simple mode, some to full, only do trn backups for certain databases and the list goes on. I think it's more a management thing then a performance thing.

-kilka|||Putting objects in different databases will allow you more flexibility in terms of allocating data and log files. (IE if you have to use primary for select into reasons, you can more easily manage it with multiple databases). Also, depending on your backup requirements you may be able to set some databases to simple mode, some to full, only do trn backups for certain databases and the list goes on. I think it's more a management thing then a performance thing.

-kilka

Nope ... and thank you for playing (at least for the first statement). You can create as many segments as you desire for a single database for both data and log files ... non-clustered indexes on multiple disks, split log files, etc., etc., etc.

Not to mention that referential integrity rules can only be enforced with database, not across database.

Also, IMHO, cross database joins requires the engine to drill down thru the metadata of the other databases to access the index and page structures of the "foreign" database since SQLServer "cooks" it database space when it is allocated.

That being said, it would be interesting to see the results of an empirical test. If Paul Randal is still hanging around, maybe he can comment on this topic!|||What do you mean by "cooks" space when it's allocated?

Gap filling in a time series

Hello,

I am new to SQL Server and learning lots very quickly! I am experienced at building databases in Access and using VBA in Access and Excel.

I have a time series of 1440 records that may have some gaps in it. I need to check the time series for gaps and then fill these or reject the time series.

The criteria for accepting and rejecting is a user defined number of time steps from 1 to 10. For example, if the user sets the maximum gap as 5 time steps and a gap has 5 or less then I simply want to lineraly interpolate betwen the two timesteps bounding the gap. If the gap is 6 time steps then I will reject the timeseries.

I have searched the BOL and MSDN for SQL Server and think there must be a solution using the PredictTimeSeries in DMX, but not quite sure if I can do this. I may be better off simply passing through the time series as a recordset and processing as I would have done in Access...(I am reluctant to do this as I have of the order 100 * 5 * 365 time series and growng by 100 each day and fear it will take quite some time...)

Can anyone help me by pointing me in the right direction please?

Unless there is a way of using PredictTimeSeries on its own, I think the solution is:

Identify if a record is the a valid one or part of a gap (ie missing values).

Identify the longest gap and reject or process data on this value.

Identify if a record preceedes or succeeds a gap.

For each gap fill it using a linear interpolation.

Thanks,

Alan.

Hello,

Thank you for reading the problem above. I have moved on one step and decided that I need to store the data in a 2-d matrix with time as one dimension and space as another. I will then have to interpolate in both time and space. Also we think that we can work with a subset of just over half of the data so we are going to read the data in to an array and process it that way.

I am still interested in knowing if the DMX functions could be used to fill multiple variable length gaps in a table. Any links would be appreciated.

Thanks,

Alan.

|||

I don't think this would be a good application for the time series algorithm. You would have to create a new TS model for each series leading up to each gap and then do a prediction after creating the model. Given the data, the time series may not be able to fill the gap - since the algorithm stops predicting when it determines the predictions are unstable.

We are working on changes to the time series algorithm that may make it more suitable for such problems, but I can't share the details as of yet.

Gap filling in a time series

Hello,

I am new to SQL Server and learning lots very quickly! I am experienced at building databases in Access and using VBA in Access and Excel.

I have a time series of 1440 records that may have some gaps in it. I need to check the time series for gaps and then fill these or reject the time series.

The criteria for accepting and rejecting is a user defined number of time steps from 1 to 10. For example, if the user sets the maximum gap as 5 time steps and a gap has 5 or less then I simply want to lineraly interpolate betwen the two timesteps bounding the gap. If the gap is 6 time steps then I will reject the timeseries.

I have searched the BOL and MSDN for SQL Server and think there must be a solution using the PredictTimeSeries in DMX, but not quite sure if I can do this. I may be better off simply passing through the time series as a recordset and processing as I would have done in Access...(I am reluctant to do this as I have of the order 100 * 5 * 365 time series and growng by 100 each day and fear it will take quite some time...)

Can anyone help me by pointing me in the right direction please?

Unless there is a way of using PredictTimeSeries on its own, I think the solution is:

Identify if a record is the a valid one or part of a gap (ie missing values). Identify the longest gap and reject or process data on this value. Identify if a record preceedes or succeeds a gap. For each gap fill it using a linear interpolation.

Thanks,

Alan.

Hello,

Thank you for reading the problem above. I have moved on one step and decided that I need to store the data in a 2-d matrix with time as one dimension and space as another. I will then have to interpolate in both time and space. Also we think that we can work with a subset of just over half of the data so we are going to read the data in to an array and process it that way.

I am still interested in knowing if the DMX functions could be used to fill multiple variable length gaps in a table. Any links would be appreciated.

Thanks,

Alan.

|||

I don't think this would be a good application for the time series algorithm. You would have to create a new TS model for each series leading up to each gap and then do a prediction after creating the model. Given the data, the time series may not be able to fill the gap - since the algorithm stops predicting when it determines the predictions are unstable.

We are working on changes to the time series algorithm that may make it more suitable for such problems, but I can't share the details as of yet.

FYI> "Invalid command option D." >Resolved

Just thought I would pass this along in hopes that it can help someone.
When I had changed the startup parameters for SQL so that the databases and
log files would be in different locations. I used CAPITAL LETTERS to
designate the default location. Like -DD:\data and -LL\:logs... that
caused the server to fail to start, no matter what I did, and when I tried
to start from a dos prompt I would get the "Invalid command option D."
error. The solution was to change the registry setting under
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
and remove any capitol letters. Once I changed -DD:\data to -dD:\data,
and -lL:\logs, SQL starts up fine..Thanks for following up your own post. It prevents others from wasting their
time trying to help you after you have solved the problem, and it helps
others when you share your solution.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:%23mMqhwiwGHA.4280@.TK2MSFTNGP04.phx.gbl...
> Just thought I would pass this along in hopes that it can help someone.
> When I had changed the startup parameters for SQL so that the databases
> and log files would be in different locations. I used CAPITAL LETTERS to
> designate the default location. Like -DD:\data and -LL\:logs... that
> caused the server to fail to start, no matter what I did, and when I tried
> to start from a dos prompt I would get the "Invalid command option D."
> error. The solution was to change the registry setting under
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
> and remove any capitol letters. Once I changed -DD:\data to -dD:\data,
> and -lL:\logs, SQL starts up fine..
>

FYI> "Invalid command option D." >Resolved

Just thought I would pass this along in hopes that it can help someone.
When I had changed the startup parameters for SQL so that the databases and
log files would be in different locations. I used CAPITAL LETTERS to
designate the default location. Like -DD:\data and -LL\:logs... that
caused the server to fail to start, no matter what I did, and when I tried
to start from a dos prompt I would get the "Invalid command option D."
error. The solution was to change the registry setting under
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Parameter
s]
and remove any capitol letters. Once I changed -DD:\data to -dD:\data,
and -lL:\logs, SQL starts up fine..Thanks for following up your own post. It prevents others from wasting their
time trying to help you after you have solved the problem, and it helps
others when you share your solution.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:%23mMqhwiwGHA.4280@.TK2MSFTNGP04.phx.gbl...
> Just thought I would pass this along in hopes that it can help someone.
> When I had changed the startup parameters for SQL so that the databases
> and log files would be in different locations. I used CAPITAL LETTERS to
> designate the default location. Like -DD:\data and -LL\:logs... that
> caused the server to fail to start, no matter what I did, and when I tried
> to start from a dos prompt I would get the "Invalid command option D."
> error. The solution was to change the registry setting under
> & #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Paramet
ers]
> and remove any capitol letters. Once I changed -DD:\data to -dD:\data,
> and -lL:\logs, SQL starts up fine..
>

Fuzzy Logic Performance

Hello,
I am just wondering if someone out there has tried some Fuzzy matching on databases of large scale i.e - about 20 million contact records. Suppose I wanted to perform matching/ grouping to 10 000 incoming messages. How fast does this usually take? What is the dependence on the number of fields chosen for the match?

Any insight is greatly appreciated,

Lubomir

Pls take a look at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/FzDTSSQL05.asp

Thanks

Wenyang

|||Thank you Wenyang, great link

Lubomir

Function Column

I have a question. I am relatively new to databases, and I have
question that I am not sure of. I have a table consisting of computer
information (name, type, location, etc). One of the columns that I
have is warrantyDate which is of type DateTime and it tells when a
machine goes out of warranty.
I would like to have another column in which gives the days left of
warranty. I would like this to be updated constantly, so any day I
query the table, the proper amount of days left on the warranty of a
machine will be available. Is this possible? If so, where do I start
to look for the answers?
Thanks!You can have:
1) a computed column
2) a view that does the equivalent of 1
3) do the query on the fly
Here's the computed column:
alter table MyTable
add
DaysLeft as datediff (dd, getdate(), warrantyDate)
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
<leshanster@.gmail.com> wrote in message
news:1148824834.873869.236910@.g10g2000cwb.googlegroups.com...
I have a question. I am relatively new to databases, and I have
question that I am not sure of. I have a table consisting of computer
information (name, type, location, etc). One of the columns that I
have is warrantyDate which is of type DateTime and it tells when a
machine goes out of warranty.
I would like to have another column in which gives the days left of
warranty. I would like this to be updated constantly, so any day I
query the table, the proper amount of days left on the warranty of a
machine will be available. Is this possible? If so, where do I start
to look for the answers?
Thanks!|||Thank you so much! That was exactly what I wanted!

Function Column

I have a question. I am relatively new to databases, and I have
question that I am not sure of. I have a table consisting of computer
information (name, type, location, etc). One of the columns that I
have is warrantyDate which is of type DateTime and it tells when a
machine goes out of warranty.
I would like to have another column in which gives the days left of
warranty. I would like this to be updated constantly, so any day I
query the table, the proper amount of days left on the warranty of a
machine will be available. Is this possible? If so, where do I start
to look for the answers?
Thanks!You can have:
1) a computed column
2) a view that does the equivalent of 1
3) do the query on the fly
Here's the computed column:
alter table MyTable
add
DaysLeft as datediff (dd, getdate(), warrantyDate)
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
<leshanster@.gmail.com> wrote in message
news:1148824834.873869.236910@.g10g2000cwb.googlegroups.com...
I have a question. I am relatively new to databases, and I have
question that I am not sure of. I have a table consisting of computer
information (name, type, location, etc). One of the columns that I
have is warrantyDate which is of type DateTime and it tells when a
machine goes out of warranty.
I would like to have another column in which gives the days left of
warranty. I would like this to be updated constantly, so any day I
query the table, the proper amount of days left on the warranty of a
machine will be available. Is this possible? If so, where do I start
to look for the answers?
Thanks!|||Thank you so much! That was exactly what I wanted!

Fully Qualified Query Accross Databases

Are there any perfmonace or query optimization limitations or issues that arise when issueing a fully qualified query across multiple databases on the same Instance of SQL Server. In other words are all features of query optimization fully supported in queries that span databases on the same Instance.

The only limitations that I'm aware of are the same limitations if the queries only run against one database, i.e. the databases have to be properly optimized for performance. If one database is properly indexed and one is not the bottleneck will be the database that isn't properly indexed.
|||

That is a fact, but I am really trying to determine if there are any optimizer limitations or nuances like there are if you are using partitioning.

|||The fact that there may be partitioning really isn't relevant since partitioning is only undertaken to optimize query performance anyway by distributing data across multiple files. As I mentioned, if the databases are optimized, whether through the use of partitioning or any other strategy, then cross database queries aren't an issue. There aren't any optimizer limitations or nuances that need to be considered.

If you were performing distributed queries across multiple linked servers or across multiple resource engines, i.e. SQL Server/Oracle then there might be some things to consider but even then, the issue would probably still come down to whether the databases are properly optimized.

fulltext search not working

HI!,
Fulltext search is not working, i have two databases, fulltext search
functionality was working fine on both of them till now. but suddenly
fulltext search on one of the databases started giving out errors.
when i try to populate, rebuild was giving out errors.
when i said sp_fulltext_database 'enable' on the db it gave out the error
"An unknown full-text failure (80004005) occurred in function EnumCatalogs
on full-text catalog ''."
when i said sp_help_fulltext_catalogs , it gave out this error
Full-Text Search is not enabled for the current database. Use
sp_fulltext_database to enable Full-Text Search.
whereas the fulltext catalog functionality is working fine on the other
database.
So, please help me resolve the problem.
The sql server was down for want of space. when space was cleared and sql
server restarted the fulltext catalog problem started.
Has the fulltext catalog problem got anything to do with sql server being
down.
Any help would be greatly appreciated.
Regards,
Prudhvi
I would try to rebuild the catalog.
Also the 80004005 is a generic access denied error message.
Consult this kb article for more information
http://support.microsoft.com/default...b;en-us;295772
"Prudhvi Raju" <PrudhviRaju@.discussions.microsoft.com> wrote in message
news:311D7D42-311B-41EC-9262-93402B8867ED@.microsoft.com...
> HI!,
> Fulltext search is not working, i have two databases, fulltext search
> functionality was working fine on both of them till now. but suddenly
> fulltext search on one of the databases started giving out errors.
> when i try to populate, rebuild was giving out errors.
> when i said sp_fulltext_database 'enable' on the db it gave out the error
> "An unknown full-text failure (80004005) occurred in function EnumCatalogs
> on full-text catalog ''."
> when i said sp_help_fulltext_catalogs , it gave out this error
> Full-Text Search is not enabled for the current database. Use
> sp_fulltext_database to enable Full-Text Search.
> whereas the fulltext catalog functionality is working fine on the other
> database.
> So, please help me resolve the problem.
> The sql server was down for want of space. when space was cleared and sql
> server restarted the fulltext catalog problem started.
> Has the fulltext catalog problem got anything to do with sql server being
> down.
> Any help would be greatly appreciated.
> Regards,
> Prudhvi
>
>
>
|||Prudhvi,
Could you post the full output of -- select @.@.version -- as this is most
important information needed to troubleshoot this FTS error message.
Depending upon the version of SQL Server, you are using, you may want to
review KB article: 295772 (Q295772) "How to debug full-text search when a
7608 (0x80004005) error message occurs in SQL Server" at:
http://support.microsoft.com/default...b;EN-US;295772
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Prudhvi Raju" <PrudhviRaju@.discussions.microsoft.com> wrote in message
news:311D7D42-311B-41EC-9262-93402B8867ED@.microsoft.com...
> HI!,
> Fulltext search is not working, i have two databases, fulltext search
> functionality was working fine on both of them till now. but suddenly
> fulltext search on one of the databases started giving out errors.
> when i try to populate, rebuild was giving out errors.
> when i said sp_fulltext_database 'enable' on the db it gave out the error
> "An unknown full-text failure (80004005) occurred in function EnumCatalogs
> on full-text catalog ''."
> when i said sp_help_fulltext_catalogs , it gave out this error
> Full-Text Search is not enabled for the current database. Use
> sp_fulltext_database to enable Full-Text Search.
> whereas the fulltext catalog functionality is working fine on the other
> database.
> So, please help me resolve the problem.
> The sql server was down for want of space. when space was cleared and sql
> server restarted the fulltext catalog problem started.
> Has the fulltext catalog problem got anything to do with sql server being
> down.
> Any help would be greatly appreciated.
> Regards,
> Prudhvi
>
>
>
|||John,
output of select @.@.version
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
It doesn't allow me to even rebuild.
Can detaching and re-attaching the db solve my probs.
regards,
Prudhvi
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Prudhvi,
Thanks for providing the @.@.version info as that allows me to provide you
with a solution to error . Basically, this is a FTS component or registry
key issue, that cannot be resolved by detaching & re-attaching the database
as this problem is at the SQL Server level and not database specific.
What you must do is to "re-install" the SQL Server 2000 Full-text Search
components via your SQL Server 2000 setup CD. As the FTS components are
already installed you will need to force the removal of the FTS installed
checkmark via the removal or renaming of the following tracking registry
key. (If you're not using a named instance, remove "<Instance_Name>\".)
NOTE: be sure to be logged on to the server as either Administrator or as a
member of the server's Admin Group before deleting the below registry key
and stop both the MSSQLServer and the MSSearch services.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\<Instance_Name>\Tracking\
{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
Once you're done removed (renamed) the above tracking key, then delete the
MSSearch directory from either:
drive_letter:\Program Files\Common Files\Microsoft Shared\
or
drive_letter::\Program Files\Common Files\System\
Then using your SQL Server 2000 installation CD re-install via "Custom
Installation" the Full-Text Search component (it should be un-checked). When
this completes find and save these files: SearchSetup.log (usually under
\windows or \winnt folders) and sqlsp.log. If any problems, please post
these files.
Re-install the service pack that you may have applied to SQL Server 2000, so
that the newly re-installed MSSearch components are upgraded to SP3 levels
and then re-boot &/or restart the MSSearch and MSSQLServer services.
You may also want to consult or perform the procedures document in the
following Kb article: 827449 "How to manually reinstall the Microsoft Search
service for an instance of SQL 2000" at:
http://support.microsoft.com/default...b;EN-US;827449
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Prudhvi Manthena" <prudhvi.m@.gmail.com> wrote in message
news:uqzgeGjGFHA.1528@.TK2MSFTNGP09.phx.gbl...
> John,
> output of select @.@.version
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: )
> It doesn't allow me to even rebuild.
> Can detaching and re-attaching the db solve my probs.
> regards,
> Prudhvi
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||John,
As i told you in my first post, the FTS component is working fine on another
database in the same instance of sql server.
i was just wondering if this issue can be sorted out without re-installing
the FTS component as the server is a production database and is hosted on a
remote server.
Regards,
Prudhvi.
"John Kane" wrote:

> Prudhvi,
> Thanks for providing the @.@.version info as that allows me to provide you
> with a solution to error . Basically, this is a FTS component or registry
> key issue, that cannot be resolved by detaching & re-attaching the database
> as this problem is at the SQL Server level and not database specific.
> What you must do is to "re-install" the SQL Server 2000 Full-text Search
> components via your SQL Server 2000 setup CD. As the FTS components are
> already installed you will need to force the removal of the FTS installed
> checkmark via the removal or renaming of the following tracking registry
> key. (If you're not using a named instance, remove "<Instance_Name>\".)
> NOTE: be sure to be logged on to the server as either Administrator or as a
> member of the server's Admin Group before deleting the below registry key
> and stop both the MSSQLServer and the MSSearch services.
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\<Instance_Name>\Tracking\
> {E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
> Once you're done removed (renamed) the above tracking key, then delete the
> MSSearch directory from either:
> drive_letter:\Program Files\Common Files\Microsoft Shared\
> or
> drive_letter::\Program Files\Common Files\System\
> Then using your SQL Server 2000 installation CD re-install via "Custom
> Installation" the Full-Text Search component (it should be un-checked). When
> this completes find and save these files: SearchSetup.log (usually under
> \windows or \winnt folders) and sqlsp.log. If any problems, please post
> these files.
> Re-install the service pack that you may have applied to SQL Server 2000, so
> that the newly re-installed MSSearch components are upgraded to SP3 levels
> and then re-boot &/or restart the MSSearch and MSSQLServer services.
> You may also want to consult or perform the procedures document in the
> following Kb article: 827449 "How to manually reinstall the Microsoft Search
> service for an instance of SQL 2000" at:
> http://support.microsoft.com/default...b;EN-US;827449
> Hope that helps!
> John
>
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Prudhvi Manthena" <prudhvi.m@.gmail.com> wrote in message
> news:uqzgeGjGFHA.1528@.TK2MSFTNGP09.phx.gbl...
>
>
|||Prudhvi,
Sorry, I missed that info in the first post... Usually, this error (An
unknown full-text failure (80004005)...) indicates a problem with the
MSSearch service components or registry key &/or values at the server level
and generally not specific to one database on a server. However, it may be
that specific FT Catalog registry keys/values maybe mis-configured or
missing that are linked to one database. However, you would need to open a
support case with Microsoft PSS SQL Server support as they have methods for
doing extended debugging of this issue to identify the exact cause of this
issue for you. If you cannot re-install the FTS components per the KB
article or the below method, then I'd recommend that you open a support case
with Microsoft SQL Server support.
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Prudhvi Raju" <PrudhviRaju@.discussions.microsoft.com> wrote in message
news:11DA5ABC-19AD-460C-84D1-94E3646BC34D@.microsoft.com...
> John,
> As i told you in my first post, the FTS component is working fine on
another
> database in the same instance of sql server.
> i was just wondering if this issue can be sorted out without re-installing
> the FTS component as the server is a production database and is hosted on
a[vbcol=seagreen]
> remote server.
> Regards,
> Prudhvi.
>
> "John Kane" wrote:
registry[vbcol=seagreen]
database[vbcol=seagreen]
installed[vbcol=seagreen]
as a[vbcol=seagreen]
key[vbcol=seagreen]
the[vbcol=seagreen]
When[vbcol=seagreen]
2000, so[vbcol=seagreen]
levels[vbcol=seagreen]
Search[vbcol=seagreen]