Binary Tree Problem in SQLServer

Hi Members
I m new in this forum, I have have Binary Tree database in SQL Server with
table fields(Mcode,Mname,LeftMCode,RightMCode). i want to display downline and pairs of each member.
can any one help me out?
Regards
Amirbkkread this.
is for OLAP, but, maybe help you.

http://www.codeproject.com/cs/database/tree_olap.asp|||From your column names, I'm guessing your are dealing with a Nested Set model ala' Joe Celko, rather than the more common Adjencency Model.
You should be able to find some code samples here:
http://www.intelligententerprise.com/001020/celko.jhtml?_requestid=1266295
...or by googling "Celko Nested Sets".|||Thanx for reply

But i have little prob that all nodes will be freely put on any side means any member can be put on left or right side and my db will grow very fast and estimated records will be more than 100000 with in few months

so if i use lineage and depth methods can i store path in one fields
and if use set model than i think , left node must be fill first and right node must be +1 than its left node.
and in my db any node(member) should be put on any side

so guys and suggestion will be higly appreciated.
i m going to build db with in few days , plz help me out.

Regards,

Amir|||Thanx for reply

But i have little prob that all nodes will be freely put on any side means any member can be put on left or right side and my db will grow very fast and estimated records will be more than 100000 with in few months

so if i use lineage and depth methods can i store path in one fields
and if use set model than i think , left node must be fill first and right node must be +1 than its left node.
and in my db any node(member) should be put on any side

so guys and suggestion will be higly appreciated.
i m going to build db with in few days , plz help me out.

Regards,

Amir

big problem with sql server 2000 msde sp 4 (stops working by accident)

Hi,
I get the following error-message from sqlserver 2000 (msde edition)
I have no idea what is going wrong.
I was only able to get back to working state by
DBCC CHECKDB ALLOW-DATA-LOSS
(or restoring a backup)
But i do not want the db to crash at my customers ...
In the knowledge-base I found:
"An assertion or Msg 7987 may occur when an operation is performed on an
instance of SQL Server"
without any reason why inconsitencies can occur
This bug is at least known since 5th april 2005 ... and still known for
sql-server 9 (2005 I think)
I hope I oversaw something ... or does SQLServer realy stops to work by
chance?
please help!
2006-07-26 03:43:04.00 spid51 ex_raise2: Exception raised, major=79,
minor=87, severity=22, attempting to create symptom dump
2006-07-26 03:43:04.28 spid51 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 51, PSS = 0x414491a8, EC = 0x414494d8
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 7/26/2006
Time: 5:32:26 AM
User: N/A
Computer: HLX02
Description:
Error: 7987, Severity: 22, State: 3
A possible database consistency problem has been detected on database
'faroer'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on database
'faroer'.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 33 1f 00 00 16 00 00 00 3......
0008: 06 00 00 00 48 00 4c 00 ...H.L.
0010: 58 00 30 00 32 00 00 00 X.0.2...
0018: 07 00 00 00 66 00 61 00 ...f.a.
0020: 72 00 6f 00 65 00 72 00 r.o.e.r.
0028: 00 00 ..Sascha Bohnenkamp wrote:
> Hi,
> I get the following error-message from sqlserver 2000 (msde edition)
> I have no idea what is going wrong.
> I was only able to get back to working state by
> DBCC CHECKDB ALLOW-DATA-LOSS
> (or restoring a backup)
> But i do not want the db to crash at my customers ...
> In the knowledge-base I found:
> "An assertion or Msg 7987 may occur when an operation is performed on an
> instance of SQL Server"
> without any reason why inconsitencies can occur
> This bug is at least known since 5th april 2005 ... and still known for
> sql-server 9 (2005 I think)
> I hope I oversaw something ... or does SQLServer realy stops to work by
> chance?
> please help!
> 2006-07-26 03:43:04.00 spid51 ex_raise2: Exception raised, major=79,
> minor=87, severity=22, attempting to create symptom dump
> 2006-07-26 03:43:04.28 spid51 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 51, PSS = 0x414491a8, EC = 0x414494d8
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 7/26/2006
> Time: 5:32:26 AM
> User: N/A
> Computer: HLX02
> Description:
> Error: 7987, Severity: 22, State: 3
> A possible database consistency problem has been detected on database
> 'faroer'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on database
> 'faroer'.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 33 1f 00 00 16 00 00 00 3......
> 0008: 06 00 00 00 48 00 4c 00 ...H.L.
> 0010: 58 00 30 00 32 00 00 00 X.0.2...
> 0018: 07 00 00 00 66 00 61 00 ...f.a.
> 0020: 72 00 6f 00 65 00 72 00 r.o.e.r.
> 0028: 00 00 ..
No, SQL Server does not "stop working by accident". Most likely you
have flaky hardware that is causing corruption in your database file.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben schrieb:
> No, SQL Server does not "stop working by accident". Most likely you
> have flaky hardware that is causing corruption in your database file.
well ... are there any chance to find someting to help find the problem
in the log files of the server (or in the dumps) ?
From teh stack dump I cannot see any i/o problems ...
* Short Stack Dump
* 009BA08C Module(sqlservr+005BA08C) (GetOSErrString+00004F68)
* 009BA9B5 Module(sqlservr+005BA9B5) (GetOSErrString+00005891)
* 006EE757 Module(sqlservr+002EE757) (SQLExit+00186C60)
* 005FA686 Module(sqlservr+001FA686) (SQLExit+00092B8F)
* 006BA785 Module(sqlservr+002BA785) (SQLExit+00152C8E)
* 004040DA Module(sqlservr+000040DA)
* 0042ADAE Module(sqlservr+0002ADAE)
* 0042A3D3 Module(sqlservr+0002A3D3)
* 0043638B Module(sqlservr+0003638B)
* 0043288B Module(sqlservr+0003288B)
* 00432542 Module(sqlservr+00032542)
* 00434980 Module(sqlservr+00034980)
* 00432542 Module(sqlservr+00032542)
* 00434980 Module(sqlservr+00034980)
* 00432542 Module(sqlservr+00032542)
* 00861732 Module(sqlservr+00461732) (GetIMallocForMsxml+0006CBB2)
* 0086116B Module(sqlservr+0046116B) (GetIMallocForMsxml+0006C5EB)
* 00434980 Module(sqlservr+00034980)
* 00432542 Module(sqlservr+00032542)
* 005B810A Module(sqlservr+001B810A) (SQLExit+00050613)
* 005B8266 Module(sqlservr+001B8266) (SQLExit+0005076F)
* 004398A5 Module(sqlservr+000398A5)
* 004398A5 Module(sqlservr+000398A5)
* 0041D396 Module(sqlservr+0001D396)
* 00861732 Module(sqlservr+00461732) (GetIMallocForMsxml+0006CBB2)
* 0086116B Module(sqlservr+0046116B) (GetIMallocForMsxml+0006C5EB)
* 005B810A Module(sqlservr+001B810A) (SQLExit+00050613)
* 005B8266 Module(sqlservr+001B8266) (SQLExit+0005076F)
* 00434980 Module(sqlservr+00034980)
* 00432542 Module(sqlservr+00032542)
* 004194B9 Module(sqlservr+000194B9)
* 004193E4 Module(sqlservr+000193E4)
* 00429EAA Module(sqlservr+00029EAA)
* 00415D04 Module(sqlservr+00015D04)
* 00416214 Module(sqlservr+00016214)
* 00415F28 Module(sqlservr+00015F28)
* 0076C7D0 Module(sqlservr+0036C7D0) (SQLExit+00204CD9)
* 007704EF Module(sqlservr+003704EF) (SQLExit+002089F8)
* 0077099C Module(sqlservr+0037099C) (SQLExit+00208EA5)
* 006332EC Module(sqlservr+002332EC) (SQLExit+000CB7F5)
* 0043D005 Module(sqlservr+0003D005)
* 0042598D Module(sqlservr+0002598D)
* 41075309 Module(ums+00005309) (UmsThreadScheduler::ExitUser+00000459)|||Sascha Bohnenkamp wrote:
> Tracy McKibben schrieb:
>> No, SQL Server does not "stop working by accident". Most likely you
>> have flaky hardware that is causing corruption in your database file.
> well ... are there any chance to find someting to help find the problem
> in the log files of the server (or in the dumps) ?
> From teh stack dump I cannot see any i/o problems ...
> * Short Stack Dump
> * 009BA08C Module(sqlservr+005BA08C) (GetOSErrString+00004F68)
> * 009BA9B5 Module(sqlservr+005BA9B5) (GetOSErrString+00005891)
> * 006EE757 Module(sqlservr+002EE757) (SQLExit+00186C60)
> * 005FA686 Module(sqlservr+001FA686) (SQLExit+00092B8F)
> * 006BA785 Module(sqlservr+002BA785) (SQLExit+00152C8E)
> * 004040DA Module(sqlservr+000040DA)
> * 0042ADAE Module(sqlservr+0002ADAE)
> * 0042A3D3 Module(sqlservr+0002A3D3)
> * 0043638B Module(sqlservr+0003638B)
> * 0043288B Module(sqlservr+0003288B)
> * 00432542 Module(sqlservr+00032542)
> * 00434980 Module(sqlservr+00034980)
> * 00432542 Module(sqlservr+00032542)
> * 00434980 Module(sqlservr+00034980)
> * 00432542 Module(sqlservr+00032542)
> * 00861732 Module(sqlservr+00461732) (GetIMallocForMsxml+0006CBB2)
> * 0086116B Module(sqlservr+0046116B) (GetIMallocForMsxml+0006C5EB)
> * 00434980 Module(sqlservr+00034980)
> * 00432542 Module(sqlservr+00032542)
> * 005B810A Module(sqlservr+001B810A) (SQLExit+00050613)
> * 005B8266 Module(sqlservr+001B8266) (SQLExit+0005076F)
> * 004398A5 Module(sqlservr+000398A5)
> * 004398A5 Module(sqlservr+000398A5)
> * 0041D396 Module(sqlservr+0001D396)
> * 00861732 Module(sqlservr+00461732) (GetIMallocForMsxml+0006CBB2)
> * 0086116B Module(sqlservr+0046116B) (GetIMallocForMsxml+0006C5EB)
> * 005B810A Module(sqlservr+001B810A) (SQLExit+00050613)
> * 005B8266 Module(sqlservr+001B8266) (SQLExit+0005076F)
> * 00434980 Module(sqlservr+00034980)
> * 00432542 Module(sqlservr+00032542)
> * 004194B9 Module(sqlservr+000194B9)
> * 004193E4 Module(sqlservr+000193E4)
> * 00429EAA Module(sqlservr+00029EAA)
> * 00415D04 Module(sqlservr+00015D04)
> * 00416214 Module(sqlservr+00016214)
> * 00415F28 Module(sqlservr+00015F28)
> * 0076C7D0 Module(sqlservr+0036C7D0) (SQLExit+00204CD9)
> * 007704EF Module(sqlservr+003704EF) (SQLExit+002089F8)
> * 0077099C Module(sqlservr+0037099C) (SQLExit+00208EA5)
> * 006332EC Module(sqlservr+002332EC) (SQLExit+000CB7F5)
> * 0043D005 Module(sqlservr+0003D005)
> * 0042598D Module(sqlservr+0002598D)
> * 41075309 Module(ums+00005309) (UmsThreadScheduler::ExitUser+00000459)
Doesn't have to be an I/O problem - it could be bad RAM, a bad CPU, any
number of things. You should run some hardware diagnostics on the
machine, perhaps even open an incident with Microsoft - they can help
you decipher the logs.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Big inconsistency!

Hi,

i have a sqlserver 2005 mergereplication.

some facts:

SQL Server 2005 9.0.3175 Standard Edition german

1 Distributor / Publisher (same Server)

10 Subscriber

30 GB Database with 200 Tables ; in sum 35,000,000 rows

Every subscriber can change data.

Sometimes (i think in 1 of 1000 cases) following curious error occured:

the subscriber update data (for example varchar value), but the changes aren′t replicated to the publisher.

In case of our 35Mil rows, this is not acceptable.

What can I do? I have no specified error, no errormessage, but the data isn′t correct.

There is big inconsistency!!!

Any assistance gratefully received,

Best Regards

Thorsten Ueberschaer

1. can you reproduce the problem? i.e. can you make a change to a subscriber and for the change NOT to appear on the Publisher and/or other subscribers within reasonable time [with network connectivity, and several runs of the Distribution Agents] ?

2. is this a permissions problem? obviously the DA's need access rights to be able to replay changes elsewhere.

3. have all subscribers been initialised ? should all start with same data [otherwise an UPDATE will fail later if there is no matching PK]

4. have you got sensible identities ? for INSERTs you should review the identity settings

sp_addmergearticle
[ , [ @.vertical_partition = ] 'vertical_partition' ]
[ , [ @.auto_identity_range = ] 'auto_identity_range' ]
[ , [ @.pub_identity_range = ] pub_identity_range ]
[ , [ @.identity_range = ] identity_range ]
[ , [ @.subscriber_upload_options = ] subscriber_upload_options ]
[ , [ @.identityrangemanagementoption = ] 'identityrangemanagementoption' ]
and do you have "NOT FOR REPLICATION" to prevent frictions ?

5. what collision resolver are you using? - perhaps a merge collision is being lost by resolver

- suggest more logging [e.g. change agent profile to verbose]

HTH

Dick

|||

hello

1. no i can′t reproduce the problem.....

2. the replicationagents work in sysadmin-mode, in my opinion is this not a permission problem

3. yes, all subscribers have been initialised with the same data

4. all tables have uniqueidentifier-pk and -rowguid column, all fk′s are "not for replication"

5. 195 of our tables solve the collision with the standard collision resolver, 5 with "later wins", but i think, that is not a conflict problem, because, after a conflict all subscriber must have the same date (the winner or the loser)

any idea?

thanks

thorsten ueberschaer

|||

Find a row that has not replicated. Pick off the value in the rowguid column. Search the MSmerge_contents table and see if a row exists for this rowguid value. That's step #1. If it isn't logged into MSmerge_contents by the triggers, it is never going to replicate.

|||

hi

this was my first idea

but in msmerge_contents a row exists for my rowguid value

bye

|||

What is the generation value? Have you tried to validate your subscriptions? What is the max generation that exists on the publisher and the subscriber in question?

|||

the generationvalue is 218016

the maxgeneration on publisher is 4647424 and on subscriber is 4049693

i don′t understand my problem

sometimes it works, sometimes not

no exception, no error

it′s not reproduceable

i don′t like it :-(

|||

If it happens more than once, it is reproducible somehow. It's a matter of figuring out the exact combination of actions that causes it. No, they aren't always straightforward. Tracking some of these things down can take weeks or months to isolate the problem. I have 6 open support cases dealing with issues in the merge metadata, the newest one has been open for over 2 weeks and while we can see the bad entries and know how to manually fix them, we still can't come up with a way to reproduce the problem. The oldest one I have on the books has been there for over 6 months and a repro still hasn't been isolated.

Then there is the one with subscribers mysteriously getting blown out which took over a month and a half before we finally figured out what the heck was happening and came up with an artificial way of reproducing it. Turns out that DNS was handing out the same IP address to more than one machine, from the perspective of SQL Server, but the DNS entry was not updated right away. This caused SQL Server to connect to MachineA which DNS resolved to an IP address which was actually MachineB thereby causing replication to think that everything was screwed up and to remove the subscription information. Try reliably reproducing something like that which only creates itself under some very specific VPN connection cicumstances which have to occur within a specific time sequence, between cycles of the merge engine.

Now that you have the generation number. Take a look in MSmerge_genhistory on the publisher and subscriber and see if an entry for this generation exists.

|||

i have this problem sinc april :-(

i took a look in msmerge_genhistory, and the result is strange:

on publisher: the data is correct, there is a row

on the subscriber which generate the update: the data is also correct

on next subscriber, the data isn′t correct, there is no entry in msmerge_genhistory

|||

I'm sorry, can't help with April. If you have this issue going back 6 months, that makes it extraordinarily difficult to try and track it down. If there isn't a row in MSmerge_genhistory for that generation, it means that the merge engine did not see it as a change to be propagated for some reason and therefore the change did not move. Again, I don't know why it would do that and it isn't going to be easy to find, because you have 6 months worth of change in this environment that the answer is buried within.

Have you ever run validation? If so, what were the results?

Big inconsistency!

Hi,

i have a sqlserver 2005 mergereplication.

some facts:

SQL Server 2005 9.0.3175 Standard Edition german

1 Distributor / Publisher (same Server)

10 Subscriber

30 GB Database with 200 Tables ; in sum 35,000,000 rows

Every subscriber can change data.

Sometimes (i think in 1 of 1000 cases) following curious error occured:

the subscriber update data (for example varchar value), but the changes aren′t replicated to the publisher.

In case of our 35Mil rows, this is not acceptable.

What can I do? I have no specified error, no errormessage, but the data isn′t correct.

There is big inconsistency!!!

Any assistance gratefully received,

Best Regards

Thorsten Ueberschaer

1. can you reproduce the problem? i.e. can you make a change to a subscriber and for the change NOT to appear on the Publisher and/or other subscribers within reasonable time [with network connectivity, and several runs of the Distribution Agents] ?

2. is this a permissions problem? obviously the DA's need access rights to be able to replay changes elsewhere.

3. have all subscribers been initialised ? should all start with same data [otherwise an UPDATE will fail later if there is no matching PK]

4. have you got sensible identities ? for INSERTs you should review the identity settings

sp_addmergearticle
[ , [ @.vertical_partition = ] 'vertical_partition' ]
[ , [ @.auto_identity_range = ] 'auto_identity_range' ]
[ , [ @.pub_identity_range = ] pub_identity_range ]
[ , [ @.identity_range = ] identity_range ]
[ , [ @.subscriber_upload_options = ] subscriber_upload_options ]
[ , [ @.identityrangemanagementoption = ] 'identityrangemanagementoption' ]
and do you have "NOT FOR REPLICATION" to prevent frictions ?

5. what collision resolver are you using? - perhaps a merge collision is being lost by resolver

- suggest more logging [e.g. change agent profile to verbose]

HTH

Dick

|||

hello

1. no i can′t reproduce the problem.....

2. the replicationagents work in sysadmin-mode, in my opinion is this not a permission problem

3. yes, all subscribers have been initialised with the same data

4. all tables have uniqueidentifier-pk and -rowguid column, all fk′s are "not for replication"

5. 195 of our tables solve the collision with the standard collision resolver, 5 with "later wins", but i think, that is not a conflict problem, because, after a conflict all subscriber must have the same date (the winner or the loser)

any idea?

thanks

thorsten ueberschaer

|||

Find a row that has not replicated. Pick off the value in the rowguid column. Search the MSmerge_contents table and see if a row exists for this rowguid value. That's step #1. If it isn't logged into MSmerge_contents by the triggers, it is never going to replicate.

|||

hi

this was my first idea

but in msmerge_contents a row exists for my rowguid value

bye

|||

What is the generation value? Have you tried to validate your subscriptions? What is the max generation that exists on the publisher and the subscriber in question?

|||

the generationvalue is 218016

the maxgeneration on publisher is 4647424 and on subscriber is 4049693

i don′t understand my problem

sometimes it works, sometimes not

no exception, no error

it′s not reproduceable

i don′t like it :-(

|||

If it happens more than once, it is reproducible somehow. It's a matter of figuring out the exact combination of actions that causes it. No, they aren't always straightforward. Tracking some of these things down can take weeks or months to isolate the problem. I have 6 open support cases dealing with issues in the merge metadata, the newest one has been open for over 2 weeks and while we can see the bad entries and know how to manually fix them, we still can't come up with a way to reproduce the problem. The oldest one I have on the books has been there for over 6 months and a repro still hasn't been isolated.

Then there is the one with subscribers mysteriously getting blown out which took over a month and a half before we finally figured out what the heck was happening and came up with an artificial way of reproducing it. Turns out that DNS was handing out the same IP address to more than one machine, from the perspective of SQL Server, but the DNS entry was not updated right away. This caused SQL Server to connect to MachineA which DNS resolved to an IP address which was actually MachineB thereby causing replication to think that everything was screwed up and to remove the subscription information. Try reliably reproducing something like that which only creates itself under some very specific VPN connection cicumstances which have to occur within a specific time sequence, between cycles of the merge engine.

Now that you have the generation number. Take a look in MSmerge_genhistory on the publisher and subscriber and see if an entry for this generation exists.

|||

i have this problem sinc april :-(

i took a look in msmerge_genhistory, and the result is strange:

on publisher: the data is correct, there is a row

on the subscriber which generate the update: the data is also correct

on next subscriber, the data isn′t correct, there is no entry in msmerge_genhistory

|||

I'm sorry, can't help with April. If you have this issue going back 6 months, that makes it extraordinarily difficult to try and track it down. If there isn't a row in MSmerge_genhistory for that generation, it means that the merge engine did not see it as a change to be propagated for some reason and therefore the change did not move. Again, I don't know why it would do that and it isn't going to be easy to find, because you have 6 months worth of change in this environment that the answer is buried within.

Have you ever run validation? If so, what were the results?

Beta Data Conversion

I have a data file in Beta 2 version, but now I've already uninstalled the
beta version and installed a new Release Version of SQLServer 2005. Does
anybody know how to convert the data file to be usable in SQLServer 2005?Jeffry
Are you talking about .MDF datafile? If you are , have you tried to attach
the file? There are two system stored procedures as sp_detach_db,
sp_attach_db
"Jeffrey Kam" <Jeffrey Kam@.discussions.microsoft.com> wrote in message
news:913ABCEF-F02C-44A2-B9C0-881A7452D331@.microsoft.com...
>I have a data file in Beta 2 version, but now I've already uninstalled the
> beta version and installed a new Release Version of SQLServer 2005. Does
> anybody know how to convert the data file to be usable in SQLServer 2005?|||i tried to attach directly but it said it doesn't support beta version
"Uri Dimant" wrote:
> Jeffry
> Are you talking about .MDF datafile? If you are , have you tried to attach
> the file? There are two system stored procedures as sp_detach_db,
> sp_attach_db
>
>
>
> "Jeffrey Kam" <Jeffrey Kam@.discussions.microsoft.com> wrote in message
> news:913ABCEF-F02C-44A2-B9C0-881A7452D331@.microsoft.com...
> >I have a data file in Beta 2 version, but now I've already uninstalled the
> > beta version and installed a new Release Version of SQLServer 2005. Does
> > anybody know how to convert the data file to be usable in SQLServer 2005?
>
>|||Yep, I see. Probably RESTORE command will not work as well.
Do you have still BETA CD to install it and transfer the data ?
Unfortanutally I have no idea (if above does not work) how to restore the
data
"Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
news:EE6DD8D9-FE2E-4566-903F-05F3748C2E7A@.microsoft.com...
>i tried to attach directly but it said it doesn't support beta version
> "Uri Dimant" wrote:
>> Jeffry
>> Are you talking about .MDF datafile? If you are , have you tried to
>> attach
>> the file? There are two system stored procedures as sp_detach_db,
>> sp_attach_db
>>
>>
>>
>> "Jeffrey Kam" <Jeffrey Kam@.discussions.microsoft.com> wrote in message
>> news:913ABCEF-F02C-44A2-B9C0-881A7452D331@.microsoft.com...
>> >I have a data file in Beta 2 version, but now I've already uninstalled
>> >the
>> > beta version and installed a new Release Version of SQLServer 2005.
>> > Does
>> > anybody know how to convert the data file to be usable in SQLServer
>> > 2005?
>>|||Thank you for your reply
Sorry, I still couldn't find it. that's why I want a solution without setup
another Beta 2. Does Microsoft provide such tools?
"Uri Dimant" wrote:
> Yep, I see. Probably RESTORE command will not work as well.
> Do you have still BETA CD to install it and transfer the data ?
>
> Unfortanutally I have no idea (if above does not work) how to restore the
> data
>
> "Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
> news:EE6DD8D9-FE2E-4566-903F-05F3748C2E7A@.microsoft.com...
> >i tried to attach directly but it said it doesn't support beta version
> >
> > "Uri Dimant" wrote:
> >
> >> Jeffry
> >> Are you talking about .MDF datafile? If you are , have you tried to
> >> attach
> >> the file? There are two system stored procedures as sp_detach_db,
> >> sp_attach_db
> >>
> >>
> >>
> >>
> >>
> >>
> >> "Jeffrey Kam" <Jeffrey Kam@.discussions.microsoft.com> wrote in message
> >> news:913ABCEF-F02C-44A2-B9C0-881A7452D331@.microsoft.com...
> >> >I have a data file in Beta 2 version, but now I've already uninstalled
> >> >the
> >> > beta version and installed a new Release Version of SQLServer 2005.
> >> > Does
> >> > anybody know how to convert the data file to be usable in SQLServer
> >> > 2005?
> >>
> >>
> >>
>
>|||Hi
I am not aware of such tools , sorry
"Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
news:BF911B6B-A4F6-4740-8DBA-46C09EB9BF20@.microsoft.com...
> Thank you for your reply
> Sorry, I still couldn't find it. that's why I want a solution without
> setup
> another Beta 2. Does Microsoft provide such tools?
> "Uri Dimant" wrote:
>> Yep, I see. Probably RESTORE command will not work as well.
>> Do you have still BETA CD to install it and transfer the data ?
>>
>> Unfortanutally I have no idea (if above does not work) how to restore the
>> data
>>
>> "Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
>> news:EE6DD8D9-FE2E-4566-903F-05F3748C2E7A@.microsoft.com...
>> >i tried to attach directly but it said it doesn't support beta version
>> >
>> > "Uri Dimant" wrote:
>> >
>> >> Jeffry
>> >> Are you talking about .MDF datafile? If you are , have you tried to
>> >> attach
>> >> the file? There are two system stored procedures as sp_detach_db,
>> >> sp_attach_db
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> "Jeffrey Kam" <Jeffrey Kam@.discussions.microsoft.com> wrote in message
>> >> news:913ABCEF-F02C-44A2-B9C0-881A7452D331@.microsoft.com...
>> >> >I have a data file in Beta 2 version, but now I've already
>> >> >uninstalled
>> >> >the
>> >> > beta version and installed a new Release Version of SQLServer 2005.
>> >> > Does
>> >> > anybody know how to convert the data file to be usable in SQLServer
>> >> > 2005?
>> >>
>> >>
>> >>
>>

Beta Data Conversion

I have a data file in Beta 2 version, but now I've already uninstalled the
beta version and installed a new Release Version of SQLServer 2005. Does
anybody know how to convert the data file to be usable in SQLServer 2005?
Jeffry
Are you talking about .MDF datafile? If you are , have you tried to attach
the file? There are two system stored procedures as sp_detach_db,
sp_attach_db
"Jeffrey Kam" <Jeffrey Kam@.discussions.microsoft.com> wrote in message
news:913ABCEF-F02C-44A2-B9C0-881A7452D331@.microsoft.com...
>I have a data file in Beta 2 version, but now I've already uninstalled the
> beta version and installed a new Release Version of SQLServer 2005. Does
> anybody know how to convert the data file to be usable in SQLServer 2005?
|||i tried to attach directly but it said it doesn't support beta version
"Uri Dimant" wrote:

> Jeffry
> Are you talking about .MDF datafile? If you are , have you tried to attach
> the file? There are two system stored procedures as sp_detach_db,
> sp_attach_db
>
>
>
> "Jeffrey Kam" <Jeffrey Kam@.discussions.microsoft.com> wrote in message
> news:913ABCEF-F02C-44A2-B9C0-881A7452D331@.microsoft.com...
>
>
|||Yep, I see. Probably RESTORE command will not work as well.
Do you have still BETA CD to install it and transfer the data ?
Unfortanutally I have no idea (if above does not work) how to restore the
data
"Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
news:EE6DD8D9-FE2E-4566-903F-05F3748C2E7A@.microsoft.com...[vbcol=seagreen]
>i tried to attach directly but it said it doesn't support beta version
> "Uri Dimant" wrote:
|||Thank you for your reply
Sorry, I still couldn't find it. that's why I want a solution without setup
another Beta 2. Does Microsoft provide such tools?
"Uri Dimant" wrote:

> Yep, I see. Probably RESTORE command will not work as well.
> Do you have still BETA CD to install it and transfer the data ?
>
> Unfortanutally I have no idea (if above does not work) how to restore the
> data
>
> "Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
> news:EE6DD8D9-FE2E-4566-903F-05F3748C2E7A@.microsoft.com...
>
>
|||Hi
I am not aware of such tools , sorry
"Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
news:BF911B6B-A4F6-4740-8DBA-46C09EB9BF20@.microsoft.com...[vbcol=seagreen]
> Thank you for your reply
> Sorry, I still couldn't find it. that's why I want a solution without
> setup
> another Beta 2. Does Microsoft provide such tools?
> "Uri Dimant" wrote:

Beta Data Conversion

I have a data file in Beta 2 version, but now I've already uninstalled the
beta version and installed a new Release Version of SQLServer 2005. Does
anybody know how to convert the data file to be usable in SQLServer 2005?Jeffry
Are you talking about .MDF datafile? If you are , have you tried to attach
the file? There are two system stored procedures as sp_detach_db,
sp_attach_db
"Jeffrey Kam" <Jeffrey Kam@.discussions.microsoft.com> wrote in message
news:913ABCEF-F02C-44A2-B9C0-881A7452D331@.microsoft.com...
>I have a data file in Beta 2 version, but now I've already uninstalled the
> beta version and installed a new Release Version of SQLServer 2005. Does
> anybody know how to convert the data file to be usable in SQLServer 2005?|||i tried to attach directly but it said it doesn't support beta version
"Uri Dimant" wrote:

> Jeffry
> Are you talking about .MDF datafile? If you are , have you tried to attac
h
> the file? There are two system stored procedures as sp_detach_db,
> sp_attach_db
>
>
>
> "Jeffrey Kam" <Jeffrey Kam@.discussions.microsoft.com> wrote in message
> news:913ABCEF-F02C-44A2-B9C0-881A7452D331@.microsoft.com...
>
>|||Yep, I see. Probably RESTORE command will not work as well.
Do you have still BETA CD to install it and transfer the data ?
Unfortanutally I have no idea (if above does not work) how to restore the
data
"Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
news:EE6DD8D9-FE2E-4566-903F-05F3748C2E7A@.microsoft.com...[vbcol=seagreen]
>i tried to attach directly but it said it doesn't support beta version
> "Uri Dimant" wrote:
>|||Thank you for your reply
Sorry, I still couldn't find it. that's why I want a solution without setup
another Beta 2. Does Microsoft provide such tools?
"Uri Dimant" wrote:

> Yep, I see. Probably RESTORE command will not work as well.
> Do you have still BETA CD to install it and transfer the data ?
>
> Unfortanutally I have no idea (if above does not work) how to restore the
> data
>
> "Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
> news:EE6DD8D9-FE2E-4566-903F-05F3748C2E7A@.microsoft.com...
>
>|||Hi
I am not aware of such tools , sorry
"Jeffrey Kam" <JeffreyKam@.discussions.microsoft.com> wrote in message
news:BF911B6B-A4F6-4740-8DBA-46C09EB9BF20@.microsoft.com...[vbcol=seagreen]
> Thank you for your reply
> Sorry, I still couldn't find it. that's why I want a solution without
> setup
> another Beta 2. Does Microsoft provide such tools?
> "Uri Dimant" wrote:
>

Best way to update/insert/delete in sqlserver database

Hello
I've passed the last days going around with xml, sqlxml, uppdategrams,
diffgrams, transactions, sp's, everything, I suppose, but still have
not a clear line of thoughts...
Im new in the info systems world.. I'm currently developing an
windows app in vb.net running over sqlserver 2000. Till now I was
using simple inserts, updates and deletes in db tables (not much so
far) but now that performance and data consistency issues are being
discussed, I was trying to understand the best way to pass data
to/from database.
Clearly I want to have the business logic in server side, being
executed by storedprocedures, but in large updates, inserts and
deletes I must pass many data and that it's a problem.
For an update I was doing something like this:
Try
loTransaction = lcnPlada.BeginTransaction()
lcmActualiza.Transaction = loTransaction
For Each loLinha In tdtActualizaHistorico.Rows
lcmActualiza.CommandText = "insert into
stetiquetahistorico (encomenda,produto,tamanho,cor,etiqueta,etiquetaem issor,dataemissaoetiqueta,etiquetaqtd,ficheiroemis sao)
" & _
"values (" & CType(loLinha(0), Integer) &
"," & CType(loLinha(1), Integer) & ",'" & loLinha(2).ToString & "'," &
CType(loLinha(3), Integer) & "," & CType(loLinha(4), Integer) & ",'" &
Environment.UserName & "','" & Now & "', " & CType(loLinha(5),
Integer) & "," & tnNumeroEmissao + 1 & ")"
lcmActualiza.ExecuteNonQuery()
Next
loTransaction.Commit()
Return True
end try
But have logic (a for each) inside a transaction its not a good idea,
right?
I've seen many different examples of adodb objects constructing a
stream with the xml statements that executes a sp and maps the table
columns to perform updates or inserts and then
adodb.command.commandstream = stream
adodb.command.execute
and in server side creates a sp that
sp_xml_preparedocument
...
insert...
sp_xml_removedocument
Sqlserver books online has an example of it that works correct in
northwind database but what about using sqlcommand? or
sqlxmlcommand?
Can I use a sqlxmlcommand to execute a stream that was written in
code, instead of using templates?
Is there other ways than sqlxml to perform this kind of tasks?
Anybody can help me, please?
Thanks in advance
sp_xml_preparedocument/OpenXML is a T-SQL feature. So it is independent of
what client you are using to connect to the database. Steps are:
1. Write your stored proc to do the logic
2. Use the normal way that your client requires to pass arguments and
execute the stored proc.
You only need the command stream object if you are using FOR XML to get XML
back from the server.
HTH
Michael
"?scar Martins" <subdueme@.hotmail.com> wrote in message
news:229f0a23.0410141120.1efff3b8@.posting.google.c om...
> Hello
> I've passed the last days going around with xml, sqlxml, uppdategrams,
> diffgrams, transactions, sp's, everything, I suppose, but still have
> not a clear line of thoughts...
> Im new in the info systems world.. I'm currently developing an
> windows app in vb.net running over sqlserver 2000. Till now I was
> using simple inserts, updates and deletes in db tables (not much so
> far) but now that performance and data consistency issues are being
> discussed, I was trying to understand the best way to pass data
> to/from database.
> Clearly I want to have the business logic in server side, being
> executed by storedprocedures, but in large updates, inserts and
> deletes I must pass many data and that it's a problem.
> For an update I was doing something like this:
> Try
> loTransaction = lcnPlada.BeginTransaction()
> lcmActualiza.Transaction = loTransaction
> For Each loLinha In tdtActualizaHistorico.Rows
> lcmActualiza.CommandText = "insert into
> stetiquetahistorico
> (encomenda,produto,tamanho,cor,etiqueta,etiquetaem issor,dataemissaoetiqueta,etiquetaqtd,ficheiroemis sao)
> " & _
> "values (" & CType(loLinha(0), Integer) &
> "," & CType(loLinha(1), Integer) & ",'" & loLinha(2).ToString & "'," &
> CType(loLinha(3), Integer) & "," & CType(loLinha(4), Integer) & ",'" &
> Environment.UserName & "','" & Now & "', " & CType(loLinha(5),
> Integer) & "," & tnNumeroEmissao + 1 & ")"
> lcmActualiza.ExecuteNonQuery()
> Next
> loTransaction.Commit()
> Return True
> end try
> But have logic (a for each) inside a transaction its not a good idea,
> right?
>
> I've seen many different examples of adodb objects constructing a
> stream with the xml statements that executes a sp and maps the table
> columns to perform updates or inserts and then
> adodb.command.commandstream = stream
> adodb.command.execute
> and in server side creates a sp that
> sp_xml_preparedocument
> ...
> insert...
> sp_xml_removedocument
> Sqlserver books online has an example of it that works correct in
> northwind database but what about using sqlcommand? or
> sqlxmlcommand?
> Can I use a sqlxmlcommand to execute a stream that was written in
> code, instead of using templates?
> Is there other ways than sqlxml to perform this kind of tasks?
> Anybody can help me, please?
>
> Thanks in advance

best way to optimize certain tables

I have a SqlServer 2000 running 7 databases. One in particular is slower
than the rest specificaly on certain tables. It seems the problem comes
from the volume of data, but I don't think 3000 lines can be considered a
big table. I have indexes on the principal keys, but it did not help.
thank you
Hi,
Identify the stored procedures , Queries taking more time / CPU. Use the
profiler tuning templace to identify this. After that save the
file as a workload table or file. Use the workload file as the input file
for index tning wizard.
I feel that this slow responce is due to the lack of proper indexes.
You could also use the Execution plans to tune your queries.
Thanks
Hari
SQL Server MVP
"Fernand St-Georges" <fernand.st-georges@.videotron.ca> wrote in message
news:Ethwe.79344$Yu4.927653@.wagner.videotron.net.. .
>I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
>
|||Tables are not slow. They are just data containers.
Queries can be slow, if they are not written properly, or when the
underlying tables are not properly indexed. You could follow Hari's
advice to analyse where and why they are slow.
You could also give the Index Tuning Wizard a try.
HTH,
Gert-Jan
Fernand St-Georges wrote:
> I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
|||Check the queries and use index tuning wizard.
Are you re-indexing the tables frequently?
Thanks
Ravi
"Fernand St-Georges" wrote:

> I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
>
>

best way to optimize certain tables

I have a SqlServer 2000 running 7 databases. One in particular is slower
than the rest specificaly on certain tables. It seems the problem comes
from the volume of data, but I don't think 3000 lines can be considered a
big table. I have indexes on the principal keys, but it did not help.

thank youFernand St-Georges (fernand.st-georges@.videotron.ca) writes:
> I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.

3000 rows is indeed a fairly small table. But a weird enough query and
make even that table slow to work with.

You need to find out more of what is going on. One way is to run Profiler,
and capture the SP:StmtCompleted, SQL:StatementCompleted, SP:Completed
and RPC:Completed events with some good filter on Duration, so you can
locate the slow queries. If there are any slow queries. The problem could
be blocking as well.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, data types, etc. in
your schema are. Sample data is also a good idea, along with clear
specifications. It is very hard to debug code when you do not let us
see it.

best way to optimize certain tables

I have a SqlServer 2000 running 7 databases. One in particular is slower
than the rest specificaly on certain tables. It seems the problem comes
from the volume of data, but I don't think 3000 lines can be considered a
big table. I have indexes on the principal keys, but it did not help.
thank youHi,
Identify the stored procedures , Queries taking more time / CPU. Use the
profiler tuning templace to identify this. After that save the
file as a workload table or file. Use the workload file as the input file
for index tning wizard.
I feel that this slow responce is due to the lack of proper indexes.
You could also use the Execution plans to tune your queries.
Thanks
Hari
SQL Server MVP
"Fernand St-Georges" <fernand.st-georges@.videotron.ca> wrote in message
news:Ethwe.79344$Yu4.927653@.wagner.videotron.net...
>I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
>|||Tables are not slow. They are just data containers.
Queries can be slow, if they are not written properly, or when the
underlying tables are not properly indexed. You could follow Hari's
advice to analyse where and why they are slow.
You could also give the Index Tuning Wizard a try.
HTH,
Gert-Jan
Fernand St-Georges wrote:
> I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you|||Check the queries and use index tuning wizard.
Are you re-indexing the tables frequently?
--
Thanks
Ravi
"Fernand St-Georges" wrote:
> I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
>
>

best way to optimize certain tables

I have a SqlServer 2000 running 7 databases. One in particular is slower
than the rest specificaly on certain tables. It seems the problem comes
from the volume of data, but I don't think 3000 lines can be considered a
big table. I have indexes on the principal keys, but it did not help.
thank youHi,
Identify the stored procedures , Queries taking more time / CPU. Use the
profiler tuning templace to identify this. After that save the
file as a workload table or file. Use the workload file as the input file
for index tning wizard.
I feel that this slow responce is due to the lack of proper indexes.
You could also use the Execution plans to tune your queries.
Thanks
Hari
SQL Server MVP
"Fernand St-Georges" <fernand.st-georges@.videotron.ca> wrote in message
news:Ethwe.79344$Yu4.927653@.wagner.videotron.net...
>I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
>|||Tables are not slow. They are just data containers.
Queries can be slow, if they are not written properly, or when the
underlying tables are not properly indexed. You could follow Hari's
advice to analyse where and why they are slow.
You could also give the Index Tuning Wizard a try.
HTH,
Gert-Jan
Fernand St-Georges wrote:
> I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you|||Check the queries and use index tuning wizard.
Are you re-indexing the tables frequently?
Thanks
Ravi
"Fernand St-Georges" wrote:

> I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
>
>

Best way to keep track of SQL server changes...!

What would be the best practice to follow to keep track of MS SQL
server changes... Stroed procs, tables, views, triggers, indexes, DTS
and also jobs ect...
I am not quite sure how Source safe works with sql server. Any other
way to do this... Even if its manual work, its okey.. I would
appreciate if any of the DBA's let me know how they are facing this
issue...
Thanks in advance...
Hi,
Have you thought about server side tracing?
If you do not wish to do the above and is ready to spend some money, then
there are few third-party tools available in the market, For ex: Red-gate.
Thanks
Yogish
|||check out www.dbghost.com for SQL Server database change management with
source control intergration.
"SQLDBA" wrote:

> What would be the best practice to follow to keep track of MS SQL
> server changes... Stroed procs, tables, views, triggers, indexes, DTS
> and also jobs ect...
> I am not quite sure how Source safe works with sql server. Any other
> way to do this... Even if its manual work, its okey.. I would
> appreciate if any of the DBA's let me know how they are facing this
> issue...
> Thanks in advance...
>

Best way to keep track of SQL server changes...!

What would be the best practice to follow to keep track of MS SQL
server changes... Stroed procs, tables, views, triggers, indexes, DTS
and also jobs ect...
I am not quite sure how Source safe works with sql server. Any other
way to do this... Even if its manual work, its okey.. I would
appreciate if any of the DBA's let me know how they are facing this
issue...
Thanks in advance...Hi,
Have you thought about server side tracing?
If you do not wish to do the above and is ready to spend some money, then
there are few third-party tools available in the market, For ex: Red-gate.
Thanks
Yogish|||check out www.dbghost.com for SQL Server database change management with
source control intergration.
"SQLDBA" wrote:

> What would be the best practice to follow to keep track of MS SQL
> server changes... Stroed procs, tables, views, triggers, indexes, DTS
> and also jobs ect...
> I am not quite sure how Source safe works with sql server. Any other
> way to do this... Even if its manual work, its okey.. I would
> appreciate if any of the DBA's let me know how they are facing this
> issue...
> Thanks in advance...
>

Best way to keep track of SQL Server Changes

What would be the best practice to follow to keep track of MS SQL
server changes... Stroed procs, tables, views, triggers, indexes, DTS
and also jobs ect...

I am not quite sure how Source safe works with sql server. Any other
way to do this... Even if its manual work, its okey.. I would
appreciate if any of the DBA's let me know how they are facing this
issue...

Thanks in advance..."SQLDBA" <pg.242w@.gmail.com> wrote in message
news:1104953120.142642.99410@.z14g2000cwz.googlegro ups.com...
> What would be the best practice to follow to keep track of MS SQL
> server changes... Stroed procs, tables, views, triggers, indexes, DTS
> and also jobs ect...
> I am not quite sure how Source safe works with sql server. Any other
> way to do this... Even if its manual work, its okey.. I would
> appreciate if any of the DBA's let me know how they are facing this
> issue...
> Thanks in advance...

There's lot of information on the web - Google 'sql 2000 source control' or
something similar to find more information. You might also want to check out
the thread in this group from yesterday called 'Backing up design changes',
as well as this approach from Erland:

http://www.abaris.se/abaperls/index.html

To get started quickly, you can script your objects to files using
Enterprise Manager, check them all in to VSS, then start using source
control for all changes. You'll need to do some basic work on source control
processes, but there's lot of stuff on the web, and you may already have
something in your organization that you can re-use.

It's also very useful to have some sort of comparison tool (I've used Red
Gate's SQL Compare before) to check the differences between databases, and
synchronize them as needed.

DTS is a bit more problematic, because packages are binary objects, not text
files, but DTS does support multiple package versions anyway, so you might
just decide to keep the last 5 versions in a package or whatever.

Simon|||Thank you very much... We do have VSS but my knowledge in VSS is
limited. So I would appreciate if you could give me a drill down on how
I can set it up. Is there any way I can link these scripts to SQL
Server objects so that everytime when someone try to make any changes
to these scripts, it needs to be checked out to get modified? Because I
need to enforce a method among the developers to follow...!|||SQLDBA (pg.242w@.gmail.com) writes:
> Thank you very much... We do have VSS but my knowledge in VSS is
> limited. So I would appreciate if you could give me a drill down on how
> I can set it up. Is there any way I can link these scripts to SQL
> Server objects so that everytime when someone try to make any changes
> to these scripts, it needs to be checked out to get modified? Because I
> need to enforce a method among the developers to follow...!

There might be means to in Visual Studio.

But in my opinion, that's flawed. Checking out - and in - should be
a concious decision, and the source for the check-in should be a file,
not an object in a database.

That's the core of configuration management: if you need to change a
file, you go the version-control system and check it out, do your
change, and then check it in. If the change is not in the version-
control system, it does simply not exists. All builds and deployments
are made from the version-control system.

Of course, if there is only one development database, this policy may
be somewhat difficult to enforce, not the least if people use tools
like Query Analyzer where it's easier to load a stored procedure to
the database than saving it to disk.

In our shop there are an unknown number of development databases, so it
becomes quite apparent that there must be a central clearinghouse for
the code, and that is is SourceSafe.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thank you all for your input. In my situation, I just need to enforce
some good practice methodology among the developers. We already have
some third party tool (Redgate SQL compare) that does a wonderful job
in migrating changes among different databases.. This is just to keep
track of who is changing what and to keep the process going without any
flaws... So anyone has any suggestions to a situation like this?
Thanks again..!

Best way to implement "warm" standby? - considering log shipping

Hi Larry,
Log Shipping is the ultimate solution if you are on SQL
Server Enterprise Edition. Follow these Resources..
Log Shipping in SQL Server 2000 - Part 1
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/sql/deploy/prodspecs/logship1.asp
Log Shipping in SQL Server 2000 - Part 2
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/sql/deploy/prodspecs/logship1.asp
How to Perform SQL Server Log Shipping
http://www.sql-server-
performance.com/sql_server_log_shipping.asp
HTH
THIRUMAL REDDY MARAM
Sys Amin / SQL DBA

quote:

---

>--Original Message--
>I have TWO networked servers; one production, and one

---

backup. I want to be

quote:

---

>able to use the backup in case of a production server

---

failure. The loss of

quote:

---

>a "little" data is acceptable in case of failure. Log

---

Shipping looks like

quote:

---

>the easiest but there seems to be a lot of warnings about

---

(1) having a

quote:

---

>monitor server, and (2) having this server NOT be either

---

the production

quote:

---

>server nor the backup. I only have two servers so I

---

can't do this.

quote:

---

>Is Log Shipping the best solution? Also--and this might

---

affect your

quote:

---

>response--it is possible that the backup system might

---

not be available 100%

quote:

---

>of the time. I bring this up because I don't know what

---

will happen if the

quote:

---

>production system wants to ship a log, and the backup

---

computer isn't

quote:

---

>available to accept it. (')
>Any help, recommendations?
>TIA,
>Larry Woods
>
>.
>

---

Thanks, Thirumal,
I've printed off all three articles and I will study them.
Larry
"Thirumal" <treddym@.hotmail.nospam.com> wrote in message
news:129a01c3df61$ab5c71d0$a601280a@.phx.gbl...[QUOTE]
> Hi Larry,
> Log Shipping is the ultimate solution if you are on SQL
> Server Enterprise Edition. Follow these Resources..
> Log Shipping in SQL Server 2000 - Part 1
> http://www.microsoft.com/technet/treeview/default.asp?
> url=/technet/prodtechnol/sql/deploy/prodspecs/logship1.asp
> Log Shipping in SQL Server 2000 - Part 2
> http://www.microsoft.com/technet/treeview/default.asp?
> url=/technet/prodtechnol/sql/deploy/prodspecs/logship1.asp
> How to Perform SQL Server Log Shipping
> http://www.sql-server-
> performance.com/sql_server_log_shipping.asp
> HTH
> --
> THIRUMAL REDDY MARAM
> Sys Amin / SQL DBA
> backup. I want to be
> failure. The loss of
> Shipping looks like
> (1) having a
> the production
> can't do this.
> affect your
> not be available 100%
> will happen if the
> computer isn't

Best way to get TOP 10 CPU intensive SQL

I run a shared hosting server where multiple people share a single SQL
server (each of them have their own data base). I need a way to monitor to
find out what % of the resources each user is taking as we don't want any
one person abusing the system. What is the best way to do this
Jay
Jay
Run SQL Server Profiler tool.
"Jay Janarthanan" <jay@.objectcube.com> wrote in message
news:e4AaSxinEHA.648@.tk2msftngp13.phx.gbl...
> I run a shared hosting server where multiple people share a single SQL
> server (each of them have their own data base). I need a way to monitor to
> find out what % of the resources each user is taking as we don't want any
> one person abusing the system. What is the best way to do this
> Jay
>
|||See if this helps:
Identifying SQL Server Perfromance Issues Using Profiler
http://vyaskn.tripod.com/analyzing_profiler_output.htm
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Jay Janarthanan" <jay@.objectcube.com> wrote in message
news:e4AaSxinEHA.648@.tk2msftngp13.phx.gbl...
> I run a shared hosting server where multiple people share a single SQL
> server (each of them have their own data base). I need a way to monitor to
> find out what % of the resources each user is taking as we don't want any
> one person abusing the system. What is the best way to do this
> Jay
>

best way to delete the reporting services jobs in sqlserver

I have six thousand reporting services jobs in sqlserver, which were
scheduled to run only once and their execution date is older than a month.
how do I know which of the jobs are useful out of these 6000.
Can I write a job, to purge the reporting services jobs older than a month
and schedule it to run every week, basically how do I manage these ever
growing jobs ?
Thanks in advance..GAis it okay to delete the subscriptions like below '
delete from reportserver..subscriptions
WHERE ModifiedDate < dateadd(day, -7, getdate()) AND Description LIKE 'SRS%'
TIA
"DallasBlue" wrote:
> I have six thousand reporting services jobs in sqlserver, which were
> scheduled to run only once and their execution date is older than a month.
> how do I know which of the jobs are useful out of these 6000.
> Can I write a job, to purge the reporting services jobs older than a month
> and schedule it to run every week, basically how do I manage these ever
> growing jobs ?
>
> Thanks in advance..GA
>|||I have deleted subscriptions using this method. There are cascading deletes
when to remove the related records in ReportSchedule and Schedule tables.
Though, bulk deleting a lot of subscriptions at the same time might not work
with that statement. I know for me I've gotten timeouts when trying a direct
delete. So instead, I create a memory table (DECLARE @.x TABLE...) and put in
all the SubscriptionID for the ones I want to delete. Then I delete from the
Subscription table using a join to the memory table. I know it might seem
strange to do it that way, but because of the way the tables are indexed, it
works.
Once you the records are deleted from the tables, the Reporting Service will
automatically delete the actual SQL Agent jobs when it does its maintenance,
I'm not sure of the frequency that it does that, but at minimum its once a
day.
Carmine
"DallasBlue" wrote:
> is it okay to delete the subscriptions like below '
> delete from reportserver..subscriptions
> WHERE ModifiedDate < dateadd(day, -7, getdate()) AND Description LIKE 'SRS%'
> TIA
> "DallasBlue" wrote:
> > I have six thousand reporting services jobs in sqlserver, which were
> > scheduled to run only once and their execution date is older than a month.
> > how do I know which of the jobs are useful out of these 6000.
> > Can I write a job, to purge the reporting services jobs older than a month
> > and schedule it to run every week, basically how do I manage these ever
> > growing jobs ?
> >
> >
> > Thanks in advance..GA
> >
> >