Max Num of Worker Threads and User Connections/Logins

Hi everyone,
I need to know what is the relationship between the "Maxium Number of Worker Threads" setting (default = 255) and user connections/sessions/logins.
From time to time, we are experiencing random login failure for several busy databases. On average, we see about 264 total sessions on the box and we were wondering if the max worker threads number, bumping it up would fix the issue.
Can anyone offer any suggestions?
Thanks in advance,
Errol Neal
As long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)
"Errol U. Neal" <eneal@.enhtech.com> wrote in message
news:09B0F39B-1468-4069-A8A1-BF2AF2E645C8@.microsoft.com...
> Hi everyone,
> I need to know what is the relationship between the "Maxium Number of
Worker Threads" setting (default = 255) and user
connections/sessions/logins.
> From time to time, we are experiencing random login failure for several
busy databases. On average, we see about 264 total sessions on the box and
we were wondering if the max worker threads number, bumping it up would fix
the issue.
> Can anyone offer any suggestions?
>
> Thanks in advance,
>
> Errol Neal
|||Okay. I understand that. Thanks!
But why are we having random login failures? We are per-processor licensing so I am confused. Its not that the login is timing out. They are outright failing and I know because I am doing a SQL Server Trace and watching them as they fail.
-- Wayne Snyder wrote: --
As long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)
|||Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Errol Uriel Neal" <eneal@.enhtech.com> wrote in message
news:94D7AB61-A7F2-4FA1-B19C-D79B64B3B23D@.microsoft.com...
> Okay. I understand that. Thanks!
> But why are we having random login failures? We are per-processor
licensing so I am confused. Its not that the login is timing out. They are
outright failing and I know because I am doing a SQL Server Trace and
watching them as they fail.
>
> -- Wayne Snyder wrote: --
> As long as there are fewer than "Max worker threads" number of
connections,
> each connection gets its own individual thread... Once you go over
that
> number, several connections will share the same thread... You can
increase
> the number of worker threads, but that uses more memory ( even if
there are
> fewer connections.)
> Thread sharing could result in front end timeouts ( especially if the
other
> connection you are sharing the thread with is a busy one.)
>
|||No. There is nothing like that or remotely similiar to that in the logs.
I've been having this issue now for over a month. I even completely rebuilt my SQL Server because
of it.
-- Jasper Smith wrote: --
Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org

Max Num of Worker Threads and User Connections/Logins

Hi everyone,
I need to know what is the relationship between the "Maxium Number of Worker
Threads" setting (default = 255) and user connections/sessions/logins.
From time to time, we are experiencing random login failure for several busy
databases. On average, we see about 264 total sessions on the box and we we
re wondering if the max worker threads number, bumping it up would fix the i
ssue.
Can anyone offer any suggestions?
Thanks in advance,
Errol NealAs long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)
"Errol U. Neal" <eneal@.enhtech.com> wrote in message
news:09B0F39B-1468-4069-A8A1-BF2AF2E645C8@.microsoft.com...
> Hi everyone,
> I need to know what is the relationship between the "Maxium Number of
Worker Threads" setting (default = 255) and user
connections/sessions/logins.
> From time to time, we are experiencing random login failure for several
busy databases. On average, we see about 264 total sessions on the box and
we were wondering if the max worker threads number, bumping it up would fix
the issue.
> Can anyone offer any suggestions?
>
> Thanks in advance,
>
> Errol Neal|||Okay. I understand that. Thanks!
But why are we having random login failures? We are per-processor licensing
so I am confused. Its not that the login is timing out. They are outright fa
iling and I know because I am doing a SQL Server Trace and watching them as
they fail.
-- Wayne Snyder wrote: --
As long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)|||Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Errol Uriel Neal" <eneal@.enhtech.com> wrote in message
news:94D7AB61-A7F2-4FA1-B19C-D79B64B3B23D@.microsoft.com...
> Okay. I understand that. Thanks!
> But why are we having random login failures? We are per-processor
licensing so I am confused. Its not that the login is timing out. They are
outright failing and I know because I am doing a SQL Server Trace and
watching them as they fail.
>
> -- Wayne Snyder wrote: --
> As long as there are fewer than "Max worker threads" number of
connections,
> each connection gets its own individual thread... Once you go over
that
> number, several connections will share the same thread... You can
increase
> the number of worker threads, but that uses more memory ( even if
there are
> fewer connections.)
> Thread sharing could result in front end timeouts ( especially if the
other
> connection you are sharing the thread with is a busy one.)
>|||No. There is nothing like that or remotely similiar to that in the logs.
I've been having this issue now for over a month. I even completely rebuilt
my SQL Server because
of it.
-- Jasper Smith wrote: --
Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.orgsql

Max Num of Worker Threads and User Connections/Logins

Hi everyone
I need to know what is the relationship between the "Maxium Number of Worker Threads" setting (default = 255) and user connections/sessions/logins.
From time to time, we are experiencing random login failure for several busy databases. On average, we see about 264 total sessions on the box and we were wondering if the max worker threads number, bumping it up would fix the issue.
Can anyone offer any suggestions
Thanks in advance
Errol NealAs long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)
"Errol U. Neal" <eneal@.enhtech.com> wrote in message
news:09B0F39B-1468-4069-A8A1-BF2AF2E645C8@.microsoft.com...
> Hi everyone,
> I need to know what is the relationship between the "Maxium Number of
Worker Threads" setting (default = 255) and user
connections/sessions/logins.
> From time to time, we are experiencing random login failure for several
busy databases. On average, we see about 264 total sessions on the box and
we were wondering if the max worker threads number, bumping it up would fix
the issue.
> Can anyone offer any suggestions?
>
> Thanks in advance,
>
> Errol Neal|||Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Errol Uriel Neal" <eneal@.enhtech.com> wrote in message
news:94D7AB61-A7F2-4FA1-B19C-D79B64B3B23D@.microsoft.com...
> Okay. I understand that. Thanks!
> But why are we having random login failures? We are per-processor
licensing so I am confused. Its not that the login is timing out. They are
outright failing and I know because I am doing a SQL Server Trace and
watching them as they fail.
>
> -- Wayne Snyder wrote: --
> As long as there are fewer than "Max worker threads" number of
connections,
> each connection gets its own individual thread... Once you go over
that
> number, several connections will share the same thread... You can
increase
> the number of worker threads, but that uses more memory ( even if
there are
> fewer connections.)
> Thread sharing could result in front end timeouts ( especially if the
other
> connection you are sharing the thread with is a busy one.)
>|||No. There is nothing like that or remotely similiar to that in the logs.
I've been having this issue now for over a month. I even completely rebuilt my SQL Server because
of it.
-- Jasper Smith wrote: --
Do you see any errors on the SQL error log e.g. "could not spawn proces
login thread" or similar ? We have seen these under conditions of hig
memory contention especially in the MemToLeave area where new threads canno
allocate enough memory to start
--
HT
Jasper Smith (SQL Server MVP
I support PASS - the definitive, globa
community for SQL Server professionals
http://www.sqlpass.or

Max Length of a SQL User ID

Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
Thanks
Hello,
SQL Server login's maximum size is 128 characters. You can determine it's
size by examine sysxlogins table in master database. Look for "name"
attribute in sysxlogins table and check it's "size" property.
Regards,
Tomislav Kralj
"Sarah Kingswell" <skingswell@.xonitek.co.uk> wrote in message
news:%23rvzXCUKFHA.2648@.TK2MSFTNGP14.phx.gbl...
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>
|||Sarah,
Are you talking about sysusers.uid? That is a smallint, so the max value
for that column would be 32767.
If you are talking about sysusers.name then the max length is 256, or
128 characters as its Unicode.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sarah Kingswell wrote:
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>

Max Length of a SQL User ID

Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
ThanksHello,
SQL Server login's maximum size is 128 characters. You can determine it's
size by examine sysxlogins table in master database. Look for "name"
attribute in sysxlogins table and check it's "size" property.
Regards,
Tomislav Kralj
"Sarah Kingswell" <skingswell@.xonitek.co.uk> wrote in message
news:%23rvzXCUKFHA.2648@.TK2MSFTNGP14.phx.gbl...
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>|||Sarah,
Are you talking about sysusers.uid? That is a smallint, so the max value
for that column would be 32767.
If you are talking about sysusers.name then the max length is 256, or
128 characters as its Unicode.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sarah Kingswell wrote:
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>

Max Length of a SQL User ID

Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
ThanksHello,
SQL Server login's maximum size is 128 characters. You can determine it's
size by examine sysxlogins table in master database. Look for "name"
attribute in sysxlogins table and check it's "size" property.
Regards,
Tomislav Kralj
"Sarah Kingswell" <skingswell@.xonitek.co.uk> wrote in message
news:%23rvzXCUKFHA.2648@.TK2MSFTNGP14.phx.gbl...
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>|||Sarah,
Are you talking about sysusers.uid? That is a smallint, so the max value
for that column would be 32767.
If you are talking about sysusers.name then the max length is 256, or
128 characters as its Unicode.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sarah Kingswell wrote:
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>

Max Height problem!

I have written a VB .Net application over 33 webforms which act as a "Wizard" interface by collecting data from a user on each screen - I have one backend SQL server 2000 table for each form.

When the user reaches the last form they have a "Print button" which when clicked creates a localreport, creates a dataset of all data across all tables, creates a reportdatasource based on the dataset.

It then reads a local rdlc file and performs various formatting options by dynamically changing the XML.

I then call LoadReportDefinition to load the report.

I then render the report as a PDF to a byte array and write the array to the response object:-

'Populate(Dataset)

thisdataSet = SqlHelper.ExecuteDataset(sqlConn, "spReportData", FormID)

'Create ReportDataSource

datasource = New ReportDataSource("Accountform_spReportData", thisdataSet.Tables(0))

rpt.LoadReportDefinition(GetCustomizedReportDefinition(thisdataSet, "c:\accountform\Accountformdata.rdlc"))

rpt.DataSources.Clear()

rpt.DataSources.Add(datasource)

rpt.Refresh()

bytes = rpt.Render("PDF", Nothing, mimeType, encoding, extension, streamids, warnings)

' ''Sent byte array to client

Response.Clear()

Response.ContentType = mimeType

Response.AddHeader("content-disposition", "attachment; filename=New Account Form.pdf")

Response.BinaryWrite(bytes)

Response.End()

Everything has been working a treat until I realised that the the report body appears to be limited to 160 inches in height. My report only ever has 1 very wide record in it and is a series of rectangles containing textboxes each rectange is set to have a page break after it. Given that each rectange is 27cm in height it appears that the maximum number of pages I will be able to render is 15 - I need it to be able to go up to 33.

Is there any way of combining 2 reports in to one when you call the render method?

Any other suggestions will be greatly appreciated.

That's an odd limitation. You may want to look at exporting two PDF files and then using a tool like abcPDF to join them.

Here's another article using itextsharp.

http://geekswithblogs.net/bsherwin/archive/2007/06/29/113566.aspx

cheers,

Andrew

Max Connections

On a SQL 2005 server I have set the max user connections to 500 and
restarted the SQL Services. The server is showing this as the current
running value.
However the user connections is reporting over 30,000 and sp_who
returns over 150 with the majority of these listed as sleeping.
Why is there difference between the values returned?You are comparing the results of sp_who and what else? Where
are you getting the user connections from?
If you are using @.@.connections, that is the number of
connections and attempted connections since SQL Server
started. It will not correlated to sp_who.
-Sue
On 24 Aug 2006 06:44:11 -0700, robin9876@.hotmail.com wrote:

>On a SQL 2005 server I have set the max user connections to 500 and
>restarted the SQL Services. The server is showing this as the current
>running value.
>However the user connections is reporting over 30,000 and sp_who
>returns over 150 with the majority of these listed as sleeping.
>Why is there difference between the values returned?|||It was a MoM rule which appears to be reporting all connections and
comparing at against concurrent connections.
Sue Hoegemeier wrote:[vbcol=seagreen]
> You are comparing the results of sp_who and what else? Where
> are you getting the user connections from?
> If you are using @.@.connections, that is the number of
> connections and attempted connections since SQL Server
> started. It will not correlated to sp_who.
> -Sue
> On 24 Aug 2006 06:44:11 -0700, robin9876@.hotmail.com wrote:
>|||But that doesn't answer what it's using. I don't have MOM
running where I'm at and don't remember all the details of
what runs what but there is a way to view what it's using.
Otherwise you can use Profiler and see what MOM is executing
when it checks your SQL Server.
-Sue
On 25 Aug 2006 01:32:13 -0700, robin9876@.hotmail.com wrote:
[vbcol=seagreen]
>It was a MoM rule which appears to be reporting all connections and
>comparing at against concurrent connections.
>
>Sue Hoegemeier wrote:

Matrix SubTotals Visibility

I am creating a report using a matrix, and matrix subtotals.
I give the user the option of including the reporting hierarchy in their
reports. If they want to include it, I would like to hide the subtotal,
completely.
The reason for this is because if I include a hierarchy within a single
field of a report, the subtotals don't sum properly.
Is there any way to hide the entire subtotal field within a matrix report?
I have tried modifying the Hidden field (using an expression) of the
SubTotal textbox, but that only seems to hide the textbox itself, not
the subtotal fields.
Thanks,
NoahNevermind. Figured it out using InScope().
Noah
Noah wrote:
> I am creating a report using a matrix, and matrix subtotals.
> I give the user the option of including the reporting hierarchy in their
> reports. If they want to include it, I would like to hide the subtotal,
> completely.
> The reason for this is because if I include a hierarchy within a single
> field of a report, the subtotals don't sum properly.
> Is there any way to hide the entire subtotal field within a matrix report?
> I have tried modifying the Hidden field (using an expression) of the
> SubTotal textbox, but that only seems to hide the textbox itself, not
> the subtotal fields.
> Thanks,
> Noah

Matrix subtotals jump to subreport?

I have a complex issue. I have a matrix that has a cell that jumps the user to a subreport sending parameters. Well the report also has subtotals compliments of the matrix. Well those subtotals also jump to the subreport sending *first* parameters. I don't want the subtotals tojump anywhere! How do I disable navigation on the subtotal row? Crazy!

Have you found a solution to this? I am having the same problem.

Matrix Calculation - New to RS2000

Hello!
Iâ'm hoping somebody out there can help me! I am a new user of SQL Reporting
Services 2000 and have been asked to create a report showing studentsâ'
attendance. After a lot of reading and research I created a matrix report
that looks like this;
=Fields!attendance_type.value Total
=Fields!student_id.value
=Fields!week_no.value =Fields!register_id.Value =count(Fields!attendance_type.value)
It gives me the following results;
PR AA AB Total
0003 7 ACCA2 4 0 0 4
BUSA2 4 0 0 4
LANA2 2 2 0 4
8 ACCA2 2 2 0 4
BUSA2 2 2 0 4
LANA2 2 0 0 2
9 ACCA2 4 0 0 4
BUSA2 2 0 2 4
LANA2 3 0 0 3
10 ACCA2 4 0 0 4
BUSA2 4 0 0 4
LANA2 3 0 0 3
I would now like to add another column next to Total (subtotal of
=Fields!attendance_type.value) to calculate the % Attendance by using
PR/Total*100.
So in the end, I want something like this;
PR AA AB Total % Attendance
0003 7 ACCA2 4 0 0 4 100
BUSA2 4 0 0 4 100
LANA2 2 2 0 4 50
8 ACCA2 2 2 0 4 50
BUSA2 2 2 0 4 50
LANA2 2 0 0 2 100
Your help would be much appreciatedâ?¦
Wilma KhaliqYou can do a second query and append it to this one with "union", like
select blah blah from blah where blah
union
select blah2 blah2 from blah2 where blah2
except in the bottom select you can do your total, making a new type called
'TOTAL'
--
"Everyone knows something you don't know"
"Whee4ever" wrote:
> Hello!
> Iâ'm hoping somebody out there can help me! I am a new user of SQL Reporting
> Services 2000 and have been asked to create a report showing studentsâ'
> attendance. After a lot of reading and research I created a matrix report
> that looks like this;
> =Fields!attendance_type.value Total
> =Fields!student_id.value
> =Fields!week_no.value =Fields!register_id.Value =count(Fields!attendance_type.value)
> It gives me the following results;
> PR AA AB Total
> 0003 7 ACCA2 4 0 0 4
> BUSA2 4 0 0 4
> LANA2 2 2 0 4
> 8 ACCA2 2 2 0 4
> BUSA2 2 2 0 4
> LANA2 2 0 0 2
> 9 ACCA2 4 0 0 4
> BUSA2 2 0 2 4
> LANA2 3 0 0 3
> 10 ACCA2 4 0 0 4
> BUSA2 4 0 0 4
> LANA2 3 0 0 3
> I would now like to add another column next to Total (subtotal of
> =Fields!attendance_type.value) to calculate the % Attendance by using
> PR/Total*100.
> So in the end, I want something like this;
> PR AA AB Total % Attendance
> 0003 7 ACCA2 4 0 0 4 100
> BUSA2 4 0 0 4 100
> LANA2 2 2 0 4 50
> 8 ACCA2 2 2 0 4 50
> BUSA2 2 2 0 4 50
> LANA2 2 0 0 2 100
> Your help would be much appreciatedâ?¦
> Wilma Khaliq

Matrix / Table Combo

Hello,
I have an request that is throwing me for a loop. The user is asking
for a report that provides purchasing amounts by months for the last
15 months, then asking for summary stats from different tables, i.e
sales, cogs and inventory. Normally I would use a matrix report to
present the 15 months of data. I could use sub queries to retrieve
all
the columns that are needed, but I was hoping there was a simpler
solution. Any thoughts or suggestions would be greatly appreciated.
R/ AnthonyOn Jan 29, 4:14 pm, awakin <a...@.ibtinc.com> wrote:
> Hello,
> I have an request that is throwing me for a loop. The user is asking
> for a report that provides purchasing amounts by months for the last
> 15 months, then asking for summary stats from different tables, i.e
> sales, cogs and inventory. Normally I would use a matrix report to
> present the 15 months of data. I could use sub queries to retrieve
> all
> the columns that are needed, but I was hoping there was a simpler
> solution. Any thoughts or suggestions would be greatly appreciated.
> R/ Anthony
As you eluded to, you could use a nested table in a matrix control.
One alternative would be to nest a subreport in the matrix control and
pass parameters, where necessary, from the matrix control to the
subreport. Also, you could use Jump to Report in the navigation
properties of a cell in the matrix control to jump to another report
and pass parameters where necessary. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

mastlog.ldf

our mastlog.ldf file of Master database got deleted accidently by some user.
Is there anyway that the database could be started and new log file created
. master.mdf file is intact.
Thanks
ATDid you try restarting the server? If it won't start then you can rebuild
Master using the rebuildm utility (see Books Online for details). Then start
the server in single-user mode, restore Master from a backup (you do backup
the Master database don't you...?) or manually reattach your databases,
recreate logins, etc.
Make sure that the location of your database files is only accessible by the
administrator and the SQL Server service account so that this can't happen
again.
David Portas
SQL Server MVP
--|||David,
There is no backup available for master database. all I have is mdf file. Is
n't there any way that I can use this file to rebuild master database.
Thanks
AT|||HI
Maybe help for you:
I tested the following procedure, and successfully completed, but not guaran
tee your success.
And the future: Backup system databases periodically (daily)!
Copy to test server the master.mdf and rename
Use sp_attach_single_file_db wit another name than master (eg: NewMaser)
Use rebuilm.exe. (Copy SQL setup cd to hard disk and remove the read only fl
ag from files!)
Reinstall Service Packs and patches.
Stop the SQL server.
Create file backup from master.mdf and mastlog.ldf (Maybe You need restart
the restore)
Then start the server in single-user mode
--Like another way from here
Allow modifications to be made directly to the system catalogs
Update sysconfigures, syscurconfigs, tables from NewMaster database
Create insert statements and copy data from NewMaster to master database (US
E: WHERE NOT IN NEW MASTER..TABLE)
-sysaltfiles (or attach all production database and distribution if exist)
-sysservers (better: Recreate Linked Servers from documentation.)
-sysmessages (It is easy)
-sysxlogins (better: use the another way procedure for recreate logins)
-sysusers (or recreate users in master)
Disable modifications to be made directly to the system catalogs
Backup the master database
Test the server
Restart server
Backup master database
Another way:
-Recreate logins:
read the folowing: Microsoft Knowledge Base Article - 246133
< http://support.microsoft.com/defaul...133&Product=sql
>
Rewrite the sp_help_revlogin (use the attachaed database as source eg: FROM
master..sysxlogins --> FROM TESTSERVER.NewMaster.dbo.sysxlogins)
Recreate Linked Servers from documentation. (If You used remote server for r
eplication create linked server instead of remote)
Recreate users on master
Attach all production databases and distribution database.
Import custom sysmessages from NewMaster
Disable modifications to be made directly to the system catalogs
Backup the master database
Test the server
Restart server
Backup master database
At end:
Create scheduled backup for system databases.
And repair and repair until errors disappear. (The original values in NewMas
ter help You, do not drop!)
JBandi

master.dbo.xp_fixeddrives

SQL Server 2000
master.dbo.xp_fixeddrives stored procedure is reporting different values
when executed by 'sa' and a regular user.
Results:
(When executed by 'sa')
drive MB free
-- --
C 18432
D 118784
E 16384
(3 row(s) affected)
(When executed by 'UserA')
drive MB free
-- --
C 8192
D 68608
E 3072
(3 row(s) affected)
Is there any reason for this difference?
Thanks,
--payyans
sorry this might be stating the obvious but,
ensure that UserA and sa are logged on to the same server.
"payyans" wrote:

> SQL Server 2000
> --
> master.dbo.xp_fixeddrives stored procedure is reporting different values
> when executed by 'sa' and a regular user.
> Results:
> (When executed by 'sa')
> drive MB free
> -- --
> C 18432
> D 118784
> E 16384
> (3 row(s) affected)
> (When executed by 'UserA')
> drive MB free
> -- --
> C 8192
> D 68608
> E 3072
> (3 row(s) affected)
> Is there any reason for this difference?
> Thanks,
> --payyans
>