Welcome to SQL
Try doing the following at a time when the database has
few or no users.
Right Click on the Database and select Properties
Select Options Tab
Under Recovery - Model if its not set to simple change it
to simple.
Press OK
Right Click the database and select All Tasks -> Shrink
Database
Select the check box 'Move Pages to beginning...'
Press ok
Go make yourself a drink whilst your waiting ;)
And after if finishes change your 'Recovery - Model' back
to what it was prior to your change.
Peter
>--Original Message--
>Please excues my ignorance, but I am in no way a SQL guy;
so here goes:
>I have an accounting package that uses SQL 2000. SQL is
creating a backup
>file that is getting HUGE (about 2 GB)
>The actual data is around a few hundred MB.
>Is there a way to reduce the size of the backup file by:
>Compacting?
>Performaing a backup (that SQL knows about)?
>Is there a way to move that file?
>Can any of this be done on-line?
>Thanks for any help.
>Regards;
>PB
>
>.
>
Please forgive my ignorance, but:
Where is the database? It appears that the app that uses SQL is pointing to
a file share on another server. The backup file (BAK) is local, and it is
killing me. As I said, it is 2 GB and growing.
If it is the BAK file that is huge; will that fix my problem? The database
itself is only 132 MB.
TIA;
PB
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:44e901c47fb8$3fa1b9d0$a401280a@.phx.gbl...[vbcol=seagreen]
> Welcome to SQL
> Try doing the following at a time when the database has
> few or no users.
> Right Click on the Database and select Properties
> Select Options Tab
> Under Recovery - Model if its not set to simple change it
> to simple.
> Press OK
> Right Click the database and select All Tasks -> Shrink
> Database
> Select the check box 'Move Pages to beginning...'
> Press ok
> Go make yourself a drink whilst your waiting ;)
> And after if finishes change your 'Recovery - Model' back
> to what it was prior to your change.
> Peter
>
>
> so here goes:
> creating a backup
|||When releasing space SQL Server doesn't actually free
disk space, its thinking is if its needed it before, it
needs it now, so if you say delete half your database you
will see the same disk space.
The problem though is probably to do with your log file
that will grows a heck of a lot.
To work out where your files are click onto your database
then at the top menu selecy view 'Something (I'm away
from SQL) pad'
It will give you the location and size of your data files
and log files.
These files can be anywhere on your Network.
As for your backup files (.BAK) its considered good
practice to store them on a different server than the one
that SQL is on.
And yes, performing the steps will solve the problem as
the steps will release the unused disk space and so the
backups will not be fooled into thinking there is more to
the files than there actually is.
Anyway its 22:15 here and I am off to do something else.
Good luck
Peter
Peter
>--Original Message--
>Please forgive my ignorance, but:
>Where is the database? It appears that the app that uses
SQL is pointing to
>a file share on another server. The backup file (BAK) is
local, and it is
>killing me. As I said, it is 2 GB and growing.
>If it is the BAK file that is huge; will that fix my
problem? The database
>itself is only 132 MB.
>TIA;
>PB
>
>"Peter The Spate" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:44e901c47fb8$3fa1b9d0$a401280a@.phx.gbl...
it[vbcol=seagreen]
back[vbcol=seagreen]
guy;[vbcol=seagreen]
is[vbcol=seagreen]
by:
>
>.
>
Showing posts with label users. Show all posts
Showing posts with label users. Show all posts
Friday, March 30, 2012
New to Replication
I have a SQL 2000 database used in a data entry / transactional mode. We
have few users, but they do occassionally run reports which are server
intensive. It is a small business. We would like to begin using the data in
the database on the website. I'm wondering if I should replicate the DB on
the same server. Does that really provide any performance protection for the
data entry folks? We don't think the traffic on the Internet will be intense
to begin with because it will only be for members. Does a snapshot
replication make sense (we only need a refresh each night) or should I just
let the web hit the data entry db? Thanks
Hi,
I understand that some of your users occasionally ran reports on your
server. The operations impacted your server performance. You want to know
if you can replicate the DB on the same server to improve the performance.
If I have misunderstood, please let me know.
Generally producing report is CPU, memory and I/O intensive, so I recommend
that you replicate your database to a different server (dedicated for
report server) and have your web application use this report server for
producing report. Since reports are for history data, snapshot replication
is enough.
For implementing replication, please refer to:
Implementing Replication (Enterprise Manager)
http://msdn2.microsoft.com/en-us/library/aa216618(sql.80).aspx
Implementing Master-Slave Snapshot Replication Using SQL Server
http://msdn2.microsoft.com/en-us/library/ms998561.aspx
Planning for Snapshot Replication
http://msdn2.microsoft.com/en-us/library/aa237481(SQL.80).aspx
If you have any other questions or concerns, please let me know. Have a
nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||That answers my question. Thanks Charles!
"Charles Wang[MSFT]" wrote:
> Hi,
> I understand that some of your users occasionally ran reports on your
> server. The operations impacted your server performance. You want to know
> if you can replicate the DB on the same server to improve the performance.
> If I have misunderstood, please let me know.
> Generally producing report is CPU, memory and I/O intensive, so I recommend
> that you replicate your database to a different server (dedicated for
> report server) and have your web application use this report server for
> producing report. Since reports are for history data, snapshot replication
> is enough.
> For implementing replication, please refer to:
> Implementing Replication (Enterprise Manager)
> http://msdn2.microsoft.com/en-us/library/aa216618(sql.80).aspx
> Implementing Master-Slave Snapshot Replication Using SQL Server
> http://msdn2.microsoft.com/en-us/library/ms998561.aspx
> Planning for Snapshot Replication
> http://msdn2.microsoft.com/en-us/library/aa237481(SQL.80).aspx
> If you have any other questions or concerns, please let me know. Have a
> nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>
>
>
>
>
sql
have few users, but they do occassionally run reports which are server
intensive. It is a small business. We would like to begin using the data in
the database on the website. I'm wondering if I should replicate the DB on
the same server. Does that really provide any performance protection for the
data entry folks? We don't think the traffic on the Internet will be intense
to begin with because it will only be for members. Does a snapshot
replication make sense (we only need a refresh each night) or should I just
let the web hit the data entry db? Thanks
Hi,
I understand that some of your users occasionally ran reports on your
server. The operations impacted your server performance. You want to know
if you can replicate the DB on the same server to improve the performance.
If I have misunderstood, please let me know.
Generally producing report is CPU, memory and I/O intensive, so I recommend
that you replicate your database to a different server (dedicated for
report server) and have your web application use this report server for
producing report. Since reports are for history data, snapshot replication
is enough.
For implementing replication, please refer to:
Implementing Replication (Enterprise Manager)
http://msdn2.microsoft.com/en-us/library/aa216618(sql.80).aspx
Implementing Master-Slave Snapshot Replication Using SQL Server
http://msdn2.microsoft.com/en-us/library/ms998561.aspx
Planning for Snapshot Replication
http://msdn2.microsoft.com/en-us/library/aa237481(SQL.80).aspx
If you have any other questions or concerns, please let me know. Have a
nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||That answers my question. Thanks Charles!
"Charles Wang[MSFT]" wrote:
> Hi,
> I understand that some of your users occasionally ran reports on your
> server. The operations impacted your server performance. You want to know
> if you can replicate the DB on the same server to improve the performance.
> If I have misunderstood, please let me know.
> Generally producing report is CPU, memory and I/O intensive, so I recommend
> that you replicate your database to a different server (dedicated for
> report server) and have your web application use this report server for
> producing report. Since reports are for history data, snapshot replication
> is enough.
> For implementing replication, please refer to:
> Implementing Replication (Enterprise Manager)
> http://msdn2.microsoft.com/en-us/library/aa216618(sql.80).aspx
> Implementing Master-Slave Snapshot Replication Using SQL Server
> http://msdn2.microsoft.com/en-us/library/ms998561.aspx
> Planning for Snapshot Replication
> http://msdn2.microsoft.com/en-us/library/aa237481(SQL.80).aspx
> If you have any other questions or concerns, please let me know. Have a
> nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>
>
>
>
>
sql
Friday, March 23, 2012
new SQL Server 2005 install giving login error... HELP!
I completely uninstalled 2000 and did a clean install of 2005. I restored m
y
database and users and all seems fine. I am set up with mixed authenticatio
n
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40Hi
This sounds like you have orphaned users
121120120" target="_blank">http://support.microsoft.com/defaul...r />
121120120
John
"SharinDenver" wrote:
> I completely uninstalled 2000 and did a clean install of 2005. I restored
my
> database and users and all seems fine. I am set up with mixed authenticat
ion
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This sounds like you have orphaned users
> 20121120120" target="_blank">http://support.microsoft.com/defaul.../>
20121120120
> John
> "SharinDenver" wrote:
>
y
database and users and all seems fine. I am set up with mixed authenticatio
n
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40Hi
This sounds like you have orphaned users
121120120" target="_blank">http://support.microsoft.com/defaul...r />
121120120
John
"SharinDenver" wrote:
> I completely uninstalled 2000 and did a clean install of 2005. I restored
my
> database and users and all seems fine. I am set up with mixed authenticat
ion
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This sounds like you have orphaned users
> 20121120120" target="_blank">http://support.microsoft.com/defaul.../>
20121120120
> John
> "SharinDenver" wrote:
>
new SQL Server 2005 install giving login error... HELP!
I completely uninstalled 2000 and did a clean install of 2005. I restored my
database and users and all seems fine. I am set up with mixed authentication
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40
Hi
This sounds like you have orphaned users
http://support.microsoft.com/default...21120121120120
John
"SharinDenver" wrote:
> I completely uninstalled 2000 and did a clean install of 2005. I restored my
> database and users and all seems fine. I am set up with mixed authentication
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>
|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This sounds like you have orphaned users
> http://support.microsoft.com/default...21120121120120
> John
> "SharinDenver" wrote:
database and users and all seems fine. I am set up with mixed authentication
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40
Hi
This sounds like you have orphaned users
http://support.microsoft.com/default...21120121120120
John
"SharinDenver" wrote:
> I completely uninstalled 2000 and did a clean install of 2005. I restored my
> database and users and all seems fine. I am set up with mixed authentication
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>
|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This sounds like you have orphaned users
> http://support.microsoft.com/default...21120121120120
> John
> "SharinDenver" wrote:
new SQL Server 2005 install giving login error... HELP!
I completely uninstalled 2000 and did a clean install of 2005. I restored my
database and users and all seems fine. I am set up with mixed authentication
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40Hi
This sounds like you have orphaned users
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546#XSLTH3182121121120121120120
John
"SharinDenver" wrote:
> I completely uninstalled 2000 and did a clean install of 2005. I restored my
> database and users and all seems fine. I am set up with mixed authentication
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
> Hi
> This sounds like you have orphaned users
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546#XSLTH3182121121120121120120
> John
> "SharinDenver" wrote:
> > I completely uninstalled 2000 and did a clean install of 2005. I restored my
> > database and users and all seems fine. I am set up with mixed authentication
> > (windows and sql server). My username is in security/logins as well as in
> > database/security/users with connect and select permissions.
> >
> > I am getting the following error when trying to submit my asp page:
> >
> >
> > Microsoft OLE DB Provider for SQL Server error '80004005'
> >
> > Cannot open database "dbName" requested by the login. The login failed.
> >
> > /AddressSearch/SearchResults.asp, line 40
> >
database and users and all seems fine. I am set up with mixed authentication
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40Hi
This sounds like you have orphaned users
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546#XSLTH3182121121120121120120
John
"SharinDenver" wrote:
> I completely uninstalled 2000 and did a clean install of 2005. I restored my
> database and users and all seems fine. I am set up with mixed authentication
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
> Hi
> This sounds like you have orphaned users
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546#XSLTH3182121121120121120120
> John
> "SharinDenver" wrote:
> > I completely uninstalled 2000 and did a clean install of 2005. I restored my
> > database and users and all seems fine. I am set up with mixed authentication
> > (windows and sql server). My username is in security/logins as well as in
> > database/security/users with connect and select permissions.
> >
> > I am getting the following error when trying to submit my asp page:
> >
> >
> > Microsoft OLE DB Provider for SQL Server error '80004005'
> >
> > Cannot open database "dbName" requested by the login. The login failed.
> >
> > /AddressSearch/SearchResults.asp, line 40
> >
Wednesday, March 21, 2012
New Server...
We are running an Enterprise CRM (SalesLogix) on SQL2K
SP3a.
The server we have is a Quad Xeon 500MHz, 4GB RAM.
We currently have 192 users that connect at any given
time, but usually no more than 70-80 at a time.
The perfomance has gradually been getting worse the last
few months and the usage has increased by about 30% since
then as well.
Would upgrading to a quad 1.5GHz Xeon with 4GB RAM
increase performance quite a bit?"Don" <donolwert@.hotmail.com> wrote in message
news:000b01c35c34$ee45c330$a401280a@.phx.gbl...
> We are running an Enterprise CRM (SalesLogix) on SQL2K
> SP3a.
> The server we have is a Quad Xeon 500MHz, 4GB RAM.
> We currently have 192 users that connect at any given
> time, but usually no more than 70-80 at a time.
> The perfomance has gradually been getting worse the last
> few months and the usage has increased by about 30% since
> then as well.
It may be time to rebuild the indices and update the statistics... In
addition, you may want to consider running the Index Tuning Wizard to
determine if performance would benefit by a few carefully placed index's.
> Would upgrading to a quad 1.5GHz Xeon with 4GB RAM
> increase performance quite a bit?
Where is the bottleneck? Is it processor? Is it disk? Some performance
monitor statistics would help answer those questions. I'd start with my
previous suggestions...
Steve|||> It is Processor performance. I haven't noticed any
> bottlenecks and there is 30GB of free space left. The DB
> is 9GB.
Free disk space doesn't indicate that processor performance is poor.
If there are no bottlenecks... then faster processors won't help.
If you are unwilling to try suggestions, and aren't willing to find
bottlenecks, try this:
1. Go out and buy the processors
2. Get fired because performance didn't improve
3. Let someone else have a go at it.
-har|||Sorry for the lack of clarification. Basically what I am
needing are suggestions on how to check for bottlenecks.
Thanks.
Don
>--Original Message--
>> It is Processor performance. I haven't noticed any
>> bottlenecks and there is 30GB of free space left. The
DB
>> is 9GB.
>Free disk space doesn't indicate that processor
performance is poor.
>If there are no bottlenecks... then faster processors
won't help.
>If you are unwilling to try suggestions, and aren't
willing to find
>bottlenecks, try this:
>1. Go out and buy the processors
>2. Get fired because performance didn't improve
>3. Let someone else have a go at it.
>-har
>
>
>.
>|||>--Original Message--
>"Don" <donolwert@.hotmail.com> wrote in message
>news:000b01c35c34$ee45c330$a401280a@.phx.gbl...
>> We are running an Enterprise CRM (SalesLogix) on SQL2K
>> SP3a.
>> The server we have is a Quad Xeon 500MHz, 4GB RAM.
>> We currently have 192 users that connect at any given
>> time, but usually no more than 70-80 at a time.
>> The perfomance has gradually been getting worse the last
>> few months and the usage has increased by about 30%
since
>> then as well.
>It may be time to rebuild the indices and update the
statistics... In
>addition, you may want to consider running the Index
Tuning Wizard to
>determine if performance would benefit by a few carefully
placed index's.
>> Would upgrading to a quad 1.5GHz Xeon with 4GB RAM
>> increase performance quite a bit?
>Where is the bottleneck? Is it processor? Is it disk?
Some performance
>monitor statistics would help answer those questions. I'd
start with my
>previous suggestions...
>Steve
It is Processor performance. I haven't noticed any
bottlenecks and there is 30GB of free space left. The DB
is 9GB.
>
>.
>sql
SP3a.
The server we have is a Quad Xeon 500MHz, 4GB RAM.
We currently have 192 users that connect at any given
time, but usually no more than 70-80 at a time.
The perfomance has gradually been getting worse the last
few months and the usage has increased by about 30% since
then as well.
Would upgrading to a quad 1.5GHz Xeon with 4GB RAM
increase performance quite a bit?"Don" <donolwert@.hotmail.com> wrote in message
news:000b01c35c34$ee45c330$a401280a@.phx.gbl...
> We are running an Enterprise CRM (SalesLogix) on SQL2K
> SP3a.
> The server we have is a Quad Xeon 500MHz, 4GB RAM.
> We currently have 192 users that connect at any given
> time, but usually no more than 70-80 at a time.
> The perfomance has gradually been getting worse the last
> few months and the usage has increased by about 30% since
> then as well.
It may be time to rebuild the indices and update the statistics... In
addition, you may want to consider running the Index Tuning Wizard to
determine if performance would benefit by a few carefully placed index's.
> Would upgrading to a quad 1.5GHz Xeon with 4GB RAM
> increase performance quite a bit?
Where is the bottleneck? Is it processor? Is it disk? Some performance
monitor statistics would help answer those questions. I'd start with my
previous suggestions...
Steve|||> It is Processor performance. I haven't noticed any
> bottlenecks and there is 30GB of free space left. The DB
> is 9GB.
Free disk space doesn't indicate that processor performance is poor.
If there are no bottlenecks... then faster processors won't help.
If you are unwilling to try suggestions, and aren't willing to find
bottlenecks, try this:
1. Go out and buy the processors
2. Get fired because performance didn't improve
3. Let someone else have a go at it.
-har|||Sorry for the lack of clarification. Basically what I am
needing are suggestions on how to check for bottlenecks.
Thanks.
Don
>--Original Message--
>> It is Processor performance. I haven't noticed any
>> bottlenecks and there is 30GB of free space left. The
DB
>> is 9GB.
>Free disk space doesn't indicate that processor
performance is poor.
>If there are no bottlenecks... then faster processors
won't help.
>If you are unwilling to try suggestions, and aren't
willing to find
>bottlenecks, try this:
>1. Go out and buy the processors
>2. Get fired because performance didn't improve
>3. Let someone else have a go at it.
>-har
>
>
>.
>|||>--Original Message--
>"Don" <donolwert@.hotmail.com> wrote in message
>news:000b01c35c34$ee45c330$a401280a@.phx.gbl...
>> We are running an Enterprise CRM (SalesLogix) on SQL2K
>> SP3a.
>> The server we have is a Quad Xeon 500MHz, 4GB RAM.
>> We currently have 192 users that connect at any given
>> time, but usually no more than 70-80 at a time.
>> The perfomance has gradually been getting worse the last
>> few months and the usage has increased by about 30%
since
>> then as well.
>It may be time to rebuild the indices and update the
statistics... In
>addition, you may want to consider running the Index
Tuning Wizard to
>determine if performance would benefit by a few carefully
placed index's.
>> Would upgrading to a quad 1.5GHz Xeon with 4GB RAM
>> increase performance quite a bit?
>Where is the bottleneck? Is it processor? Is it disk?
Some performance
>monitor statistics would help answer those questions. I'd
start with my
>previous suggestions...
>Steve
It is Processor performance. I haven't noticed any
bottlenecks and there is 30GB of free space left. The DB
is 9GB.
>
>.
>sql
Monday, March 19, 2012
New Role Assignment Question
I have just set up SQL Reporting Services in our Development environment and
want to set all users with browser or read-only access to our reports but do
not see how. I am going in through the web interface and it tells me that I
must have a valid domain group or interface. Any idea on how to just select
"Everyone"?DomainName\Everyone
ComputerName\Everyone
HTH, Jens Süßmeyer
--
http://www.sqlserver2005.de
--
"Charles Collins" <Charles Collins@.discussions.microsoft.com> schrieb im
Newsbeitrag news:234DF76B-A041-4989-A116-6CADDEB19E9B@.microsoft.com...
>I have just set up SQL Reporting Services in our Development environment
>and
> want to set all users with browser or read-only access to our reports but
> do
> not see how. I am going in through the web interface and it tells me that
> I
> must have a valid domain group or interface. Any idea on how to just
> select
> "Everyone"?|||Currently Reporting Services only supports Windows Authentication. Which
means you need to create a network group (with everyone you want) in it and
then give that network group access to the reports. Reporting Services
security is extensible though if you want to create your own security
extension (Not an easy task). Here is link to a microsoft example of
creating your own security extension...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
"Charles Collins" wrote:
> I have just set up SQL Reporting Services in our Development environment and
> want to set all users with browser or read-only access to our reports but do
> not see how. I am going in through the web interface and it tells me that I
> must have a valid domain group or interface. Any idea on how to just select
> "Everyone"?|||When I try that I get:
The user or group name '(domain or computer name)\everyone' is not
recognized. (rsUnknownUserName)
"Jens Sü�meyer" wrote:
> DomainName\Everyone
> ComputerName\Everyone
> HTH, Jens Sü�meyer
> --
> http://www.sqlserver2005.de
> --
> "Charles Collins" <Charles Collins@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:234DF76B-A041-4989-A116-6CADDEB19E9B@.microsoft.com...
> >I have just set up SQL Reporting Services in our Development environment
> >and
> > want to set all users with browser or read-only access to our reports but
> > do
> > not see how. I am going in through the web interface and it tells me that
> > I
> > must have a valid domain group or interface. Any idea on how to just
> > select
> > "Everyone"?
>
>|||Is there an way to assign mulitple users an role at once?
"Jens Sü�meyer" wrote:
> DomainName\Everyone
> ComputerName\Everyone
> HTH, Jens Sü�meyer
> --
> http://www.sqlserver2005.de
> --
> "Charles Collins" <Charles Collins@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:234DF76B-A041-4989-A116-6CADDEB19E9B@.microsoft.com...
> >I have just set up SQL Reporting Services in our Development environment
> >and
> > want to set all users with browser or read-only access to our reports but
> > do
> > not see how. I am going in through the web interface and it tells me that
> > I
> > must have a valid domain group or interface. Any idea on how to just
> > select
> > "Everyone"?
>
>
want to set all users with browser or read-only access to our reports but do
not see how. I am going in through the web interface and it tells me that I
must have a valid domain group or interface. Any idea on how to just select
"Everyone"?DomainName\Everyone
ComputerName\Everyone
HTH, Jens Süßmeyer
--
http://www.sqlserver2005.de
--
"Charles Collins" <Charles Collins@.discussions.microsoft.com> schrieb im
Newsbeitrag news:234DF76B-A041-4989-A116-6CADDEB19E9B@.microsoft.com...
>I have just set up SQL Reporting Services in our Development environment
>and
> want to set all users with browser or read-only access to our reports but
> do
> not see how. I am going in through the web interface and it tells me that
> I
> must have a valid domain group or interface. Any idea on how to just
> select
> "Everyone"?|||Currently Reporting Services only supports Windows Authentication. Which
means you need to create a network group (with everyone you want) in it and
then give that network group access to the reports. Reporting Services
security is extensible though if you want to create your own security
extension (Not an easy task). Here is link to a microsoft example of
creating your own security extension...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
"Charles Collins" wrote:
> I have just set up SQL Reporting Services in our Development environment and
> want to set all users with browser or read-only access to our reports but do
> not see how. I am going in through the web interface and it tells me that I
> must have a valid domain group or interface. Any idea on how to just select
> "Everyone"?|||When I try that I get:
The user or group name '(domain or computer name)\everyone' is not
recognized. (rsUnknownUserName)
"Jens Sü�meyer" wrote:
> DomainName\Everyone
> ComputerName\Everyone
> HTH, Jens Sü�meyer
> --
> http://www.sqlserver2005.de
> --
> "Charles Collins" <Charles Collins@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:234DF76B-A041-4989-A116-6CADDEB19E9B@.microsoft.com...
> >I have just set up SQL Reporting Services in our Development environment
> >and
> > want to set all users with browser or read-only access to our reports but
> > do
> > not see how. I am going in through the web interface and it tells me that
> > I
> > must have a valid domain group or interface. Any idea on how to just
> > select
> > "Everyone"?
>
>|||Is there an way to assign mulitple users an role at once?
"Jens Sü�meyer" wrote:
> DomainName\Everyone
> ComputerName\Everyone
> HTH, Jens Sü�meyer
> --
> http://www.sqlserver2005.de
> --
> "Charles Collins" <Charles Collins@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:234DF76B-A041-4989-A116-6CADDEB19E9B@.microsoft.com...
> >I have just set up SQL Reporting Services in our Development environment
> >and
> > want to set all users with browser or read-only access to our reports but
> > do
> > not see how. I am going in through the web interface and it tells me that
> > I
> > must have a valid domain group or interface. Any idea on how to just
> > select
> > "Everyone"?
>
>
Monday, March 12, 2012
New Production Server - Orphaned Users
Hi,
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both o
f
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.If I followed your chain correctly, you basically took your system databases
from a to b to c. Then
you take your user databases from a to c. This should mean that the logins e
xists with correct SID -
i.e., no orphaned users.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new producti
on
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP
2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production serv
er
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.|||Hi
http://dimantdatabasesolutions.blog...on.
html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both o
f
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.If I followed your chain correctly, you basically took your system databases
from a to b to c. Then
you take your user databases from a to c. This should mean that the logins e
xists with correct SID -
i.e., no orphaned users.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new producti
on
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP
2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production serv
er
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.|||Hi
http://dimantdatabasesolutions.blog...on.
html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
New Production Server - Orphaned Users
Hi,
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both of
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.
If I followed your chain correctly, you basically took your system databases from a to b to c. Then
you take your user databases from a to c. This should mean that the logins exists with correct SID -
i.e., no orphaned users.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
|||Hi
http://dimantdatabasesolutions.blogspot.com/2007/04/sql-or-windows-authentication.html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both of
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.
If I followed your chain correctly, you basically took your system databases from a to b to c. Then
you take your user databases from a to c. This should mean that the logins exists with correct SID -
i.e., no orphaned users.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
|||Hi
http://dimantdatabasesolutions.blogspot.com/2007/04/sql-or-windows-authentication.html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
New Production Server - Orphaned Users
Hi,
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both of
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.If I followed your chain correctly, you basically took your system databases from a to b to c. Then
you take your user databases from a to c. This should mean that the logins exists with correct SID -
i.e., no orphaned users.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.|||Hi
http://dimantdatabasesolutions.blogspot.com/2007/04/sql-or-windows-authentication.html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both of
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.If I followed your chain correctly, you basically took your system databases from a to b to c. Then
you take your user databases from a to c. This should mean that the logins exists with correct SID -
i.e., no orphaned users.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.|||Hi
http://dimantdatabasesolutions.blogspot.com/2007/04/sql-or-windows-authentication.html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
Friday, March 9, 2012
New kind of merge repl error floating point exception?
Got a weird one. Hope someone has seen it before. Need some smarts.
Rolled out 150 new laptops, all imaged the same for users with a local msde
sp3a. All installed with subscriptionDB.
Previously, all were synching well on the same Sql 2000 pub/distr, on the
same publications for 18 months.
50% now work just fine, the other half get the message below. I tried
reinits, reinstall and sp4 upgrade (per several bug doc, found 3 close).
Varied results, some success but not consistant. Temporary success with
failures occationally but never clean.
Dies on sp_MSenumchanges....
The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
------
A floating point exception occurred in the user process. Current transaction
is canceled.
(Source: Servername_removed (Data source); Error number: 3628)
------
The process was successfully stopped.
Any experiences with this, ideas of causes are appreciated.
Mike
If data falls in the woods and nobody is there to see it ...... ?
You could try running service pack 3a again on the subscribers although
it doesn't make logical sense why anything should be different. I know
of a similiar error if the clients are use Windows 95/98/ME. Try
running dbcc checkdb just in case there is some corruption in any of
the tables.
|||Thanks for the suggestions. Good ideas.
I tried reinstalling sp3 and a new subscriptionDB too.
Dumped the subscription and recreated it with the wizard too.
dbcc checkdb ran clean but I haven't caught one with a failure in action
yet. Will keep at it.
The randomness makes me wonder if the subscription proc timesout somehow
before the server can return info. The subs history shows it processes
uploads to some random article and then fails.
Mike
If data falls in the woods and nobody is there to see it ...... ?
"seanbell68@.gmail.com" wrote:
> You could try running service pack 3a again on the subscribers although
> it doesn't make logical sense why anything should be different. I know
> of a similiar error if the clients are use Windows 95/98/ME. Try
> running dbcc checkdb just in case there is some corruption in any of
> the tables.
>
|||any commonalities on the machines that do not work? also take in
consideration isp/routers/vpn/encryption etc?
"Tigermikefl" <Tigermikefl@.discussions.microsoft.com> wrote in message
news:0900566A-3A1B-44F4-8118-4427B4FBAD3B@.microsoft.com...[vbcol=seagreen]
> Thanks for the suggestions. Good ideas.
> I tried reinstalling sp3 and a new subscriptionDB too.
> Dumped the subscription and recreated it with the wizard too.
> dbcc checkdb ran clean but I haven't caught one with a failure in action
> yet. Will keep at it.
> The randomness makes me wonder if the subscription proc timesout somehow
> before the server can return info. The subs history shows it processes
> uploads to some random article and then fails.
> --
> Mike
> If data falls in the woods and nobody is there to see it ...... ?
>
> "seanbell68@.gmail.com" wrote:
|||Unfortunately no commonalities any found yet. All laptops in the same
shipment, imaged with the same WinXP. All received a new vpn client but half
are synching fine. Soho offices mostly, isp's vary.
I will poll the challenged as to ISP/Wireless/Routers etc to see if
something jumps out.
We are leaning towards a connection problem but can't figure how they all
get the same error and doesn't go into the retry mode via sql agent.
Mike
If data falls in the woods and nobody is there to see it ...... ?
"S c o t t K r a m e r" wrote:
> any commonalities on the machines that do not work? also take in
> consideration isp/routers/vpn/encryption etc?
>
> "Tigermikefl" <Tigermikefl@.discussions.microsoft.com> wrote in message
> news:0900566A-3A1B-44F4-8118-4427B4FBAD3B@.microsoft.com...
>
>
|||Turned out to be a problem with the newer cisco vpn client 4.6. Runs
errorless with earier client. Checking networking but no longer a repl issue.
Thanks for the input anywho.
Mike
If data falls in the woods and nobody is there to see it ...... ?
"Tigermikefl" wrote:
[vbcol=seagreen]
> Unfortunately no commonalities any found yet. All laptops in the same
> shipment, imaged with the same WinXP. All received a new vpn client but half
> are synching fine. Soho offices mostly, isp's vary.
> I will poll the challenged as to ISP/Wireless/Routers etc to see if
> something jumps out.
> We are leaning towards a connection problem but can't figure how they all
> get the same error and doesn't go into the retry mode via sql agent.
>
> --
> Mike
> If data falls in the woods and nobody is there to see it ...... ?
>
> "S c o t t K r a m e r" wrote:
Rolled out 150 new laptops, all imaged the same for users with a local msde
sp3a. All installed with subscriptionDB.
Previously, all were synching well on the same Sql 2000 pub/distr, on the
same publications for 18 months.
50% now work just fine, the other half get the message below. I tried
reinits, reinstall and sp4 upgrade (per several bug doc, found 3 close).
Varied results, some success but not consistant. Temporary success with
failures occationally but never clean.
Dies on sp_MSenumchanges....
The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
------
A floating point exception occurred in the user process. Current transaction
is canceled.
(Source: Servername_removed (Data source); Error number: 3628)
------
The process was successfully stopped.
Any experiences with this, ideas of causes are appreciated.
Mike
If data falls in the woods and nobody is there to see it ...... ?
You could try running service pack 3a again on the subscribers although
it doesn't make logical sense why anything should be different. I know
of a similiar error if the clients are use Windows 95/98/ME. Try
running dbcc checkdb just in case there is some corruption in any of
the tables.
|||Thanks for the suggestions. Good ideas.
I tried reinstalling sp3 and a new subscriptionDB too.
Dumped the subscription and recreated it with the wizard too.
dbcc checkdb ran clean but I haven't caught one with a failure in action
yet. Will keep at it.
The randomness makes me wonder if the subscription proc timesout somehow
before the server can return info. The subs history shows it processes
uploads to some random article and then fails.
Mike
If data falls in the woods and nobody is there to see it ...... ?
"seanbell68@.gmail.com" wrote:
> You could try running service pack 3a again on the subscribers although
> it doesn't make logical sense why anything should be different. I know
> of a similiar error if the clients are use Windows 95/98/ME. Try
> running dbcc checkdb just in case there is some corruption in any of
> the tables.
>
|||any commonalities on the machines that do not work? also take in
consideration isp/routers/vpn/encryption etc?
"Tigermikefl" <Tigermikefl@.discussions.microsoft.com> wrote in message
news:0900566A-3A1B-44F4-8118-4427B4FBAD3B@.microsoft.com...[vbcol=seagreen]
> Thanks for the suggestions. Good ideas.
> I tried reinstalling sp3 and a new subscriptionDB too.
> Dumped the subscription and recreated it with the wizard too.
> dbcc checkdb ran clean but I haven't caught one with a failure in action
> yet. Will keep at it.
> The randomness makes me wonder if the subscription proc timesout somehow
> before the server can return info. The subs history shows it processes
> uploads to some random article and then fails.
> --
> Mike
> If data falls in the woods and nobody is there to see it ...... ?
>
> "seanbell68@.gmail.com" wrote:
|||Unfortunately no commonalities any found yet. All laptops in the same
shipment, imaged with the same WinXP. All received a new vpn client but half
are synching fine. Soho offices mostly, isp's vary.
I will poll the challenged as to ISP/Wireless/Routers etc to see if
something jumps out.
We are leaning towards a connection problem but can't figure how they all
get the same error and doesn't go into the retry mode via sql agent.
Mike
If data falls in the woods and nobody is there to see it ...... ?
"S c o t t K r a m e r" wrote:
> any commonalities on the machines that do not work? also take in
> consideration isp/routers/vpn/encryption etc?
>
> "Tigermikefl" <Tigermikefl@.discussions.microsoft.com> wrote in message
> news:0900566A-3A1B-44F4-8118-4427B4FBAD3B@.microsoft.com...
>
>
|||Turned out to be a problem with the newer cisco vpn client 4.6. Runs
errorless with earier client. Checking networking but no longer a repl issue.
Thanks for the input anywho.
Mike
If data falls in the woods and nobody is there to see it ...... ?
"Tigermikefl" wrote:
[vbcol=seagreen]
> Unfortunately no commonalities any found yet. All laptops in the same
> shipment, imaged with the same WinXP. All received a new vpn client but half
> are synching fine. Soho offices mostly, isp's vary.
> I will poll the challenged as to ISP/Wireless/Routers etc to see if
> something jumps out.
> We are leaning towards a connection problem but can't figure how they all
> get the same error and doesn't go into the retry mode via sql agent.
>
> --
> Mike
> If data falls in the woods and nobody is there to see it ...... ?
>
> "S c o t t K r a m e r" wrote:
Subscribe to:
Posts (Atom)