Developing, building, and testing. How do it the best? Learning from the world leader - Microsoft
I'm very interested in how the developing/build/testing workflow @. Microsoft looks like. I think Microsoft as world leader in software developing business must have a very good workflow. Does anyone know how the development flow @. Microsoft looks like?
I'm also interested in the workflow in your company perhaps the workflow in your company better then @. Microsoft? What do you think about test driven development?
Regards,
GicioBeen reading anything about security issues lately?
Can you say Monopoly?
Do a google for developemnt life cycles...|||test-driven? man, unless you have an army of very good developers who can read between the lines of each other, - you may find yourself doomed, as well as the project.
"@. Microsoft" the concept is very simple: check for the vision out on the market, crank something similar or close to it up, get it out the door, and then throw a bunch of fixers at it with service packs as deliverables (one fixes something and breaks something else, so that the next one can fix it :) )|||Check out sun's developers site:
link (http://developer.sun.com/)
I have found that microsoft has lagged behind sun on best practices. However, basically since the adoption of .Net, ms has been changing and adding key personnel in this area.|||Which workflow use companies that are on the CMM levels 3, 4, 5 ?
(http://www.sei.cmu.edu/cmm/)
regards,
gicio
Saturday, February 25, 2012
Developing with Enterprise tools, deploying without them
I have designed my database using Sql 2000 Developer Edition, but I need to apply that design to MSDE. I can run the script on a database using MSDE through Enterprise manager on my machine and, using Enterprise manager again, back the database up. How do I restore that backup to a MSDE database on another machine without Enterprise tools?
In other words, I need to install MSDE on another machine and restore a backed up database design to it, without Enterprise tools on the host machine.
Also: If I want to use exactly the same database I have developed using Enterprise tools packaged with Sql 2000 Developer Edition, how may I back 'that' database up so that it may be restored to a MSDE database or replicate the database in question to an MSDE client?
Thank you,
John SpurlinYou can execute a script or query using OSQL from the command line. See the follwoing MSDN article for more details:
osql Utility
Hope this helps
Regards
Wayne Phipps
Developing WAP using ASP.NET and Web Services
Hi all,
I would like to develop WAP using ASP.NET which can connect to the Database( MS SQL Server ). Is it possible to do it? I try to find the tutorial but I cannot find it.
Another thing I want to ask is can I connect the WAP to the web services that I create using ASP.NET, anyone can tell me how to do it.
Thanks, Regards.
REDWAP is something that is sent to and displayed on the client. ASP.NET and Web Services are server side technologies. You can certainly have your ASP.NET application call out to a Web service, and then send the results to your WAP device.
Developing Thirty Party Controls for RS2005
I want to develop a new report control or extend the existing textbox control in RS2005. Is there any documentation or examples on how to do this?
Thanks,
Check out Teo Lachev's recent MSDN article on the CustomReportItem feature of RS 2005: http://msdn.microsoft.com/msdnmag/issues/06/10/SQLServer2005/default.aspx
-- Robert
Developing the clever backup strategy
Hi there...
I've been reading around in the BOL to figure out what backup strategy is th
e
"best" available. The database I want to backup, is ~4.5 after a shrink, but
it
of course grows after a while. Same with the log.
The database runs in "full recovery" mode currently, and it is being used du
ring
a normal workday, by around 15 people. What backup setup is the recommended
in
this situation?
I've tried setting it up to backup the database every 4 hours, and the log e
very
30 minutes. This generates a /lot/ of *.trn files, is there anyway to
"consolidate" those after a day? Secondly, when I do a database backup every
24
hours, does that mean that I can then afterward safely truncate the log (I l
ike
keeping things neat
? What do I do with the *.bak and *.trn when they are
over
two days old?
I doubt, therefore I might be.I'd suggest a good, thorough read through of books on line to make sure you
understand things like truncating the logs, full recovery more, simple
recovery mode, etc.
Truncating the logs should probably never be done which is why I suggest thi
s.
burt_king@.yahoo.com
"Kim Noer" wrote:
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is
the
> "best" available. The database I want to backup, is ~4.5 after a shrink, b
ut it
> of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used
during
> a normal workday, by around 15 people. What backup setup is the recommende
d in
> this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log
every
> 30 minutes. This generates a /lot/ of *.trn files, is there anyway to
> "consolidate" those after a day? Secondly, when I do a database backup eve
ry 24
> hours, does that mean that I can then afterward safely truncate the log (I
like
> keeping things neat? What do I do with the *.bak and *.trn when they ar
e over
> two days old?
> --
> I doubt, therefore I might be.
>|||I definitely agree. Also, be restrictive using shrink, for more info, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"burt_king" <burt_king@.yahoo.com> wrote in message
news:193B7308-3D54-426E-AF7A-B9983D509983@.microsoft.com...[vbcol=seagreen]
> I'd suggest a good, thorough read through of books on line to make sure yo
u
> understand things like truncating the logs, full recovery more, simple
> recovery mode, etc.
> Truncating the logs should probably never be done which is why I suggest t
his.
>
> --
> burt_king@.yahoo.com
>
> "Kim Noer" wrote:
>|||Usually in a smaller environment like you describe I reccomend a daily full
backup and then differential backups throughout the day. With this scenario
you can put the database in simple recovery mode and not have to worry about
log file growth. I have seen too many environments where they left the
databases in Full Recovery (default) and never back up the logs. A couple
weeks go by and the database is refusing transactions because the disk is
full.
I truncate and shrink the logs every night to make sure it gets done. One
big Insert or something else can throw your log files out of whack. With
this you should make sure your minimum log file is big enough that it does
not have to grow signifigantly during a normal work day.
When you say your DB is 4.5G (I assume G) after the shrink, how big is it
before the shrink? If your database files are shrinking signifigantly
(>20%) every night you need to look at your clustered indexes and fill
factors to make sure there is enough room that the database is not having to
auto grow throughout the day. Also, if you have not done reindexed in a
while, you should look at doing that - see DBCC Reindex (note that this
should be done when the database is not being accessed).
"Kim Noer" <kn@.nospam.dk> wrote in message
news:%231ouK%2327FHA.2816@.tk2msftngp13.phx.gbl...
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is
> the "best" available. The database I want to backup, is ~4.5 after a
> shrink, but it of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used
> during a normal workday, by around 15 people. What backup setup is the
> recommended in this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log
> every 30 minutes. This generates a /lot/ of *.trn files, is there anyway
> to "consolidate" those after a day? Secondly, when I do a database backup
> every 24 hours, does that mean that I can then afterward safely truncate
> the log (I like keeping things neat? What do I do with the *.bak and
> *.trn when they are over two days old?
> --
> I doubt, therefore I might be.|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote in message news:uHbwqP37FHA.1140@.tk2msftngp13.phx.gbl
> I definitely agree. Also, be restrictive using shrink, for more info,
> see http://www.karaszi.com/SQLServer/info_dont_shrink.asp
I've read your excellent guide, and I think I actually more now than before
.
Anyway. Currently the database runs in "full recovery" mode. Then I did a
complete backup of the database, and then I tried a dbcc loginfo('database')
Now, according to your guide, status 2 means the VLF is in use. The result i
s
this -
2 253952 8192 65770 0 64 0
2 253952 262144 65769 0 64 0
2 253952 516096 65768 0 128 0
2 278528 770048 65771 0 64 0
2 262144 1048576 65772 0 128 40875000000042200043
...
And this continues all the way to row 308 (your guide tells me I should set
the
allocated size way above the current) -
2 27000832 2188771328 65773 2 64 65760000004588300008
2 27000832 2215772160 65766 0 64 65760000004588300008
As you might be able to see, row 308 have the status 2. Doesn't this mean th
at
this logfile will never go below 2.06GB unless I truncate it manually? Secon
dly,
what about the VLF's below, since they are unused will this cause SQL Server
to
reuse the VLF, or will it proceed from CreateLSN 65760000004588300008?
I doubt, therefore I might be.|||"Kim Noer" <kn@.nospam.dk> wrote in message
news:OZD%23gFE8FHA.1140@.tk2msftngp13.phx.gbl
> Secondly, what about the VLF's below, since they are
> unused will this cause SQL Server to reuse the VLF, or will it
> proceed from CreateLSN 65760000004588300008?
Nevermind, I decided to use your guide as test, that is, create a table, the
n
insert a lot of records, which showed me that SQL Server reuses unused VLF,
even
when they are "before" used VLF's.
I doubt, therefore I might be.
I've been reading around in the BOL to figure out what backup strategy is th
e
"best" available. The database I want to backup, is ~4.5 after a shrink, but
it
of course grows after a while. Same with the log.
The database runs in "full recovery" mode currently, and it is being used du
ring
a normal workday, by around 15 people. What backup setup is the recommended
in
this situation?
I've tried setting it up to backup the database every 4 hours, and the log e
very
30 minutes. This generates a /lot/ of *.trn files, is there anyway to
"consolidate" those after a day? Secondly, when I do a database backup every
24
hours, does that mean that I can then afterward safely truncate the log (I l
ike
keeping things neat
? What do I do with the *.bak and *.trn when they are over
two days old?
I doubt, therefore I might be.I'd suggest a good, thorough read through of books on line to make sure you
understand things like truncating the logs, full recovery more, simple
recovery mode, etc.
Truncating the logs should probably never be done which is why I suggest thi
s.
burt_king@.yahoo.com
"Kim Noer" wrote:
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is
the
> "best" available. The database I want to backup, is ~4.5 after a shrink, b
ut it
> of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used
during
> a normal workday, by around 15 people. What backup setup is the recommende
d in
> this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log
every
> 30 minutes. This generates a /lot/ of *.trn files, is there anyway to
> "consolidate" those after a day? Secondly, when I do a database backup eve
ry 24
> hours, does that mean that I can then afterward safely truncate the log (I
like
> keeping things neat
? What do I do with the *.bak and *.trn when they are over
> two days old?
> --
> I doubt, therefore I might be.
>|||I definitely agree. Also, be restrictive using shrink, for more info, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"burt_king" <burt_king@.yahoo.com> wrote in message
news:193B7308-3D54-426E-AF7A-B9983D509983@.microsoft.com...[vbcol=seagreen]
> I'd suggest a good, thorough read through of books on line to make sure yo
u
> understand things like truncating the logs, full recovery more, simple
> recovery mode, etc.
> Truncating the logs should probably never be done which is why I suggest t
his.
>
> --
> burt_king@.yahoo.com
>
> "Kim Noer" wrote:
>|||Usually in a smaller environment like you describe I reccomend a daily full
backup and then differential backups throughout the day. With this scenario
you can put the database in simple recovery mode and not have to worry about
log file growth. I have seen too many environments where they left the
databases in Full Recovery (default) and never back up the logs. A couple
weeks go by and the database is refusing transactions because the disk is
full.
I truncate and shrink the logs every night to make sure it gets done. One
big Insert or something else can throw your log files out of whack. With
this you should make sure your minimum log file is big enough that it does
not have to grow signifigantly during a normal work day.
When you say your DB is 4.5G (I assume G) after the shrink, how big is it
before the shrink? If your database files are shrinking signifigantly
(>20%) every night you need to look at your clustered indexes and fill
factors to make sure there is enough room that the database is not having to
auto grow throughout the day. Also, if you have not done reindexed in a
while, you should look at doing that - see DBCC Reindex (note that this
should be done when the database is not being accessed).
"Kim Noer" <kn@.nospam.dk> wrote in message
news:%231ouK%2327FHA.2816@.tk2msftngp13.phx.gbl...
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is
> the "best" available. The database I want to backup, is ~4.5 after a
> shrink, but it of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used
> during a normal workday, by around 15 people. What backup setup is the
> recommended in this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log
> every 30 minutes. This generates a /lot/ of *.trn files, is there anyway
> to "consolidate" those after a day? Secondly, when I do a database backup
> every 24 hours, does that mean that I can then afterward safely truncate
> the log (I like keeping things neat
? What do I do with the *.bak and> *.trn when they are over two days old?
> --
> I doubt, therefore I might be.|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote in message news:uHbwqP37FHA.1140@.tk2msftngp13.phx.gbl
> I definitely agree. Also, be restrictive using shrink, for more info,
> see http://www.karaszi.com/SQLServer/info_dont_shrink.asp
I've read your excellent guide, and I think I actually more now than before
.Anyway. Currently the database runs in "full recovery" mode. Then I did a
complete backup of the database, and then I tried a dbcc loginfo('database')
Now, according to your guide, status 2 means the VLF is in use. The result i
s
this -
2 253952 8192 65770 0 64 0
2 253952 262144 65769 0 64 0
2 253952 516096 65768 0 128 0
2 278528 770048 65771 0 64 0
2 262144 1048576 65772 0 128 40875000000042200043
...
And this continues all the way to row 308 (your guide tells me I should set
the
allocated size way above the current) -
2 27000832 2188771328 65773 2 64 65760000004588300008
2 27000832 2215772160 65766 0 64 65760000004588300008
As you might be able to see, row 308 have the status 2. Doesn't this mean th
at
this logfile will never go below 2.06GB unless I truncate it manually? Secon
dly,
what about the VLF's below, since they are unused will this cause SQL Server
to
reuse the VLF, or will it proceed from CreateLSN 65760000004588300008?
I doubt, therefore I might be.|||"Kim Noer" <kn@.nospam.dk> wrote in message
news:OZD%23gFE8FHA.1140@.tk2msftngp13.phx.gbl
> Secondly, what about the VLF's below, since they are
> unused will this cause SQL Server to reuse the VLF, or will it
> proceed from CreateLSN 65760000004588300008?
Nevermind, I decided to use your guide as test, that is, create a table, the
n
insert a lot of records, which showed me that SQL Server reuses unused VLF,
even
when they are "before" used VLF's.
I doubt, therefore I might be.
Developing the clever backup strategy
Hi there...
I've been reading around in the BOL to figure out what backup strategy is the
"best" available. The database I want to backup, is ~4.5 after a shrink, but it
of course grows after a while. Same with the log.
The database runs in "full recovery" mode currently, and it is being used during
a normal workday, by around 15 people. What backup setup is the recommended in
this situation?
I've tried setting it up to backup the database every 4 hours, and the log every
30 minutes. This generates a /lot/ of *.trn files, is there anyway to
"consolidate" those after a day? Secondly, when I do a database backup every 24
hours, does that mean that I can then afterward safely truncate the log (I like
keeping things neat? What do I do with the *.bak and *.trn when they are over
two days old?
I doubt, therefore I might be.
I'd suggest a good, thorough read through of books on line to make sure you
understand things like truncating the logs, full recovery more, simple
recovery mode, etc.
Truncating the logs should probably never be done which is why I suggest this.
burt_king@.yahoo.com
"Kim Noer" wrote:
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is the
> "best" available. The database I want to backup, is ~4.5 after a shrink, but it
> of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used during
> a normal workday, by around 15 people. What backup setup is the recommended in
> this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log every
> 30 minutes. This generates a /lot/ of *.trn files, is there anyway to
> "consolidate" those after a day? Secondly, when I do a database backup every 24
> hours, does that mean that I can then afterward safely truncate the log (I like
> keeping things neat? What do I do with the *.bak and *.trn when they are over
> two days old?
> --
> I doubt, therefore I might be.
>
|||I definitely agree. Also, be restrictive using shrink, for more info, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"burt_king" <burt_king@.yahoo.com> wrote in message
news:193B7308-3D54-426E-AF7A-B9983D509983@.microsoft.com...[vbcol=seagreen]
> I'd suggest a good, thorough read through of books on line to make sure you
> understand things like truncating the logs, full recovery more, simple
> recovery mode, etc.
> Truncating the logs should probably never be done which is why I suggest this.
>
> --
> burt_king@.yahoo.com
>
> "Kim Noer" wrote:
|||Usually in a smaller environment like you describe I reccomend a daily full
backup and then differential backups throughout the day. With this scenario
you can put the database in simple recovery mode and not have to worry about
log file growth. I have seen too many environments where they left the
databases in Full Recovery (default) and never back up the logs. A couple
weeks go by and the database is refusing transactions because the disk is
full.
I truncate and shrink the logs every night to make sure it gets done. One
big Insert or something else can throw your log files out of whack. With
this you should make sure your minimum log file is big enough that it does
not have to grow signifigantly during a normal work day.
When you say your DB is 4.5G (I assume G) after the shrink, how big is it
before the shrink? If your database files are shrinking signifigantly
(>20%) every night you need to look at your clustered indexes and fill
factors to make sure there is enough room that the database is not having to
auto grow throughout the day. Also, if you have not done reindexed in a
while, you should look at doing that - see DBCC Reindex (note that this
should be done when the database is not being accessed).
"Kim Noer" <kn@.nospam.dk> wrote in message
news:%231ouK%2327FHA.2816@.tk2msftngp13.phx.gbl...
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is
> the "best" available. The database I want to backup, is ~4.5 after a
> shrink, but it of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used
> during a normal workday, by around 15 people. What backup setup is the
> recommended in this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log
> every 30 minutes. This generates a /lot/ of *.trn files, is there anyway
> to "consolidate" those after a day? Secondly, when I do a database backup
> every 24 hours, does that mean that I can then afterward safely truncate
> the log (I like keeping things neat? What do I do with the *.bak and
> *.trn when they are over two days old?
> --
> I doubt, therefore I might be.
|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote in message news:uHbwqP37FHA.1140@.tk2msftngp13.phx.gbl
> I definitely agree. Also, be restrictive using shrink, for more info,
> see http://www.karaszi.com/SQLServer/info_dont_shrink.asp
I've read your excellent guide, and I think I actually more now than before.
Anyway. Currently the database runs in "full recovery" mode. Then I did a
complete backup of the database, and then I tried a dbcc loginfo('database')
Now, according to your guide, status 2 means the VLF is in use. The result is
this -
2 253952 8192 65770 0 64 0
2 253952 262144 65769 0 64 0
2 253952 516096 65768 0 128 0
2 278528 770048 65771 0 64 0
2 262144 1048576 65772 0 128 40875000000042200043
...
And this continues all the way to row 308 (your guide tells me I should set the
allocated size way above the current) -
2 27000832 2188771328 65773 2 64 65760000004588300008
2 27000832 2215772160 65766 0 64 65760000004588300008
As you might be able to see, row 308 have the status 2. Doesn't this mean that
this logfile will never go below 2.06GB unless I truncate it manually? Secondly,
what about the VLF's below, since they are unused will this cause SQL Server to
reuse the VLF, or will it proceed from CreateLSN 65760000004588300008?
I doubt, therefore I might be.
|||"Kim Noer" <kn@.nospam.dk> wrote in message
news:OZD%23gFE8FHA.1140@.tk2msftngp13.phx.gbl
> Secondly, what about the VLF's below, since they are
> unused will this cause SQL Server to reuse the VLF, or will it
> proceed from CreateLSN 65760000004588300008?
Nevermind, I decided to use your guide as test, that is, create a table, then
insert a lot of records, which showed me that SQL Server reuses unused VLF, even
when they are "before" used VLF's.
I doubt, therefore I might be.
I've been reading around in the BOL to figure out what backup strategy is the
"best" available. The database I want to backup, is ~4.5 after a shrink, but it
of course grows after a while. Same with the log.
The database runs in "full recovery" mode currently, and it is being used during
a normal workday, by around 15 people. What backup setup is the recommended in
this situation?
I've tried setting it up to backup the database every 4 hours, and the log every
30 minutes. This generates a /lot/ of *.trn files, is there anyway to
"consolidate" those after a day? Secondly, when I do a database backup every 24
hours, does that mean that I can then afterward safely truncate the log (I like
keeping things neat
? What do I do with the *.bak and *.trn when they are overtwo days old?
I doubt, therefore I might be.
I'd suggest a good, thorough read through of books on line to make sure you
understand things like truncating the logs, full recovery more, simple
recovery mode, etc.
Truncating the logs should probably never be done which is why I suggest this.
burt_king@.yahoo.com
"Kim Noer" wrote:
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is the
> "best" available. The database I want to backup, is ~4.5 after a shrink, but it
> of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used during
> a normal workday, by around 15 people. What backup setup is the recommended in
> this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log every
> 30 minutes. This generates a /lot/ of *.trn files, is there anyway to
> "consolidate" those after a day? Secondly, when I do a database backup every 24
> hours, does that mean that I can then afterward safely truncate the log (I like
> keeping things neat
? What do I do with the *.bak and *.trn when they are over> two days old?
> --
> I doubt, therefore I might be.
>
|||I definitely agree. Also, be restrictive using shrink, for more info, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"burt_king" <burt_king@.yahoo.com> wrote in message
news:193B7308-3D54-426E-AF7A-B9983D509983@.microsoft.com...[vbcol=seagreen]
> I'd suggest a good, thorough read through of books on line to make sure you
> understand things like truncating the logs, full recovery more, simple
> recovery mode, etc.
> Truncating the logs should probably never be done which is why I suggest this.
>
> --
> burt_king@.yahoo.com
>
> "Kim Noer" wrote:
|||Usually in a smaller environment like you describe I reccomend a daily full
backup and then differential backups throughout the day. With this scenario
you can put the database in simple recovery mode and not have to worry about
log file growth. I have seen too many environments where they left the
databases in Full Recovery (default) and never back up the logs. A couple
weeks go by and the database is refusing transactions because the disk is
full.
I truncate and shrink the logs every night to make sure it gets done. One
big Insert or something else can throw your log files out of whack. With
this you should make sure your minimum log file is big enough that it does
not have to grow signifigantly during a normal work day.
When you say your DB is 4.5G (I assume G) after the shrink, how big is it
before the shrink? If your database files are shrinking signifigantly
(>20%) every night you need to look at your clustered indexes and fill
factors to make sure there is enough room that the database is not having to
auto grow throughout the day. Also, if you have not done reindexed in a
while, you should look at doing that - see DBCC Reindex (note that this
should be done when the database is not being accessed).
"Kim Noer" <kn@.nospam.dk> wrote in message
news:%231ouK%2327FHA.2816@.tk2msftngp13.phx.gbl...
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is
> the "best" available. The database I want to backup, is ~4.5 after a
> shrink, but it of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used
> during a normal workday, by around 15 people. What backup setup is the
> recommended in this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log
> every 30 minutes. This generates a /lot/ of *.trn files, is there anyway
> to "consolidate" those after a day? Secondly, when I do a database backup
> every 24 hours, does that mean that I can then afterward safely truncate
> the log (I like keeping things neat
? What do I do with the *.bak and> *.trn when they are over two days old?
> --
> I doubt, therefore I might be.
|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote in message news:uHbwqP37FHA.1140@.tk2msftngp13.phx.gbl
> I definitely agree. Also, be restrictive using shrink, for more info,
> see http://www.karaszi.com/SQLServer/info_dont_shrink.asp
I've read your excellent guide, and I think I actually more now than before
.Anyway. Currently the database runs in "full recovery" mode. Then I did a
complete backup of the database, and then I tried a dbcc loginfo('database')
Now, according to your guide, status 2 means the VLF is in use. The result is
this -
2 253952 8192 65770 0 64 0
2 253952 262144 65769 0 64 0
2 253952 516096 65768 0 128 0
2 278528 770048 65771 0 64 0
2 262144 1048576 65772 0 128 40875000000042200043
...
And this continues all the way to row 308 (your guide tells me I should set the
allocated size way above the current) -
2 27000832 2188771328 65773 2 64 65760000004588300008
2 27000832 2215772160 65766 0 64 65760000004588300008
As you might be able to see, row 308 have the status 2. Doesn't this mean that
this logfile will never go below 2.06GB unless I truncate it manually? Secondly,
what about the VLF's below, since they are unused will this cause SQL Server to
reuse the VLF, or will it proceed from CreateLSN 65760000004588300008?
I doubt, therefore I might be.
|||"Kim Noer" <kn@.nospam.dk> wrote in message
news:OZD%23gFE8FHA.1140@.tk2msftngp13.phx.gbl
> Secondly, what about the VLF's below, since they are
> unused will this cause SQL Server to reuse the VLF, or will it
> proceed from CreateLSN 65760000004588300008?
Nevermind, I decided to use your guide as test, that is, create a table, then
insert a lot of records, which showed me that SQL Server reuses unused VLF, even
when they are "before" used VLF's.
I doubt, therefore I might be.
Developing the clever backup strategy
Hi there...
I've been reading around in the BOL to figure out what backup strategy is the
"best" available. The database I want to backup, is ~4.5 after a shrink, but it
of course grows after a while. Same with the log.
The database runs in "full recovery" mode currently, and it is being used during
a normal workday, by around 15 people. What backup setup is the recommended in
this situation?
I've tried setting it up to backup the database every 4 hours, and the log every
30 minutes. This generates a /lot/ of *.trn files, is there anyway to
"consolidate" those after a day? Secondly, when I do a database backup every 24
hours, does that mean that I can then afterward safely truncate the log (I like
keeping things neat :)? What do I do with the *.bak and *.trn when they are over
two days old?
--
I doubt, therefore I might be.I'd suggest a good, thorough read through of books on line to make sure you
understand things like truncating the logs, full recovery more, simple
recovery mode, etc.
Truncating the logs should probably never be done which is why I suggest this.
burt_king@.yahoo.com
"Kim Noer" wrote:
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is the
> "best" available. The database I want to backup, is ~4.5 after a shrink, but it
> of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used during
> a normal workday, by around 15 people. What backup setup is the recommended in
> this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log every
> 30 minutes. This generates a /lot/ of *.trn files, is there anyway to
> "consolidate" those after a day? Secondly, when I do a database backup every 24
> hours, does that mean that I can then afterward safely truncate the log (I like
> keeping things neat :)? What do I do with the *.bak and *.trn when they are over
> two days old?
> --
> I doubt, therefore I might be.
>|||I definitely agree. Also, be restrictive using shrink, for more info, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"burt_king" <burt_king@.yahoo.com> wrote in message
news:193B7308-3D54-426E-AF7A-B9983D509983@.microsoft.com...
> I'd suggest a good, thorough read through of books on line to make sure you
> understand things like truncating the logs, full recovery more, simple
> recovery mode, etc.
> Truncating the logs should probably never be done which is why I suggest this.
>
> --
> burt_king@.yahoo.com
>
> "Kim Noer" wrote:
>> Hi there...
>> I've been reading around in the BOL to figure out what backup strategy is the
>> "best" available. The database I want to backup, is ~4.5 after a shrink, but it
>> of course grows after a while. Same with the log.
>> The database runs in "full recovery" mode currently, and it is being used during
>> a normal workday, by around 15 people. What backup setup is the recommended in
>> this situation?
>>
>> I've tried setting it up to backup the database every 4 hours, and the log every
>> 30 minutes. This generates a /lot/ of *.trn files, is there anyway to
>> "consolidate" those after a day? Secondly, when I do a database backup every 24
>> hours, does that mean that I can then afterward safely truncate the log (I like
>> keeping things neat :)? What do I do with the *.bak and *.trn when they are over
>> two days old?
>> --
>> I doubt, therefore I might be.
>>|||Usually in a smaller environment like you describe I reccomend a daily full
backup and then differential backups throughout the day. With this scenario
you can put the database in simple recovery mode and not have to worry about
log file growth. I have seen too many environments where they left the
databases in Full Recovery (default) and never back up the logs. A couple
weeks go by and the database is refusing transactions because the disk is
full.
I truncate and shrink the logs every night to make sure it gets done. One
big Insert or something else can throw your log files out of whack. With
this you should make sure your minimum log file is big enough that it does
not have to grow signifigantly during a normal work day.
When you say your DB is 4.5G (I assume G) after the shrink, how big is it
before the shrink? If your database files are shrinking signifigantly
(>20%) every night you need to look at your clustered indexes and fill
factors to make sure there is enough room that the database is not having to
auto grow throughout the day. Also, if you have not done reindexed in a
while, you should look at doing that - see DBCC Reindex (note that this
should be done when the database is not being accessed).
"Kim Noer" <kn@.nospam.dk> wrote in message
news:%231ouK%2327FHA.2816@.tk2msftngp13.phx.gbl...
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is
> the "best" available. The database I want to backup, is ~4.5 after a
> shrink, but it of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used
> during a normal workday, by around 15 people. What backup setup is the
> recommended in this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log
> every 30 minutes. This generates a /lot/ of *.trn files, is there anyway
> to "consolidate" those after a day? Secondly, when I do a database backup
> every 24 hours, does that mean that I can then afterward safely truncate
> the log (I like keeping things neat :)? What do I do with the *.bak and
> *.trn when they are over two days old?
> --
> I doubt, therefore I might be.|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote in message news:uHbwqP37FHA.1140@.tk2msftngp13.phx.gbl
> I definitely agree. Also, be restrictive using shrink, for more info,
> see http://www.karaszi.com/SQLServer/info_dont_shrink.asp
I've read your excellent guide, and I think I actually more now than before :).
Anyway. Currently the database runs in "full recovery" mode. Then I did a
complete backup of the database, and then I tried a dbcc loginfo('database')
Now, according to your guide, status 2 means the VLF is in use. The result is
this -
2 253952 8192 65770 0 64 0
2 253952 262144 65769 0 64 0
2 253952 516096 65768 0 128 0
2 278528 770048 65771 0 64 0
2 262144 1048576 65772 0 128 40875000000042200043
...
And this continues all the way to row 308 (your guide tells me I should set the
allocated size way above the current) -
2 27000832 2188771328 65773 2 64 65760000004588300008
2 27000832 2215772160 65766 0 64 65760000004588300008
As you might be able to see, row 308 have the status 2. Doesn't this mean that
this logfile will never go below 2.06GB unless I truncate it manually? Secondly,
what about the VLF's below, since they are unused will this cause SQL Server to
reuse the VLF, or will it proceed from CreateLSN 65760000004588300008?
--
I doubt, therefore I might be.|||"Kim Noer" <kn@.nospam.dk> wrote in message
news:OZD%23gFE8FHA.1140@.tk2msftngp13.phx.gbl
> Secondly, what about the VLF's below, since they are
> unused will this cause SQL Server to reuse the VLF, or will it
> proceed from CreateLSN 65760000004588300008?
Nevermind, I decided to use your guide as test, that is, create a table, then
insert a lot of records, which showed me that SQL Server reuses unused VLF, even
when they are "before" used VLF's.
--
I doubt, therefore I might be.
I've been reading around in the BOL to figure out what backup strategy is the
"best" available. The database I want to backup, is ~4.5 after a shrink, but it
of course grows after a while. Same with the log.
The database runs in "full recovery" mode currently, and it is being used during
a normal workday, by around 15 people. What backup setup is the recommended in
this situation?
I've tried setting it up to backup the database every 4 hours, and the log every
30 minutes. This generates a /lot/ of *.trn files, is there anyway to
"consolidate" those after a day? Secondly, when I do a database backup every 24
hours, does that mean that I can then afterward safely truncate the log (I like
keeping things neat :)? What do I do with the *.bak and *.trn when they are over
two days old?
--
I doubt, therefore I might be.I'd suggest a good, thorough read through of books on line to make sure you
understand things like truncating the logs, full recovery more, simple
recovery mode, etc.
Truncating the logs should probably never be done which is why I suggest this.
burt_king@.yahoo.com
"Kim Noer" wrote:
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is the
> "best" available. The database I want to backup, is ~4.5 after a shrink, but it
> of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used during
> a normal workday, by around 15 people. What backup setup is the recommended in
> this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log every
> 30 minutes. This generates a /lot/ of *.trn files, is there anyway to
> "consolidate" those after a day? Secondly, when I do a database backup every 24
> hours, does that mean that I can then afterward safely truncate the log (I like
> keeping things neat :)? What do I do with the *.bak and *.trn when they are over
> two days old?
> --
> I doubt, therefore I might be.
>|||I definitely agree. Also, be restrictive using shrink, for more info, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"burt_king" <burt_king@.yahoo.com> wrote in message
news:193B7308-3D54-426E-AF7A-B9983D509983@.microsoft.com...
> I'd suggest a good, thorough read through of books on line to make sure you
> understand things like truncating the logs, full recovery more, simple
> recovery mode, etc.
> Truncating the logs should probably never be done which is why I suggest this.
>
> --
> burt_king@.yahoo.com
>
> "Kim Noer" wrote:
>> Hi there...
>> I've been reading around in the BOL to figure out what backup strategy is the
>> "best" available. The database I want to backup, is ~4.5 after a shrink, but it
>> of course grows after a while. Same with the log.
>> The database runs in "full recovery" mode currently, and it is being used during
>> a normal workday, by around 15 people. What backup setup is the recommended in
>> this situation?
>>
>> I've tried setting it up to backup the database every 4 hours, and the log every
>> 30 minutes. This generates a /lot/ of *.trn files, is there anyway to
>> "consolidate" those after a day? Secondly, when I do a database backup every 24
>> hours, does that mean that I can then afterward safely truncate the log (I like
>> keeping things neat :)? What do I do with the *.bak and *.trn when they are over
>> two days old?
>> --
>> I doubt, therefore I might be.
>>|||Usually in a smaller environment like you describe I reccomend a daily full
backup and then differential backups throughout the day. With this scenario
you can put the database in simple recovery mode and not have to worry about
log file growth. I have seen too many environments where they left the
databases in Full Recovery (default) and never back up the logs. A couple
weeks go by and the database is refusing transactions because the disk is
full.
I truncate and shrink the logs every night to make sure it gets done. One
big Insert or something else can throw your log files out of whack. With
this you should make sure your minimum log file is big enough that it does
not have to grow signifigantly during a normal work day.
When you say your DB is 4.5G (I assume G) after the shrink, how big is it
before the shrink? If your database files are shrinking signifigantly
(>20%) every night you need to look at your clustered indexes and fill
factors to make sure there is enough room that the database is not having to
auto grow throughout the day. Also, if you have not done reindexed in a
while, you should look at doing that - see DBCC Reindex (note that this
should be done when the database is not being accessed).
"Kim Noer" <kn@.nospam.dk> wrote in message
news:%231ouK%2327FHA.2816@.tk2msftngp13.phx.gbl...
> Hi there...
> I've been reading around in the BOL to figure out what backup strategy is
> the "best" available. The database I want to backup, is ~4.5 after a
> shrink, but it of course grows after a while. Same with the log.
> The database runs in "full recovery" mode currently, and it is being used
> during a normal workday, by around 15 people. What backup setup is the
> recommended in this situation?
>
> I've tried setting it up to backup the database every 4 hours, and the log
> every 30 minutes. This generates a /lot/ of *.trn files, is there anyway
> to "consolidate" those after a day? Secondly, when I do a database backup
> every 24 hours, does that mean that I can then afterward safely truncate
> the log (I like keeping things neat :)? What do I do with the *.bak and
> *.trn when they are over two days old?
> --
> I doubt, therefore I might be.|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote in message news:uHbwqP37FHA.1140@.tk2msftngp13.phx.gbl
> I definitely agree. Also, be restrictive using shrink, for more info,
> see http://www.karaszi.com/SQLServer/info_dont_shrink.asp
I've read your excellent guide, and I think I actually more now than before :).
Anyway. Currently the database runs in "full recovery" mode. Then I did a
complete backup of the database, and then I tried a dbcc loginfo('database')
Now, according to your guide, status 2 means the VLF is in use. The result is
this -
2 253952 8192 65770 0 64 0
2 253952 262144 65769 0 64 0
2 253952 516096 65768 0 128 0
2 278528 770048 65771 0 64 0
2 262144 1048576 65772 0 128 40875000000042200043
...
And this continues all the way to row 308 (your guide tells me I should set the
allocated size way above the current) -
2 27000832 2188771328 65773 2 64 65760000004588300008
2 27000832 2215772160 65766 0 64 65760000004588300008
As you might be able to see, row 308 have the status 2. Doesn't this mean that
this logfile will never go below 2.06GB unless I truncate it manually? Secondly,
what about the VLF's below, since they are unused will this cause SQL Server to
reuse the VLF, or will it proceed from CreateLSN 65760000004588300008?
--
I doubt, therefore I might be.|||"Kim Noer" <kn@.nospam.dk> wrote in message
news:OZD%23gFE8FHA.1140@.tk2msftngp13.phx.gbl
> Secondly, what about the VLF's below, since they are
> unused will this cause SQL Server to reuse the VLF, or will it
> proceed from CreateLSN 65760000004588300008?
Nevermind, I decided to use your guide as test, that is, create a table, then
insert a lot of records, which showed me that SQL Server reuses unused VLF, even
when they are "before" used VLF's.
--
I doubt, therefore I might be.
Developing Stored Procedures using Management Studio Express
Hi,
I am new to SQL server 2005. I am developing stored procedures as follows in Management Studio:
1)Right click Stored Procedures folder on a database
2)Select "New Stored Procedure"
3)Write the query in a .sql file
4)Execute the query.
Now in this model, I dont seem to have a develop->test->develop and then deploy, type of development cycle. The problem is each time I execute a query it is deployed and re-executing it results in an error like: "There is already an object named 'NewEmployee' in the database." Which forces you to manually delete the SP and re-execute your query. It doesn't give you a chance to test your SP logic before deploying. Contrary to this, If I developed CLR SP's in Visual Studio, I would test/debug the procedure, and then "deploy" it later when I'm finished with it. Can I not do this in Management Studio?
Thanks,
Bahadir
right click the existing stored proc
click on "script stored procedure as">alter>"new query editor"
modify the scripts
and run
|||Doh! I think this was a bit stupid question. More clever next time :)Thanks,
Bahadir
Developing Stored Procedures using Management Studio Express
Hi,
I am new to SQL server 2005. I am developing stored procedures as follows in Management Studio:
1)Right click Stored Procedures folder on a database
2)Select "New Stored Procedure"
3)Write the query in a .sql file
4)Execute the query.
Now in this model, I dont seem to have a develop->test->develop and then deploy, type of development cycle. The problem is each time I execute a query it is deployed and re-executing it results in an error like: "There is already an object named 'NewEmployee' in the database." Which forces you to manually delete the SP and re-execute your query. It doesn't give you a chance to test your SP logic before deploying. Contrary to this, If I developed CLR SP's in Visual Studio, I would test/debug the procedure, and then "deploy" it later when I'm finished with it. Can I not do this in Management Studio?
Thanks,
Bahadir
right click the existing stored proc
click on "script stored procedure as">alter>"new query editor"
modify the scripts
and run
|||Doh! I think this was a bit stupid question. More clever next time :)
Thanks,
Bahadir
developing ssis in 64bit sql server 2005
I have designed a packege using my local machine ( 32bit) and am trying to deploy this package to 64bit machine and open it up.. are there any issues that I need to aware of? 32 bit ssis and 64bit ssis are comparable each other?
If you are using connections that only have 32bit drivers you will have some issues when you try to execute the package (ie: excel). Other than that you won't see any differences, besides performance gains (most likely).
|||Hi safd*,
Apart from that,
We do have list of Oracle Connectivity issues we need to be aware of, Indeed an adventure to some, see here 
I've summarized the settings we need to be aware of in my blog .
For detailed information download Connectivity and SSIS.doc from Microsoft official site.
Thanks
Subhash Subramanyam
|||I have developed 32bit SSIS package and trying to deploy in 64bit machine ( 64bit sql server 2005). Are there any know issues that i need to aware of? are they fully comparable?|||I'm confused, you posted the same question three days ago and you marked the reply I gave you as answered. Are you have some issues?
|||
Anthony Martin wrote:
I'm confused, you posted the same question three days ago and you marked the reply I gave you as answered. Are you have some issues?
safddddddddddddddddddddd ,
Double posting questions does not do any good to the dynamic of the forum. I am merging this thread to the original one.
Thanks Anthony, for pointing that out.
|||
All,
I am trying to execute a ssis package that has OLE DB orale connection( 32bit) in SQL server 2005 machine ( run as a package )...
I've tried
"D:\Program Files\Microsoft SQL Server (x86)\90\DTS\Binn\DTExec.exe" /FILE "C:\SSISPackage\test3.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E
to run the package in 32bit mode.. but still getting
Description: The connection manager "oracleconnection" will not acquire a connection because the package OfflineMode property is TRUE. When the OfflineMode is TRUE, connections cannot be acquired. End Error Error: 2007-09-20 13:47:12.61 Code: 0xC020801C Source: Data Flow Task OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "oracleconnection" failed with error code 0xC0014019. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2007-09-20 13:47:12.61 Code: 0xC004701A Source: Data Flow Task DTS.Pipeline Description... Process Exit Code 1. The step failed.
can you please help!!!
|||The last time we encountered this, reinstalling the SQL clientworkstation tools fixed the issue.
|||thanks jwelch..
Is there any way you can tell me the step by step procedure that I have to take to make OLE DB for oracle work? I have read a couple of posts and it made me more confused..
what kind of drive do i really need, what kind of patch do i have to apply .. and what configurations do i have to change?
|||Unfortunately, it's been a while, so I don't really have step by step documentation.|||i understand i need to usine 32bit DTExec.exe to run the pakage that has oracle ole db data source..
i've tried .. but it still giving me an error... whatelse should i try ?
|||If you are still getting the "work offline" error meesage, first make sure the package isn't set to Work Offline. If it isn't, then reinstalling the client tools is the only resolution I am aware of.|||thanks Jwelch..
where do i set the "Work offline" property in package?
|||Under the SSIS menu in BIDS, there is an option that says "Work Offline". Make sure it isn't checked.developing reports for Exchange 2003
Has anyone had experience with developing reports based off items in
Exchange 2003? Is it possible to use reporting services to connect to
Exchange to report on types of emails or does another type of connection
have to made? Any insight would be much appreciated. Thanks.
--
****************************************
Andy S.
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
****************************************You might want to download the new "SQL Server 2000 Report Pack for
Microsoft Exchange":
http://www.microsoft.com/downloads/details.aspx?FamilyId=108C2B01-2CC9-4A84-A669-EB22533FA5E2&displaylang=en
It is a set of 13 Microsoft Exchange-based reports with a sample database
that lets you easily visualize and author managed reports for e-mail
administration.
--
Robert M. Bruckner
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andy S." <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:eMSHKeipEHA.2764@.TK2MSFTNGP11.phx.gbl...
> Has anyone had experience with developing reports based off items in
> Exchange 2003? Is it possible to use reporting services to connect to
> Exchange to report on types of emails or does another type of connection
> have to made? Any insight would be much appreciated. Thanks.
> --
> ****************************************
> Andy S.
> andymcdba1@.NOMORESPAM.yahoo.com
> Please remove NOMORESPAM before replying.
> ****************************************
>
>|||Thanks, I saw that. However, if you notice, this SQL Server Report Pack is
for a 3rd party app developed by Super Software for their tool that exports
Exchange code.
What I really need to figure out is how to create a reporting service
connection to Exchange instead of having to figure out how to create a .NET
application that uses a CDO type connection. I keep seeing something about
an Exchange OLE DB Provider but no instructions on how to add it to the
available providers in reporting services or how to access the store in
Exchange with it.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:uPxFW2jpEHA.1992@.TK2MSFTNGP09.phx.gbl...
> You might want to download the new "SQL Server 2000 Report Pack for
> Microsoft Exchange":
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=108C2B01-2CC9-4A84-A669-EB22533FA5E2&displaylang=en
> It is a set of 13 Microsoft Exchange-based reports with a sample database
> that lets you easily visualize and author managed reports for e-mail
> administration.
> --
> Robert M. Bruckner
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andy S." <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
> news:eMSHKeipEHA.2764@.TK2MSFTNGP11.phx.gbl...
> > Has anyone had experience with developing reports based off items in
> > Exchange 2003? Is it possible to use reporting services to connect to
> > Exchange to report on types of emails or does another type of connection
> > have to made? Any insight would be much appreciated. Thanks.
> >
> > --
> > ****************************************
> > Andy S.
> > andymcdba1@.NOMORESPAM.yahoo.com
> >
> > Please remove NOMORESPAM before replying.
> >
> > ****************************************
> >
> >
> >
> >
>|||The Exchange OLEDB provider only works on the Exchange Server itself so you
would have to run Reporting Services on your Exchange Server. Your other
option is to find a WebDAV OLEDB provider (I believe there are some freeware
ones) and you could use that as well from Reporting Services.
--
Looking for a good book on programming Exchange, Outlook, ADSI and
SharePoint? Check out http://www.microsoft.com/MSPress/books/5517.asp
"Andy S." <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:e%23d2CUmpEHA.1296@.TK2MSFTNGP12.phx.gbl...
> Thanks, I saw that. However, if you notice, this SQL Server Report Pack
> is
> for a 3rd party app developed by Super Software for their tool that
> exports
> Exchange code.
> What I really need to figure out is how to create a reporting service
> connection to Exchange instead of having to figure out how to create a
> .NET
> application that uses a CDO type connection. I keep seeing something
> about
> an Exchange OLE DB Provider but no instructions on how to add it to the
> available providers in reporting services or how to access the store in
> Exchange with it.
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:uPxFW2jpEHA.1992@.TK2MSFTNGP09.phx.gbl...
>> You might want to download the new "SQL Server 2000 Report Pack for
>> Microsoft Exchange":
> http://www.microsoft.com/downloads/details.aspx?FamilyId=108C2B01-2CC9-4A84-A669-EB22533FA5E2&displaylang=en
>> It is a set of 13 Microsoft Exchange-based reports with a sample database
>> that lets you easily visualize and author managed reports for e-mail
>> administration.
>> --
>> Robert M. Bruckner
>> Microsoft SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Andy S." <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
>> news:eMSHKeipEHA.2764@.TK2MSFTNGP11.phx.gbl...
>> > Has anyone had experience with developing reports based off items in
>> > Exchange 2003? Is it possible to use reporting services to connect to
>> > Exchange to report on types of emails or does another type of
>> > connection
>> > have to made? Any insight would be much appreciated. Thanks.
>> >
>> > --
>> > ****************************************
>> > Andy S.
>> > andymcdba1@.NOMORESPAM.yahoo.com
>> >
>> > Please remove NOMORESPAM before replying.
>> >
>> > ****************************************
>> >
>> >
>> >
>> >
>>
>
Exchange 2003? Is it possible to use reporting services to connect to
Exchange to report on types of emails or does another type of connection
have to made? Any insight would be much appreciated. Thanks.
--
****************************************
Andy S.
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
****************************************You might want to download the new "SQL Server 2000 Report Pack for
Microsoft Exchange":
http://www.microsoft.com/downloads/details.aspx?FamilyId=108C2B01-2CC9-4A84-A669-EB22533FA5E2&displaylang=en
It is a set of 13 Microsoft Exchange-based reports with a sample database
that lets you easily visualize and author managed reports for e-mail
administration.
--
Robert M. Bruckner
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andy S." <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:eMSHKeipEHA.2764@.TK2MSFTNGP11.phx.gbl...
> Has anyone had experience with developing reports based off items in
> Exchange 2003? Is it possible to use reporting services to connect to
> Exchange to report on types of emails or does another type of connection
> have to made? Any insight would be much appreciated. Thanks.
> --
> ****************************************
> Andy S.
> andymcdba1@.NOMORESPAM.yahoo.com
> Please remove NOMORESPAM before replying.
> ****************************************
>
>|||Thanks, I saw that. However, if you notice, this SQL Server Report Pack is
for a 3rd party app developed by Super Software for their tool that exports
Exchange code.
What I really need to figure out is how to create a reporting service
connection to Exchange instead of having to figure out how to create a .NET
application that uses a CDO type connection. I keep seeing something about
an Exchange OLE DB Provider but no instructions on how to add it to the
available providers in reporting services or how to access the store in
Exchange with it.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:uPxFW2jpEHA.1992@.TK2MSFTNGP09.phx.gbl...
> You might want to download the new "SQL Server 2000 Report Pack for
> Microsoft Exchange":
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=108C2B01-2CC9-4A84-A669-EB22533FA5E2&displaylang=en
> It is a set of 13 Microsoft Exchange-based reports with a sample database
> that lets you easily visualize and author managed reports for e-mail
> administration.
> --
> Robert M. Bruckner
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andy S." <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
> news:eMSHKeipEHA.2764@.TK2MSFTNGP11.phx.gbl...
> > Has anyone had experience with developing reports based off items in
> > Exchange 2003? Is it possible to use reporting services to connect to
> > Exchange to report on types of emails or does another type of connection
> > have to made? Any insight would be much appreciated. Thanks.
> >
> > --
> > ****************************************
> > Andy S.
> > andymcdba1@.NOMORESPAM.yahoo.com
> >
> > Please remove NOMORESPAM before replying.
> >
> > ****************************************
> >
> >
> >
> >
>|||The Exchange OLEDB provider only works on the Exchange Server itself so you
would have to run Reporting Services on your Exchange Server. Your other
option is to find a WebDAV OLEDB provider (I believe there are some freeware
ones) and you could use that as well from Reporting Services.
--
Looking for a good book on programming Exchange, Outlook, ADSI and
SharePoint? Check out http://www.microsoft.com/MSPress/books/5517.asp
"Andy S." <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:e%23d2CUmpEHA.1296@.TK2MSFTNGP12.phx.gbl...
> Thanks, I saw that. However, if you notice, this SQL Server Report Pack
> is
> for a 3rd party app developed by Super Software for their tool that
> exports
> Exchange code.
> What I really need to figure out is how to create a reporting service
> connection to Exchange instead of having to figure out how to create a
> .NET
> application that uses a CDO type connection. I keep seeing something
> about
> an Exchange OLE DB Provider but no instructions on how to add it to the
> available providers in reporting services or how to access the store in
> Exchange with it.
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:uPxFW2jpEHA.1992@.TK2MSFTNGP09.phx.gbl...
>> You might want to download the new "SQL Server 2000 Report Pack for
>> Microsoft Exchange":
> http://www.microsoft.com/downloads/details.aspx?FamilyId=108C2B01-2CC9-4A84-A669-EB22533FA5E2&displaylang=en
>> It is a set of 13 Microsoft Exchange-based reports with a sample database
>> that lets you easily visualize and author managed reports for e-mail
>> administration.
>> --
>> Robert M. Bruckner
>> Microsoft SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Andy S." <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
>> news:eMSHKeipEHA.2764@.TK2MSFTNGP11.phx.gbl...
>> > Has anyone had experience with developing reports based off items in
>> > Exchange 2003? Is it possible to use reporting services to connect to
>> > Exchange to report on types of emails or does another type of
>> > connection
>> > have to made? Any insight would be much appreciated. Thanks.
>> >
>> > --
>> > ****************************************
>> > Andy S.
>> > andymcdba1@.NOMORESPAM.yahoo.com
>> >
>> > Please remove NOMORESPAM before replying.
>> >
>> > ****************************************
>> >
>> >
>> >
>> >
>>
>
Developing new Task in SSIS
Hi All:
For making a custom Task in SSIS, is it possible to reuse the existing code base? For e.g. If i need to append some functionalities to LookUp Transform. Can I inherit the lookUp transform class?
Thanks,
Vipul
Vipul123 wrote:
Hi All:
For making a custom Task in SSIS, is it possible to reuse the existing code base? For e.g. If i need to append some functionalities to LookUp Transform. Can I inherit the lookUp transform class?
Thanks,
Vipul
No. Unfortunately not.
-Jamie
developing new task
Hi
Can i inherit a existing task to a new custom class to add functionality to custom class.
for eg: Inherit lookup transfor which is already present in SSIS to add some funstionality into it.
Thanks
Vipul
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=796926&SiteID=1
Developing Microsoft SQL Server CE 2.0 Merge Replication Using .NET Compact Framework
We are developing Microsoft SQL Server CE 2.0 Merge Replication Using .NET Compact Framework. There is need of sinhronizations between SQL 2005 Mobile Edition witch resides on Barcode terminal (Windows CE) and SQL 2005 Developer Edition (on Windows XP). Everything is done by the book. There is few lines of code that we are using:
public bool Replicate()
{ bool ret = true;
SqlCeReplication repl = null;
try {
// Instantiate and configure
SqlCeReplication object repl = new SqlCeReplication();
string dbFile = ........
repl.InternetUrl = this.InternetUrl;
repl.InternetLogin = this.InternetLogin;
repl.InternetPassword = this.InternetPassword;
repl.Publisher = this.Publisher;
repl.PublisherDatabase = this.PublisherDatabase;
repl.PublisherLogin = this.PublisherLogin;
repl.PublisherPassword = this.PublisherPassword;
repl.Publication = this.Publication;
repl.Subscriber = this.Subscriber;
repl.SubscriberConnectionString ="Data Source=" +dbFile;
if (!System.IO.File.Exists(dbFile))
{ repl.AddSubscription(AddOption.CreateDatabase);
}
repl.Synchronize();
}
IIS is configured, but in log on the server we've got this error:
2007/08/09 15:33:02 Hr=80004005 ACK:Error for DistributorSessionID = 58 2007/08/09 15:33:02 Hr=80004005 The SQL statement failed to execute. [,,,SQL statement,,] 28560 Please give us posible solution of this problem, we have searched on forums but with no result. p.s. I'ts urgentWe are developing Microsoft SQL Server CE 2.0 Merge Replication Using .NET Compact Framework. There is need of sinhronizations between SQL 2005 Mobile Edition witch resides on Barcode terminal (Windows CE) and SQL 2005 Developer Edition (on Windows XP). Everything is done by the book. There is few lines of code that we are using:
public bool Replicate()
{ bool ret = true;
SqlCeReplication repl = null;
try {
// Instantiate and configure
SqlCeReplication object repl = new SqlCeReplication();
string dbFile = ........
repl.InternetUrl = this.InternetUrl;
repl.InternetLogin = this.InternetLogin;
repl.InternetPassword = this.InternetPassword;
repl.Publisher = this.Publisher;
repl.PublisherDatabase = this.PublisherDatabase;
repl.PublisherLogin = this.PublisherLogin;
repl.PublisherPassword = this.PublisherPassword;
repl.Publication = this.Publication;
repl.Subscriber = this.Subscriber;
repl.SubscriberConnectionString ="Data Source=" +dbFile;
if (!System.IO.File.Exists(dbFile))
{ repl.AddSubscription(AddOption.CreateDatabase);
}
repl.Synchronize();
}
IIS is configured, but in log on the server we've got this error:
2007/08/09 15:33:02 Hr=80004005 ACK:Error for DistributorSessionID = 58 2007/08/09 15:33:02 Hr=80004005 The SQL statement failed to execute. [,,,SQL statement,,] 28560 Please give us posible solution of this problem, we have searched on forums but with no result. p.s. I'ts urgent|||
public bool Replicate()
{ bool ret = true;
SqlCeReplication repl = null;
try {
// Instantiate and configure
SqlCeReplication object repl = new SqlCeReplication();
string dbFile = ........
repl.InternetUrl = this.InternetUrl;
repl.InternetLogin = this.InternetLogin;
repl.InternetPassword = this.InternetPassword;
repl.Publisher = this.Publisher;
repl.PublisherDatabase = this.PublisherDatabase;
repl.PublisherLogin = this.PublisherLogin;
repl.PublisherPassword = this.PublisherPassword;
repl.Publication = this.Publication;
repl.Subscriber = this.Subscriber;
repl.SubscriberConnectionString ="Data Source=" +dbFile;
if (!System.IO.File.Exists(dbFile))
{ repl.AddSubscription(AddOption.CreateDatabase);
}
repl.Synchronize();
}
IIS is configured, but in log on the server we've got this error:
2007/08/09 15:33:02 Hr=80004005 ACK:Error for DistributorSessionID = 58 2007/08/09 15:33:02 Hr=80004005 The SQL statement failed to execute. [,,,SQL statement,,] 28560 Please give us posible solution of this problem, we have searched on forums but with no result. p.s. I'ts urgentWe are developing Microsoft SQL Server CE 2.0 Merge Replication Using .NET Compact Framework. There is need of sinhronizations between SQL 2005 Mobile Edition witch resides on Barcode terminal (Windows CE) and SQL 2005 Developer Edition (on Windows XP). Everything is done by the book. There is few lines of code that we are using:
public bool Replicate()
{ bool ret = true;
SqlCeReplication repl = null;
try {
// Instantiate and configure
SqlCeReplication object repl = new SqlCeReplication();
string dbFile = ........
repl.InternetUrl = this.InternetUrl;
repl.InternetLogin = this.InternetLogin;
repl.InternetPassword = this.InternetPassword;
repl.Publisher = this.Publisher;
repl.PublisherDatabase = this.PublisherDatabase;
repl.PublisherLogin = this.PublisherLogin;
repl.PublisherPassword = this.PublisherPassword;
repl.Publication = this.Publication;
repl.Subscriber = this.Subscriber;
repl.SubscriberConnectionString ="Data Source=" +dbFile;
if (!System.IO.File.Exists(dbFile))
{ repl.AddSubscription(AddOption.CreateDatabase);
}
repl.Synchronize();
}
IIS is configured, but in log on the server we've got this error:
2007/08/09 15:33:02 Hr=80004005 ACK:Error for DistributorSessionID = 58 2007/08/09 15:33:02 Hr=80004005 The SQL statement failed to execute. [,,,SQL statement,,] 28560 Please give us posible solution of this problem, we have searched on forums but with no result. p.s. I'ts urgent|||
i hope this will be usefull
Public Shared Function CreateDatabase(ByVal strUserName As String, ByVal strPassword As String) As Boolean
Dim strPublisher, strPublisherDataBase, strPublication As String
Dim strDistributor, strInternetURL As String
Dim strSubscriberDatabasePassword As String
Dim strSubscriberDatabasePath As String
Try
Dim rmReplication As New System.Resources.ResourceManager( _
"RoadRunner.Replication", _
System.Reflection.Assembly.GetExecutingAssembly())
' Assign the resource manager values to data members
strPublication = rmReplication.GetString("Publication")
strPublisher = rmReplication.GetString("Publisher")
strPublisherDataBase = rmReplication.GetString("PublisherDatabase")
strDistributor = rmReplication.GetString("Distributor")
strInternetURL = rmReplication.GetString("InternetUrl")
strSubscriberDatabasePassword = rmReplication.GetString("SubscriberDatabasePassword")
strSubscriberDatabasePath = rmReplication.GetString("SubscriberDatabasePath")
Catch ex As Exception
' MessageBox.Show(ex.Message)
LogFile.AddEntry(ex.Message)
Cursor.Current = Cursors.Default
' if any error occured while reading from resource file, exit function
Return False
End Try
' Declare replication object
Dim replicate As SqlServerCe.SqlCeReplication
Try
' 1: Instantiate replication option
replicate = New SqlServerCe.SqlCeReplication
'***********************************************************
' SQL server 2000 machine name and database for replication
'***********************************************************
replicate.Publisher = strPublisher
replicate.PublisherDatabase = strPublisherDataBase
'**********************************************************
' Publisher server info
'**********************************************************
replicate.Publication = strPublication
replicate.PublisherLogin = strUserName
replicate.PublisherPassword = strPassword
replicate.PublisherSecurityMode = SqlServerCe.SecurityType.NTAuthentication
'**********************************************************
' Distributor server info
'**********************************************************
replicate.Distributor = strDistributor
replicate.DistributorLogin = strUserName
replicate.DistributorPassword = strPassword
replicate.DistributorSecurityMode = SqlServerCe.SecurityType.NTAuthentication
'***********************************************************
' Set subscriber info for salesman and db on PDA
'***********************************************************
replicate.Subscriber = "BTCHH"
replicate.SubscriberConnectionString = "Provider=Microsoft.SQLSERVER.OLEDB.CE.2.0;" _
& "Data Source=" & strSubscriberDatabasePath _
& ";Password=" & strSubscriberDatabasePassword
'***********************************************************
' IIS server info
'***********************************************************
replicate.InternetUrl = strInternetURL
replicate.InternetLogin = strUserName
replicate.InternetPassword = strPassword
' if database doesn't exist then create it
If System.IO.File.Exists(strSubscriberDatabasePath) = False Then
Try
replicate.AddSubscription(SqlServerCe.AddOption.CreateDatabase)
replicate.Synchronize()
Return True
Catch ex As SqlServerCe.SqlCeException
System.IO.File.Delete(strSubscriberDatabasePath)
ReplicationOperationErrors(ex)
Cursor.Current = Cursors.Default
Return False
End Try
End If
Try
' BuildObject.Compact(strSubscriberDatabasePath)
replicate.ReinitializeSubscription(True)
replicate.Synchronize()
'BuildObject.Dispose()
Catch ex As SqlServerCe.SqlCeException
replicate.Dispose()
MsgBox(ex.Message)
End Try
Return True
Catch ex As SqlServerCe.SqlCeException
ReplicationOperationErrors(ex)
Cursor.Current = Cursors.Default
Return False
Finally
'BuildObject.Dispose()
replicate.Dispose()
End Try
End Function
Developing Microsoft SQL Server CE 2.0 Merge Replication Using .NET Compact Framework
We are developing Microsoft SQL Server CE 2.0 Merge Replication Using .NET Compact Framework. There is need of sinhronizations between SQL 2005 Mobile Edition witch resides on Barcode terminal (Windows CE) and SQL 2005 Developer Edition (on Windows XP). Everything is done by the book. There is few lines of code that we are using:
public bool Replicate()
{ bool ret = true;
SqlCeReplication repl = null;
try {
// Instantiate and configure
SqlCeReplication object repl = new SqlCeReplication();
string dbFile = ........
repl.InternetUrl = this.InternetUrl;
repl.InternetLogin = this.InternetLogin;
repl.InternetPassword = this.InternetPassword;
repl.Publisher = this.Publisher;
repl.PublisherDatabase = this.PublisherDatabase;
repl.PublisherLogin = this.PublisherLogin;
repl.PublisherPassword = this.PublisherPassword;
repl.Publication = this.Publication;
repl.Subscriber = this.Subscriber;
repl.SubscriberConnectionString ="Data Source=" +dbFile;
if (!System.IO.File.Exists(dbFile))
{ repl.AddSubscription(AddOption.CreateDatabase);
}
repl.Synchronize();
}
IIS is configured, but in log on the server we've got this error:
2007/08/09 15:33:02 Hr=80004005 ACK:Error for DistributorSessionID = 58 2007/08/09 15:33:02 Hr=80004005 The SQL statement failed to execute. [,,,SQL statement,,] 28560 Please give us posible solution of this problem, we have searched on forums but with no result. p.s. I'ts urgentWe are developing Microsoft SQL Server CE 2.0 Merge Replication Using .NET Compact Framework. There is need of sinhronizations between SQL 2005 Mobile Edition witch resides on Barcode terminal (Windows CE) and SQL 2005 Developer Edition (on Windows XP). Everything is done by the book. There is few lines of code that we are using:
public bool Replicate()
{ bool ret = true;
SqlCeReplication repl = null;
try {
// Instantiate and configure
SqlCeReplication object repl = new SqlCeReplication();
string dbFile = ........
repl.InternetUrl = this.InternetUrl;
repl.InternetLogin = this.InternetLogin;
repl.InternetPassword = this.InternetPassword;
repl.Publisher = this.Publisher;
repl.PublisherDatabase = this.PublisherDatabase;
repl.PublisherLogin = this.PublisherLogin;
repl.PublisherPassword = this.PublisherPassword;
repl.Publication = this.Publication;
repl.Subscriber = this.Subscriber;
repl.SubscriberConnectionString ="Data Source=" +dbFile;
if (!System.IO.File.Exists(dbFile))
{ repl.AddSubscription(AddOption.CreateDatabase);
}
repl.Synchronize();
}
IIS is configured, but in log on the server we've got this error:
2007/08/09 15:33:02 Hr=80004005 ACK:Error for DistributorSessionID = 58 2007/08/09 15:33:02 Hr=80004005 The SQL statement failed to execute. [,,,SQL statement,,] 28560 Please give us posible solution of this problem, we have searched on forums but with no result. p.s. I'ts urgent|||
public bool Replicate()
{ bool ret = true;
SqlCeReplication repl = null;
try {
// Instantiate and configure
SqlCeReplication object repl = new SqlCeReplication();
string dbFile = ........
repl.InternetUrl = this.InternetUrl;
repl.InternetLogin = this.InternetLogin;
repl.InternetPassword = this.InternetPassword;
repl.Publisher = this.Publisher;
repl.PublisherDatabase = this.PublisherDatabase;
repl.PublisherLogin = this.PublisherLogin;
repl.PublisherPassword = this.PublisherPassword;
repl.Publication = this.Publication;
repl.Subscriber = this.Subscriber;
repl.SubscriberConnectionString ="Data Source=" +dbFile;
if (!System.IO.File.Exists(dbFile))
{ repl.AddSubscription(AddOption.CreateDatabase);
}
repl.Synchronize();
}
IIS is configured, but in log on the server we've got this error:
2007/08/09 15:33:02 Hr=80004005 ACK:Error for DistributorSessionID = 58 2007/08/09 15:33:02 Hr=80004005 The SQL statement failed to execute. [,,,SQL statement,,] 28560 Please give us posible solution of this problem, we have searched on forums but with no result. p.s. I'ts urgentWe are developing Microsoft SQL Server CE 2.0 Merge Replication Using .NET Compact Framework. There is need of sinhronizations between SQL 2005 Mobile Edition witch resides on Barcode terminal (Windows CE) and SQL 2005 Developer Edition (on Windows XP). Everything is done by the book. There is few lines of code that we are using:
public bool Replicate()
{ bool ret = true;
SqlCeReplication repl = null;
try {
// Instantiate and configure
SqlCeReplication object repl = new SqlCeReplication();
string dbFile = ........
repl.InternetUrl = this.InternetUrl;
repl.InternetLogin = this.InternetLogin;
repl.InternetPassword = this.InternetPassword;
repl.Publisher = this.Publisher;
repl.PublisherDatabase = this.PublisherDatabase;
repl.PublisherLogin = this.PublisherLogin;
repl.PublisherPassword = this.PublisherPassword;
repl.Publication = this.Publication;
repl.Subscriber = this.Subscriber;
repl.SubscriberConnectionString ="Data Source=" +dbFile;
if (!System.IO.File.Exists(dbFile))
{ repl.AddSubscription(AddOption.CreateDatabase);
}
repl.Synchronize();
}
IIS is configured, but in log on the server we've got this error:
2007/08/09 15:33:02 Hr=80004005 ACK:Error for DistributorSessionID = 58 2007/08/09 15:33:02 Hr=80004005 The SQL statement failed to execute. [,,,SQL statement,,] 28560 Please give us posible solution of this problem, we have searched on forums but with no result. p.s. I'ts urgent|||
i hope this will be usefull
Public Shared Function CreateDatabase(ByVal strUserName As String, ByVal strPassword As String) As Boolean
Dim strPublisher, strPublisherDataBase, strPublication As String
Dim strDistributor, strInternetURL As String
Dim strSubscriberDatabasePassword As String
Dim strSubscriberDatabasePath As String
Try
Dim rmReplication As New System.Resources.ResourceManager( _
"RoadRunner.Replication", _
System.Reflection.Assembly.GetExecutingAssembly())
' Assign the resource manager values to data members
strPublication = rmReplication.GetString("Publication")
strPublisher = rmReplication.GetString("Publisher")
strPublisherDataBase = rmReplication.GetString("PublisherDatabase")
strDistributor = rmReplication.GetString("Distributor")
strInternetURL = rmReplication.GetString("InternetUrl")
strSubscriberDatabasePassword = rmReplication.GetString("SubscriberDatabasePassword")
strSubscriberDatabasePath = rmReplication.GetString("SubscriberDatabasePath")
Catch ex As Exception
' MessageBox.Show(ex.Message)
LogFile.AddEntry(ex.Message)
Cursor.Current = Cursors.Default
' if any error occured while reading from resource file, exit function
Return False
End Try
' Declare replication object
Dim replicate As SqlServerCe.SqlCeReplication
Try
' 1: Instantiate replication option
replicate = New SqlServerCe.SqlCeReplication
'***********************************************************
' SQL server 2000 machine name and database for replication
'***********************************************************
replicate.Publisher = strPublisher
replicate.PublisherDatabase = strPublisherDataBase
'**********************************************************
' Publisher server info
'**********************************************************
replicate.Publication = strPublication
replicate.PublisherLogin = strUserName
replicate.PublisherPassword = strPassword
replicate.PublisherSecurityMode = SqlServerCe.SecurityType.NTAuthentication
'**********************************************************
' Distributor server info
'**********************************************************
replicate.Distributor = strDistributor
replicate.DistributorLogin = strUserName
replicate.DistributorPassword = strPassword
replicate.DistributorSecurityMode = SqlServerCe.SecurityType.NTAuthentication
'***********************************************************
' Set subscriber info for salesman and db on PDA
'***********************************************************
replicate.Subscriber = "BTCHH"
replicate.SubscriberConnectionString = "Provider=Microsoft.SQLSERVER.OLEDB.CE.2.0;" _
& "Data Source=" & strSubscriberDatabasePath _
& ";Password=" & strSubscriberDatabasePassword
'***********************************************************
' IIS server info
'***********************************************************
replicate.InternetUrl = strInternetURL
replicate.InternetLogin = strUserName
replicate.InternetPassword = strPassword
' if database doesn't exist then create it
If System.IO.File.Exists(strSubscriberDatabasePath) = False Then
Try
replicate.AddSubscription(SqlServerCe.AddOption.CreateDatabase)
replicate.Synchronize()
Return True
Catch ex As SqlServerCe.SqlCeException
System.IO.File.Delete(strSubscriberDatabasePath)
ReplicationOperationErrors(ex)
Cursor.Current = Cursors.Default
Return False
End Try
End If
Try
' BuildObject.Compact(strSubscriberDatabasePath)
replicate.ReinitializeSubscription(True)
replicate.Synchronize()
'BuildObject.Dispose()
Catch ex As SqlServerCe.SqlCeException
replicate.Dispose()
MsgBox(ex.Message)
End Try
Return True
Catch ex As SqlServerCe.SqlCeException
ReplicationOperationErrors(ex)
Cursor.Current = Cursors.Default
Return False
Finally
'BuildObject.Dispose()
replicate.Dispose()
End Try
End Function
Developing for 2000 and 2005
Hi,
What are our options for developing for 2000 and 2005 "at the same time" /
on one computer.
I upgraded my local sql2000 to sql2005 and installed Visual Studio 2005 side
by side with Visual Studio 2003. Now Visual Studio 2003 cannot open Sql2000
report server projects anymore and 2005 "complains" about upgrading the
report projects. For several customers we still need to develop Sql2000
reports while other customers request Sql2005 reports.
Please advise,
ErikYou need to keep the source for the RS 2000 reports separate from the RS
2005 reports. RS 2005 will still run 2000 reports. 2000 will not run 2005
reports. 2005 Report Designer converts 2000 reports when you try to modify
them in 2005.
I took a 2000 report (I have both report designers on my machine) and I
deployed it to RS 2005.
Although 2005 is supposed to run 2000 reports I have noticed some minor
problems. For instance, if I do this:
= "Myparam1 = " & Parameters!Myparam1.Label
It doesn't like the use of label. However, if I convert the report by
bringing it into the 2005 designer, convert, redeploy the error goes away.
My suggestion is to have two report servers. One for 2000 and one for 2005.
Having both designers on one machine is not a problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in message
news:eEZs$fB7FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Hi,
> What are our options for developing for 2000 and 2005 "at the same time" /
> on one computer.
> I upgraded my local sql2000 to sql2005 and installed Visual Studio 2005
> side by side with Visual Studio 2003. Now Visual Studio 2003 cannot open
> Sql2000 report server projects anymore and 2005 "complains" about
> upgrading the report projects. For several customers we still need to
> develop Sql2000 reports while other customers request Sql2005 reports.
> Please advise,
> Erik
>|||Plausible.
The upgrade of Sql2000 to Sql2005 (developer editions) on my own machine
removed Sql 2000 Report Designed and installed Sql 2005 Report Designed. I
now reinstalled the Sql 2000 Report Designed (which I didn't think was
possible).
Thanks.
Erik
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eQND1pE7FHA.268@.TK2MSFTNGP10.phx.gbl...
> You need to keep the source for the RS 2000 reports separate from the RS
> 2005 reports. RS 2005 will still run 2000 reports. 2000 will not run 2005
> reports. 2005 Report Designer converts 2000 reports when you try to modify
> them in 2005.
> I took a 2000 report (I have both report designers on my machine) and I
> deployed it to RS 2005.
> Although 2005 is supposed to run 2000 reports I have noticed some minor
> problems. For instance, if I do this:
> = "Myparam1 = " & Parameters!Myparam1.Label
> It doesn't like the use of label. However, if I convert the report by
> bringing it into the 2005 designer, convert, redeploy the error goes away.
> My suggestion is to have two report servers. One for 2000 and one for
> 2005. Having both designers on one machine is not a problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> message news:eEZs$fB7FHA.3660@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> What are our options for developing for 2000 and 2005 "at the same time"
>> / on one computer.
>> I upgraded my local sql2000 to sql2005 and installed Visual Studio 2005
>> side by side with Visual Studio 2003. Now Visual Studio 2003 cannot open
>> Sql2000 report server projects anymore and 2005 "complains" about
>> upgrading the report projects. For several customers we still need to
>> develop Sql2000 reports while other customers request Sql2005 reports.
>> Please advise,
>> Erik
>
What are our options for developing for 2000 and 2005 "at the same time" /
on one computer.
I upgraded my local sql2000 to sql2005 and installed Visual Studio 2005 side
by side with Visual Studio 2003. Now Visual Studio 2003 cannot open Sql2000
report server projects anymore and 2005 "complains" about upgrading the
report projects. For several customers we still need to develop Sql2000
reports while other customers request Sql2005 reports.
Please advise,
ErikYou need to keep the source for the RS 2000 reports separate from the RS
2005 reports. RS 2005 will still run 2000 reports. 2000 will not run 2005
reports. 2005 Report Designer converts 2000 reports when you try to modify
them in 2005.
I took a 2000 report (I have both report designers on my machine) and I
deployed it to RS 2005.
Although 2005 is supposed to run 2000 reports I have noticed some minor
problems. For instance, if I do this:
= "Myparam1 = " & Parameters!Myparam1.Label
It doesn't like the use of label. However, if I convert the report by
bringing it into the 2005 designer, convert, redeploy the error goes away.
My suggestion is to have two report servers. One for 2000 and one for 2005.
Having both designers on one machine is not a problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in message
news:eEZs$fB7FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Hi,
> What are our options for developing for 2000 and 2005 "at the same time" /
> on one computer.
> I upgraded my local sql2000 to sql2005 and installed Visual Studio 2005
> side by side with Visual Studio 2003. Now Visual Studio 2003 cannot open
> Sql2000 report server projects anymore and 2005 "complains" about
> upgrading the report projects. For several customers we still need to
> develop Sql2000 reports while other customers request Sql2005 reports.
> Please advise,
> Erik
>|||Plausible.
The upgrade of Sql2000 to Sql2005 (developer editions) on my own machine
removed Sql 2000 Report Designed and installed Sql 2005 Report Designed. I
now reinstalled the Sql 2000 Report Designed (which I didn't think was
possible).
Thanks.
Erik
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eQND1pE7FHA.268@.TK2MSFTNGP10.phx.gbl...
> You need to keep the source for the RS 2000 reports separate from the RS
> 2005 reports. RS 2005 will still run 2000 reports. 2000 will not run 2005
> reports. 2005 Report Designer converts 2000 reports when you try to modify
> them in 2005.
> I took a 2000 report (I have both report designers on my machine) and I
> deployed it to RS 2005.
> Although 2005 is supposed to run 2000 reports I have noticed some minor
> problems. For instance, if I do this:
> = "Myparam1 = " & Parameters!Myparam1.Label
> It doesn't like the use of label. However, if I convert the report by
> bringing it into the 2005 designer, convert, redeploy the error goes away.
> My suggestion is to have two report servers. One for 2000 and one for
> 2005. Having both designers on one machine is not a problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> message news:eEZs$fB7FHA.3660@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> What are our options for developing for 2000 and 2005 "at the same time"
>> / on one computer.
>> I upgraded my local sql2000 to sql2005 and installed Visual Studio 2005
>> side by side with Visual Studio 2003. Now Visual Studio 2003 cannot open
>> Sql2000 report server projects anymore and 2005 "complains" about
>> upgrading the report projects. For several customers we still need to
>> develop Sql2000 reports while other customers request Sql2005 reports.
>> Please advise,
>> Erik
>
Developing for 2000 (SQL8) on 2005 (SQL9)
We've started upgrading some of our servers to 2005 from 2000, and that
includes my development machine.
I slightly concerned that I will inadvertantly throw in some 2005 code in my
2000 databases which will screw up the destination database on deployment.
Is there a way of specifying that a DB should be 2000-compliant?
What other pitfalls might I face? Any other good advice?
In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
don't think I've been pushing the boundaries with anything I'm doing at the
moment, so I dont expect too many problems, but you never know...
Thanks in advance...
cjmnews04@.REMOVEMEyahoo.co.uk
[remove the obvious bits]CJM
As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
2005
Are you talking about T-SQL enhances in SQL Server 2005?
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||I keep both versions installed for different kinds of work and simply do not
worry about potential risks, since 2005 features simply do not exist in 2000
.
ML
http://milambda.blogspot.com/|||You can come a bit closer to 2000 compliant by specifying database compatibi
lity level 80 instead of
the default 90. See sp_dbcmptlevel for details.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.
gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that in
cludes my development
> machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
my 2000 databases which
> will screw up the destination database on deployment. Is there a way of sp
ecifying that a DB
> should be 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I do
n't think I've been
> pushing the boundaries with anything I'm doing at the moment, so I dont ex
pect too many problems,
> but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23Orrb4OIGHA.3036@.tk2msftngp13.phx.gbl...
> CJM
> As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
> 2005
> Are you talking about T-SQL enhances in SQL Server 2005?
>
I'm talking about anything I don't know! :)
Obviously I don't intend to use any of the 2005 enhancements in my 2000
DB's, but I just want to be sure that if I stick to ANSI SQL that will I be
OK... For example, do SQL8 & 9 have compatible data files/backup files - I
often transfer data by restoring a backup on a different server or by copy a
data file and attaching it.
Update: I've just noticed that you can install SQL 2000 alongside 2005, and
I've also spotted the compatability settings. Is it better to try and
develop in the one system (2005) or should I install SQL 2000 alongside it?
(note: I've got a new development machine so I have a 'blank canvas' so to
speak; SQL 2000 is currently not installed)
Thanks
Chris|||Keeping both versions and doing work in the appropriate one seems safer to
me...
ML
http://milambda.blogspot.com/|||"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||
> OK... For example, do SQL8 & 9 have compatible data files/backup files - I
> often transfer data by restoring a backup on a different server or by copy
> a data file and attaching it.
No - you cannot restore a database from sql server 2005 to a database in sql
server 2000. Same for detach/attach. I believe the reverse direction is
supported.|||"Scott Morris" <bogus@.bogus.com> wrote in message
news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> No - you cannot restore a database from sql server 2005 to a database in
> sql server 2000. Same for detach/attach. I believe the reverse direction
> is supported.
>
Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but it appears from what you (and others) say that it
works from 2000 to 2005 which is useful to know.
However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...|||I definitely agree that you should have side-by-side and develop on a "pure"
2000. Short story is
that database compatibility level isn't 100%...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:umKq9FQIGHA.3904@.TK2MSFTNGP10.phx.
gbl...
> "Scott Morris" <bogus@.bogus.com> wrote in message news:uZpP%23CQIGHA.2064@.
TK2MSFTNGP09.phx.gbl...
> Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but
> it appears from what you (and others) say that it works from 2000 to 2005
which is useful to know.
> However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...
>
includes my development machine.
I slightly concerned that I will inadvertantly throw in some 2005 code in my
2000 databases which will screw up the destination database on deployment.
Is there a way of specifying that a DB should be 2000-compliant?
What other pitfalls might I face? Any other good advice?
In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
don't think I've been pushing the boundaries with anything I'm doing at the
moment, so I dont expect too many problems, but you never know...
Thanks in advance...
cjmnews04@.REMOVEMEyahoo.co.uk
[remove the obvious bits]CJM
As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
2005
Are you talking about T-SQL enhances in SQL Server 2005?
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||I keep both versions installed for different kinds of work and simply do not
worry about potential risks, since 2005 features simply do not exist in 2000
.
ML
http://milambda.blogspot.com/|||You can come a bit closer to 2000 compliant by specifying database compatibi
lity level 80 instead of
the default 90. See sp_dbcmptlevel for details.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.
gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that in
cludes my development
> machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
my 2000 databases which
> will screw up the destination database on deployment. Is there a way of sp
ecifying that a DB
> should be 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I do
n't think I've been
> pushing the boundaries with anything I'm doing at the moment, so I dont ex
pect too many problems,
> but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23Orrb4OIGHA.3036@.tk2msftngp13.phx.gbl...
> CJM
> As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
> 2005
> Are you talking about T-SQL enhances in SQL Server 2005?
>
I'm talking about anything I don't know! :)
Obviously I don't intend to use any of the 2005 enhancements in my 2000
DB's, but I just want to be sure that if I stick to ANSI SQL that will I be
OK... For example, do SQL8 & 9 have compatible data files/backup files - I
often transfer data by restoring a backup on a different server or by copy a
data file and attaching it.
Update: I've just noticed that you can install SQL 2000 alongside 2005, and
I've also spotted the compatability settings. Is it better to try and
develop in the one system (2005) or should I install SQL 2000 alongside it?
(note: I've got a new development machine so I have a 'blank canvas' so to
speak; SQL 2000 is currently not installed)
Thanks
Chris|||Keeping both versions and doing work in the appropriate one seems safer to
me...
ML
http://milambda.blogspot.com/|||"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||
> OK... For example, do SQL8 & 9 have compatible data files/backup files - I
> often transfer data by restoring a backup on a different server or by copy
> a data file and attaching it.
No - you cannot restore a database from sql server 2005 to a database in sql
server 2000. Same for detach/attach. I believe the reverse direction is
supported.|||"Scott Morris" <bogus@.bogus.com> wrote in message
news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> No - you cannot restore a database from sql server 2005 to a database in
> sql server 2000. Same for detach/attach. I believe the reverse direction
> is supported.
>
Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but it appears from what you (and others) say that it
works from 2000 to 2005 which is useful to know.
However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...|||I definitely agree that you should have side-by-side and develop on a "pure"
2000. Short story is
that database compatibility level isn't 100%...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:umKq9FQIGHA.3904@.TK2MSFTNGP10.phx.
gbl...
> "Scott Morris" <bogus@.bogus.com> wrote in message news:uZpP%23CQIGHA.2064@.
TK2MSFTNGP09.phx.gbl...
> Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but
> it appears from what you (and others) say that it works from 2000 to 2005
which is useful to know.
> However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...
>
Developing for 2000 (SQL8) on 2005 (SQL9)
We've started upgrading some of our servers to 2005 from 2000, and that
includes my development machine.
I slightly concerned that I will inadvertantly throw in some 2005 code in my
2000 databases which will screw up the destination database on deployment.
Is there a way of specifying that a DB should be 2000-compliant?
What other pitfalls might I face? Any other good advice?
In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
don't think I've been pushing the boundaries with anything I'm doing at the
moment, so I dont expect too many problems, but you never know...
Thanks in advance...
cjmnews04@.REMOVEMEyahoo.co.uk
[remove the obvious bits]CJM
As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
2005
Are you talking about T-SQL enhances in SQL Server 2005?
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||I keep both versions installed for different kinds of work and simply do not
worry about potential risks, since 2005 features simply do not exist in 2000
.
ML
http://milambda.blogspot.com/|||You can come a bit closer to 2000 compliant by specifying database compatibi
lity level 80 instead of
the default 90. See sp_dbcmptlevel for details.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.g
bl...
> We've started upgrading some of our servers to 2005 from 2000, and that in
cludes my development
> machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
my 2000 databases which
> will screw up the destination database on deployment. Is there a way of sp
ecifying that a DB
> should be 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I do
n't think I've been
> pushing the boundaries with anything I'm doing at the moment, so I dont ex
pect too many problems,
> but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23Orrb4OIGHA.3036@.tk2msftngp13.phx.gbl...
> CJM
> As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
> 2005
> Are you talking about T-SQL enhances in SQL Server 2005?
>
I'm talking about anything I don't know!
Obviously I don't intend to use any of the 2005 enhancements in my 2000
DB's, but I just want to be sure that if I stick to ANSI SQL that will I be
OK... For example, do SQL8 & 9 have compatible data files/backup files - I
often transfer data by restoring a backup on a different server or by copy a
data file and attaching it.
Update: I've just noticed that you can install SQL 2000 alongside 2005, and
I've also spotted the compatability settings. Is it better to try and
develop in the one system (2005) or should I install SQL 2000 alongside it?
(note: I've got a new development machine so I have a 'blank canvas' so to
speak; SQL 2000 is currently not installed)
Thanks
Chris|||Keeping both versions and doing work in the appropriate one seems safer to
me...
ML
http://milambda.blogspot.com/|||
> OK... For example, do SQL8 & 9 have compatible data files/backup files - I
> often transfer data by restoring a backup on a different server or by copy
> a data file and attaching it.
No - you cannot restore a database from sql server 2005 to a database in sql
server 2000. Same for detach/attach. I believe the reverse direction is
supported.|||"Scott Morris" <bogus@.bogus.com> wrote in message
news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> No - you cannot restore a database from sql server 2005 to a database in
> sql server 2000. Same for detach/attach. I believe the reverse direction
> is supported.
>
Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but it appears from what you (and others) say that it
works from 2000 to 2005 which is useful to know.
However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...|||I definitely agree that you should have side-by-side and develop on a "pure"
2000. Short story is
that database compatibility level isn't 100%...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:umKq9FQIGHA.3904@.TK2MSFTNGP10.phx.g
bl...
> "Scott Morris" <bogus@.bogus.com> wrote in message news:uZpP%23CQIGHA.2064@.
TK2MSFTNGP09.phx.gbl...
> Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but
> it appears from what you (and others) say that it works from 2000 to 2005
which is useful to know.
> However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...
>
includes my development machine.
I slightly concerned that I will inadvertantly throw in some 2005 code in my
2000 databases which will screw up the destination database on deployment.
Is there a way of specifying that a DB should be 2000-compliant?
What other pitfalls might I face? Any other good advice?
In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
don't think I've been pushing the boundaries with anything I'm doing at the
moment, so I dont expect too many problems, but you never know...
Thanks in advance...
cjmnews04@.REMOVEMEyahoo.co.uk
[remove the obvious bits]CJM
As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
2005
Are you talking about T-SQL enhances in SQL Server 2005?
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||I keep both versions installed for different kinds of work and simply do not
worry about potential risks, since 2005 features simply do not exist in 2000
.
ML
http://milambda.blogspot.com/|||You can come a bit closer to 2000 compliant by specifying database compatibi
lity level 80 instead of
the default 90. See sp_dbcmptlevel for details.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.g
bl...
> We've started upgrading some of our servers to 2005 from 2000, and that in
cludes my development
> machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
my 2000 databases which
> will screw up the destination database on deployment. Is there a way of sp
ecifying that a DB
> should be 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I do
n't think I've been
> pushing the boundaries with anything I'm doing at the moment, so I dont ex
pect too many problems,
> but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23Orrb4OIGHA.3036@.tk2msftngp13.phx.gbl...
> CJM
> As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
> 2005
> Are you talking about T-SQL enhances in SQL Server 2005?
>
I'm talking about anything I don't know!
Obviously I don't intend to use any of the 2005 enhancements in my 2000
DB's, but I just want to be sure that if I stick to ANSI SQL that will I be
OK... For example, do SQL8 & 9 have compatible data files/backup files - I
often transfer data by restoring a backup on a different server or by copy a
data file and attaching it.
Update: I've just noticed that you can install SQL 2000 alongside 2005, and
I've also spotted the compatability settings. Is it better to try and
develop in the one system (2005) or should I install SQL 2000 alongside it?
(note: I've got a new development machine so I have a 'blank canvas' so to
speak; SQL 2000 is currently not installed)
Thanks
Chris|||Keeping both versions and doing work in the appropriate one seems safer to
me...
ML
http://milambda.blogspot.com/|||
> OK... For example, do SQL8 & 9 have compatible data files/backup files - I
> often transfer data by restoring a backup on a different server or by copy
> a data file and attaching it.
No - you cannot restore a database from sql server 2005 to a database in sql
server 2000. Same for detach/attach. I believe the reverse direction is
supported.|||"Scott Morris" <bogus@.bogus.com> wrote in message
news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> No - you cannot restore a database from sql server 2005 to a database in
> sql server 2000. Same for detach/attach. I believe the reverse direction
> is supported.
>
Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but it appears from what you (and others) say that it
works from 2000 to 2005 which is useful to know.
However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...|||I definitely agree that you should have side-by-side and develop on a "pure"
2000. Short story is
that database compatibility level isn't 100%...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:umKq9FQIGHA.3904@.TK2MSFTNGP10.phx.g
bl...
> "Scott Morris" <bogus@.bogus.com> wrote in message news:uZpP%23CQIGHA.2064@.
TK2MSFTNGP09.phx.gbl...
> Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but
> it appears from what you (and others) say that it works from 2000 to 2005
which is useful to know.
> However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...
>
Developing for 2000 (SQL8) on 2005 (SQL9)
We've started upgrading some of our servers to 2005 from 2000, and that
includes my development machine.
I slightly concerned that I will inadvertantly throw in some 2005 code in my
2000 databases which will screw up the destination database on deployment.
Is there a way of specifying that a DB should be 2000-compliant?
What other pitfalls might I face? Any other good advice?
In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
don't think I've been pushing the boundaries with anything I'm doing at the
moment, so I dont expect too many problems, but you never know...
Thanks in advance...
cjmnews04@.REMOVEMEyahoo.co.uk
[remove the obvious bits]
CJM
As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
2005
Are you talking about T-SQL enhances in SQL Server 2005?
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>
|||I keep both versions installed for different kinds of work and simply do not
worry about potential risks, since 2005 features simply do not exist in 2000.
ML
http://milambda.blogspot.com/
|||You can come a bit closer to 2000 compliant by specifying database compatibility level 80 instead of
the default 90. See sp_dbcmptlevel for details.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that includes my development
> machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in my 2000 databases which
> will screw up the destination database on deployment. Is there a way of specifying that a DB
> should be 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I don't think I've been
> pushing the boundaries with anything I'm doing at the moment, so I dont expect too many problems,
> but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>
|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23Orrb4OIGHA.3036@.tk2msftngp13.phx.gbl...
> CJM
> As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
> 2005
> Are you talking about T-SQL enhances in SQL Server 2005?
>
I'm talking about anything I don't know!
Obviously I don't intend to use any of the 2005 enhancements in my 2000
DB's, but I just want to be sure that if I stick to ANSI SQL that will I be
OK... For example, do SQL8 & 9 have compatible data files/backup files - I
often transfer data by restoring a backup on a different server or by copy a
data file and attaching it.
Update: I've just noticed that you can install SQL 2000 alongside 2005, and
I've also spotted the compatability settings. Is it better to try and
develop in the one system (2005) or should I install SQL 2000 alongside it?
(note: I've got a new development machine so I have a 'blank canvas' so to
speak; SQL 2000 is currently not installed)
Thanks
Chris
|||Keeping both versions and doing work in the appropriate one seems safer to
me...
ML
http://milambda.blogspot.com/
|||
> OK... For example, do SQL8 & 9 have compatible data files/backup files - I
> often transfer data by restoring a backup on a different server or by copy
> a data file and attaching it.
No - you cannot restore a database from sql server 2005 to a database in sql
server 2000. Same for detach/attach. I believe the reverse direction is
supported.
|||"Scott Morris" <bogus@.bogus.com> wrote in message
news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> No - you cannot restore a database from sql server 2005 to a database in
> sql server 2000. Same for detach/attach. I believe the reverse direction
> is supported.
>
Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but it appears from what you (and others) say that it
works from 2000 to 2005 which is useful to know.
However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...
|||I definitely agree that you should have side-by-side and develop on a "pure" 2000. Short story is
that database compatibility level isn't 100%...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:umKq9FQIGHA.3904@.TK2MSFTNGP10.phx.gbl...
> "Scott Morris" <bogus@.bogus.com> wrote in message news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> Sorry - I should have been more clear. I don't expect to restore a 2005 DB to a 2000 instance, but
> it appears from what you (and others) say that it works from 2000 to 2005 which is useful to know.
> However, I think I'm erring towards installing 2000 and 2005 side-by-side instead...
>
includes my development machine.
I slightly concerned that I will inadvertantly throw in some 2005 code in my
2000 databases which will screw up the destination database on deployment.
Is there a way of specifying that a DB should be 2000-compliant?
What other pitfalls might I face? Any other good advice?
In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
don't think I've been pushing the boundaries with anything I'm doing at the
moment, so I dont expect too many problems, but you never know...
Thanks in advance...
cjmnews04@.REMOVEMEyahoo.co.uk
[remove the obvious bits]
CJM
As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
2005
Are you talking about T-SQL enhances in SQL Server 2005?
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>
|||I keep both versions installed for different kinds of work and simply do not
worry about potential risks, since 2005 features simply do not exist in 2000.
ML
http://milambda.blogspot.com/
|||You can come a bit closer to 2000 compliant by specifying database compatibility level 80 instead of
the default 90. See sp_dbcmptlevel for details.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that includes my development
> machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in my 2000 databases which
> will screw up the destination database on deployment. Is there a way of specifying that a DB
> should be 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I don't think I've been
> pushing the boundaries with anything I'm doing at the moment, so I dont expect too many problems,
> but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>
|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23Orrb4OIGHA.3036@.tk2msftngp13.phx.gbl...
> CJM
> As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
> 2005
> Are you talking about T-SQL enhances in SQL Server 2005?
>
I'm talking about anything I don't know!
Obviously I don't intend to use any of the 2005 enhancements in my 2000
DB's, but I just want to be sure that if I stick to ANSI SQL that will I be
OK... For example, do SQL8 & 9 have compatible data files/backup files - I
often transfer data by restoring a backup on a different server or by copy a
data file and attaching it.
Update: I've just noticed that you can install SQL 2000 alongside 2005, and
I've also spotted the compatability settings. Is it better to try and
develop in the one system (2005) or should I install SQL 2000 alongside it?
(note: I've got a new development machine so I have a 'blank canvas' so to
speak; SQL 2000 is currently not installed)
Thanks
Chris
|||Keeping both versions and doing work in the appropriate one seems safer to
me...
ML
http://milambda.blogspot.com/
|||
> OK... For example, do SQL8 & 9 have compatible data files/backup files - I
> often transfer data by restoring a backup on a different server or by copy
> a data file and attaching it.
No - you cannot restore a database from sql server 2005 to a database in sql
server 2000. Same for detach/attach. I believe the reverse direction is
supported.
|||"Scott Morris" <bogus@.bogus.com> wrote in message
news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> No - you cannot restore a database from sql server 2005 to a database in
> sql server 2000. Same for detach/attach. I believe the reverse direction
> is supported.
>
Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but it appears from what you (and others) say that it
works from 2000 to 2005 which is useful to know.
However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...
|||I definitely agree that you should have side-by-side and develop on a "pure" 2000. Short story is
that database compatibility level isn't 100%...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:umKq9FQIGHA.3904@.TK2MSFTNGP10.phx.gbl...
> "Scott Morris" <bogus@.bogus.com> wrote in message news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> Sorry - I should have been more clear. I don't expect to restore a 2005 DB to a 2000 instance, but
> it appears from what you (and others) say that it works from 2000 to 2005 which is useful to know.
> However, I think I'm erring towards installing 2000 and 2005 side-by-side instead...
>
Developing for 2000 (SQL8) on 2005 (SQL9)
We've started upgrading some of our servers to 2005 from 2000, and that
includes my development machine.
I slightly concerned that I will inadvertantly throw in some 2005 code in my
2000 databases which will screw up the destination database on deployment.
Is there a way of specifying that a DB should be 2000-compliant?
What other pitfalls might I face? Any other good advice?
In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
don't think I've been pushing the boundaries with anything I'm doing at the
moment, so I dont expect too many problems, but you never know...
Thanks in advance...
--
cjmnews04@.REMOVEMEyahoo.co.uk
[remove the obvious bits]CJM
As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
2005
Are you talking about T-SQL enhances in SQL Server 2005?
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||I keep both versions installed for different kinds of work and simply do not
worry about potential risks, since 2005 features simply do not exist in 2000.
ML
--
http://milambda.blogspot.com/|||You can come a bit closer to 2000 compliant by specifying database compatibility level 80 instead of
the default 90. See sp_dbcmptlevel for details.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that includes my development
> machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in my 2000 databases which
> will screw up the destination database on deployment. Is there a way of specifying that a DB
> should be 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I don't think I've been
> pushing the boundaries with anything I'm doing at the moment, so I dont expect too many problems,
> but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23Orrb4OIGHA.3036@.tk2msftngp13.phx.gbl...
> CJM
> As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
> 2005
> Are you talking about T-SQL enhances in SQL Server 2005?
>
I'm talking about anything I don't know! :)
Obviously I don't intend to use any of the 2005 enhancements in my 2000
DB's, but I just want to be sure that if I stick to ANSI SQL that will I be
OK... For example, do SQL8 & 9 have compatible data files/backup files - I
often transfer data by restoring a backup on a different server or by copy a
data file and attaching it.
Update: I've just noticed that you can install SQL 2000 alongside 2005, and
I've also spotted the compatability settings. Is it better to try and
develop in the one system (2005) or should I install SQL 2000 alongside it?
(note: I've got a new development machine so I have a 'blank canvas' so to
speak; SQL 2000 is currently not installed)
Thanks
Chris|||Keeping both versions and doing work in the appropriate one seems safer to
me...
ML
--
http://milambda.blogspot.com/|||> OK... For example, do SQL8 & 9 have compatible data files/backup files - I
> often transfer data by restoring a backup on a different server or by copy
> a data file and attaching it.
No - you cannot restore a database from sql server 2005 to a database in sql
server 2000. Same for detach/attach. I believe the reverse direction is
supported.|||"Scott Morris" <bogus@.bogus.com> wrote in message
news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> No - you cannot restore a database from sql server 2005 to a database in
> sql server 2000. Same for detach/attach. I believe the reverse direction
> is supported.
>
Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but it appears from what you (and others) say that it
works from 2000 to 2005 which is useful to know.
However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...|||I definitely agree that you should have side-by-side and develop on a "pure" 2000. Short story is
that database compatibility level isn't 100%...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:umKq9FQIGHA.3904@.TK2MSFTNGP10.phx.gbl...
> "Scott Morris" <bogus@.bogus.com> wrote in message news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
>> No - you cannot restore a database from sql server 2005 to a database in sql server 2000. Same
>> for detach/attach. I believe the reverse direction is supported.
> Sorry - I should have been more clear. I don't expect to restore a 2005 DB to a 2000 instance, but
> it appears from what you (and others) say that it works from 2000 to 2005 which is useful to know.
> However, I think I'm erring towards installing 2000 and 2005 side-by-side instead...
>
includes my development machine.
I slightly concerned that I will inadvertantly throw in some 2005 code in my
2000 databases which will screw up the destination database on deployment.
Is there a way of specifying that a DB should be 2000-compliant?
What other pitfalls might I face? Any other good advice?
In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
don't think I've been pushing the boundaries with anything I'm doing at the
moment, so I dont expect too many problems, but you never know...
Thanks in advance...
--
cjmnews04@.REMOVEMEyahoo.co.uk
[remove the obvious bits]CJM
As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
2005
Are you talking about T-SQL enhances in SQL Server 2005?
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message
news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that
> includes my development machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in
> my 2000 databases which will screw up the destination database on
> deployment. Is there a way of specifying that a DB should be
> 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I
> don't think I've been pushing the boundaries with anything I'm doing at
> the moment, so I dont expect too many problems, but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||I keep both versions installed for different kinds of work and simply do not
worry about potential risks, since 2005 features simply do not exist in 2000.
ML
--
http://milambda.blogspot.com/|||You can come a bit closer to 2000 compliant by specifying database compatibility level 80 instead of
the default 90. See sp_dbcmptlevel for details.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:edaDM0OIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> We've started upgrading some of our servers to 2005 from 2000, and that includes my development
> machine.
> I slightly concerned that I will inadvertantly throw in some 2005 code in my 2000 databases which
> will screw up the destination database on deployment. Is there a way of specifying that a DB
> should be 2000-compliant?
> What other pitfalls might I face? Any other good advice?
> In relative terms, I'm dealing with small-ish DBs (<100,000 rows) and I don't think I've been
> pushing the boundaries with anything I'm doing at the moment, so I dont expect too many problems,
> but you never know...
> Thanks in advance...
> --
> cjmnews04@.REMOVEMEyahoo.co.uk
> [remove the obvious bits]
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23Orrb4OIGHA.3036@.tk2msftngp13.phx.gbl...
> CJM
> As far as I know one thing is TOP 100 PERCENT doesn't work in SQL Server
> 2005
> Are you talking about T-SQL enhances in SQL Server 2005?
>
I'm talking about anything I don't know! :)
Obviously I don't intend to use any of the 2005 enhancements in my 2000
DB's, but I just want to be sure that if I stick to ANSI SQL that will I be
OK... For example, do SQL8 & 9 have compatible data files/backup files - I
often transfer data by restoring a backup on a different server or by copy a
data file and attaching it.
Update: I've just noticed that you can install SQL 2000 alongside 2005, and
I've also spotted the compatability settings. Is it better to try and
develop in the one system (2005) or should I install SQL 2000 alongside it?
(note: I've got a new development machine so I have a 'blank canvas' so to
speak; SQL 2000 is currently not installed)
Thanks
Chris|||Keeping both versions and doing work in the appropriate one seems safer to
me...
ML
--
http://milambda.blogspot.com/|||> OK... For example, do SQL8 & 9 have compatible data files/backup files - I
> often transfer data by restoring a backup on a different server or by copy
> a data file and attaching it.
No - you cannot restore a database from sql server 2005 to a database in sql
server 2000. Same for detach/attach. I believe the reverse direction is
supported.|||"Scott Morris" <bogus@.bogus.com> wrote in message
news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
> No - you cannot restore a database from sql server 2005 to a database in
> sql server 2000. Same for detach/attach. I believe the reverse direction
> is supported.
>
Sorry - I should have been more clear. I don't expect to restore a 2005 DB
to a 2000 instance, but it appears from what you (and others) say that it
works from 2000 to 2005 which is useful to know.
However, I think I'm erring towards installing 2000 and 2005 side-by-side
instead...|||I definitely agree that you should have side-by-side and develop on a "pure" 2000. Short story is
that database compatibility level isn't 100%...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"CJM" <cjmnews04@.newsgroup.nospam> wrote in message news:umKq9FQIGHA.3904@.TK2MSFTNGP10.phx.gbl...
> "Scott Morris" <bogus@.bogus.com> wrote in message news:uZpP%23CQIGHA.2064@.TK2MSFTNGP09.phx.gbl...
>> No - you cannot restore a database from sql server 2005 to a database in sql server 2000. Same
>> for detach/attach. I believe the reverse direction is supported.
> Sorry - I should have been more clear. I don't expect to restore a 2005 DB to a 2000 instance, but
> it appears from what you (and others) say that it works from 2000 to 2005 which is useful to know.
> However, I think I'm erring towards installing 2000 and 2005 side-by-side instead...
>
developing enterprise using c# and dmo
hi all,
i have a question ,
i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager for use it with Desktop engine,for you it is legal develop and sell this software?
Thanks.
AFAIK, yes. DMO is re-distributable. Just note that there already exists a number of these admin tools, where
some are free...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GMC" <killthedrake@.yahoo.it> wrote in message news:9601E139-1667-4C83-8A7F-7EC2564EFBB4@.microsoft.com...
> hi all,
> i have a question ,
> i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager for use it with Desktop
engine,for you it is legal develop and sell this software?
> Thanks.
i have a question ,
i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager for use it with Desktop engine,for you it is legal develop and sell this software?
Thanks.
AFAIK, yes. DMO is re-distributable. Just note that there already exists a number of these admin tools, where
some are free...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GMC" <killthedrake@.yahoo.it> wrote in message news:9601E139-1667-4C83-8A7F-7EC2564EFBB4@.microsoft.com...
> hi all,
> i have a question ,
> i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager for use it with Desktop
engine,for you it is legal develop and sell this software?
> Thanks.
developing enterprise using c# and dmo
hi all,
i have a question ,
i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager for use it with Desktop engine,for you it is legal develop and sell this software?
Thanks.AFAIK, yes. DMO is re-distributable. Just note that there already exists a number of these admin tools, where
some are free...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GMC" <killthedrake@.yahoo.it> wrote in message news:9601E139-1667-4C83-8A7F-7EC2564EFBB4@.microsoft.com...
> hi all,
> i have a question ,
> i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager for use it with Desktop
engine,for you it is legal develop and sell this software?
> Thanks.
i have a question ,
i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager for use it with Desktop engine,for you it is legal develop and sell this software?
Thanks.AFAIK, yes. DMO is re-distributable. Just note that there already exists a number of these admin tools, where
some are free...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GMC" <killthedrake@.yahoo.it> wrote in message news:9601E139-1667-4C83-8A7F-7EC2564EFBB4@.microsoft.com...
> hi all,
> i have a question ,
> i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager for use it with Desktop
engine,for you it is legal develop and sell this software?
> Thanks.
developing enterprise using c# and dmo
hi all,
i have a question ,
i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager
for use it with Desktop engine,for you it is legal develop and sell this s
oftware?
Thanks.AFAIK, yes. DMO is re-distributable. Just note that there already exists a n
umber of these admin tools, where
some are free...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GMC" <killthedrake@.yahoo.it> wrote in message news:9601E139-1667-4C83-8A7F-7EC2564EFBB4@.mic
rosoft.com...
> hi all,
> i have a question ,
> i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager
for use it with Desktop
engine,for you it is legal develop and sell this software?
> Thanks.
i have a question ,
i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager
for use it with Desktop engine,for you it is legal develop and sell this s
oftware?
Thanks.AFAIK, yes. DMO is re-distributable. Just note that there already exists a n
umber of these admin tools, where
some are free...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GMC" <killthedrake@.yahoo.it> wrote in message news:9601E139-1667-4C83-8A7F-7EC2564EFBB4@.mic
rosoft.com...
> hi all,
> i have a question ,
> i'm interested to develop (using c# and SqlDmo) a little Enterprise Manager
for use it with Desktop
engine,for you it is legal develop and sell this software?
> Thanks.
developing custom components by extending the SSIS stock data flow components
Everything I've read says that custom data flow components are built by inheriting from the Microsoft.SqlServer.Dts.Pipeline.PipelineComponent class.
But the stock components such as the Derived Column data flow transformation must each be implemented by their own class. So how do I base my custom components on those classes? The documentation for the PipelineComponent class doesn't list any such subclasses.
Not possible unfortunately. Those classes are not overrideable.
There is functionality hopefully coming in the next version which may mean this is possible (although via a slightly different method).
-Jamie
Developing CLR Objects - Visual Studio Requirements?
I have SQL 2005 Express & Visual Studio 2005 Standard on my XP workstation,
and SQL 2005 Standard installed on my Win2k3 server. I can't find anywhere
on either system's VS installation the option to create a new Sql
Project/Solution to create CLR objects. Am I missing something, or do I
need VS Professional?
CraigHi Craig,
the option should be under
FIle --> New --> Project --> (Programming Language, e.g. C# ) -->
Database --> SQLServer project
In the Project you can define new object types like functions /
procedures / UDA etc.
HTH, Jens Suessmeyer.|||AFAIK, you need VS Professional version or (beta of) Team System dev.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/bobb
"Craig S" <cscheets@.dontspam.kc.rr.com> wrote in message
news:e$AATwKDGHA.1384@.TK2MSFTNGP11.phx.gbl...
>I have SQL 2005 Express & Visual Studio 2005 Standard on my XP workstation,
>and SQL 2005 Standard installed on my Win2k3 server. I can't find anywhere
>on either system's VS installation the option to create a new Sql
>Project/Solution to create CLR objects. Am I missing something, or do I
>need VS Professional?
> Craig
>|||You don't need to use Visual Studio to create and run
assemblies in SQL Server:
http://www.eggheadcafe.com/articles...5_clr_regex.asp
Robbe Morris - 2004/2005 Microsoft MVP C#
http://www.eggheadcafe.com/forums/merit.asp
"Craig S" <cscheets@.dontspam.kc.rr.com> wrote in message
news:e$AATwKDGHA.1384@.TK2MSFTNGP11.phx.gbl...
>I have SQL 2005 Express & Visual Studio 2005 Standard on my XP workstation,
>and SQL 2005 Standard installed on my Win2k3 server. I can't find anywhere
>on either system's VS installation the option to create a new Sql
>Project/Solution to create CLR objects. Am I missing something, or do I
>need VS Professional?
> Craig
>|||True. By the description in the posting, it appeared that he was looking for
the built-in Visual Studio "SQL Server Projects" for .NET languages, that
are included as part of some editions of Visual Studio.
You could conceivably develop and deploy SQLCLR assemblies with a command
line compiler and SQLCMD.exe.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Robbe Morris [C# MVP]" <info@.eggheadcafe.com> wrote in message
news:%23XoVWSLDGHA.3984@.TK2MSFTNGP14.phx.gbl...
> You don't need to use Visual Studio to create and run
> assemblies in SQL Server:
> http://www.eggheadcafe.com/articles...5_clr_regex.asp
> --
> Robbe Morris - 2004/2005 Microsoft MVP C#
> http://www.eggheadcafe.com/forums/merit.asp
>
>
> "Craig S" <cscheets@.dontspam.kc.rr.com> wrote in message
> news:e$AATwKDGHA.1384@.TK2MSFTNGP11.phx.gbl...
>|||Niels Berglund has released an custom SQL Server project, VS addin and a
stand-alone SQL CLR deployment tool which work with any edition of Visual
Studio.
http://staff.develop.com/nielsb/cod...ropAndAddIn.zip
David
"Bob Beauchemin" <no_bobb_spam@.sqlskills.com> wrote in message
news:%23AIOLzMDGHA.628@.TK2MSFTNGP14.phx.gbl...
> True. By the description in the posting, it appeared that he was looking
> for the built-in Visual Studio "SQL Server Projects" for .NET languages,
> that are included as part of some editions of Visual Studio.
> You could conceivably develop and deploy SQLCLR assemblies with a command
> line compiler and SQLCMD.exe.
> Cheers,
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb
>
> "Robbe Morris [C# MVP]" <info@.eggheadcafe.com> wrote in message
> news:%23XoVWSLDGHA.3984@.TK2MSFTNGP14.phx.gbl...
>|||Yep. I was aware of that too. ;-) It sounded as though the questioner was
asking/wondering why the built-in projects didn't show up, rather than what
are the choices when...
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:eYUIWFNDGHA.748@.TK2MSFTNGP12.phx.gbl...
> Niels Berglund has released an custom SQL Server project, VS addin and a
> stand-alone SQL CLR deployment tool which work with any edition of Visual
> Studio.
> http://staff.develop.com/nielsb/cod...ropAndAddIn.zip
> David
>
> "Bob Beauchemin" <no_bobb_spam@.sqlskills.com> wrote in message
> news:%23AIOLzMDGHA.628@.TK2MSFTNGP14.phx.gbl...
>|||I was kind of asking both, mainly "how do I develop one without notepad.exe"
:) I found all of these posts to be both correct and very helpful, thank
you all.
Craig
"Bob Beauchemin" <no_bobb_spam@.sqlskills.com> wrote in message
news:uCuImBODGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Yep. I was aware of that too. ;-) It sounded as though the questioner was
> asking/wondering why the built-in projects didn't show up, rather than
> what are the choices when...
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:eYUIWFNDGHA.748@.TK2MSFTNGP12.phx.gbl...
>
and SQL 2005 Standard installed on my Win2k3 server. I can't find anywhere
on either system's VS installation the option to create a new Sql
Project/Solution to create CLR objects. Am I missing something, or do I
need VS Professional?
CraigHi Craig,
the option should be under
FIle --> New --> Project --> (Programming Language, e.g. C# ) -->
Database --> SQLServer project
In the Project you can define new object types like functions /
procedures / UDA etc.
HTH, Jens Suessmeyer.|||AFAIK, you need VS Professional version or (beta of) Team System dev.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/bobb
"Craig S" <cscheets@.dontspam.kc.rr.com> wrote in message
news:e$AATwKDGHA.1384@.TK2MSFTNGP11.phx.gbl...
>I have SQL 2005 Express & Visual Studio 2005 Standard on my XP workstation,
>and SQL 2005 Standard installed on my Win2k3 server. I can't find anywhere
>on either system's VS installation the option to create a new Sql
>Project/Solution to create CLR objects. Am I missing something, or do I
>need VS Professional?
> Craig
>|||You don't need to use Visual Studio to create and run
assemblies in SQL Server:
http://www.eggheadcafe.com/articles...5_clr_regex.asp
Robbe Morris - 2004/2005 Microsoft MVP C#
http://www.eggheadcafe.com/forums/merit.asp
"Craig S" <cscheets@.dontspam.kc.rr.com> wrote in message
news:e$AATwKDGHA.1384@.TK2MSFTNGP11.phx.gbl...
>I have SQL 2005 Express & Visual Studio 2005 Standard on my XP workstation,
>and SQL 2005 Standard installed on my Win2k3 server. I can't find anywhere
>on either system's VS installation the option to create a new Sql
>Project/Solution to create CLR objects. Am I missing something, or do I
>need VS Professional?
> Craig
>|||True. By the description in the posting, it appeared that he was looking for
the built-in Visual Studio "SQL Server Projects" for .NET languages, that
are included as part of some editions of Visual Studio.
You could conceivably develop and deploy SQLCLR assemblies with a command
line compiler and SQLCMD.exe.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Robbe Morris [C# MVP]" <info@.eggheadcafe.com> wrote in message
news:%23XoVWSLDGHA.3984@.TK2MSFTNGP14.phx.gbl...
> You don't need to use Visual Studio to create and run
> assemblies in SQL Server:
> http://www.eggheadcafe.com/articles...5_clr_regex.asp
> --
> Robbe Morris - 2004/2005 Microsoft MVP C#
> http://www.eggheadcafe.com/forums/merit.asp
>
>
> "Craig S" <cscheets@.dontspam.kc.rr.com> wrote in message
> news:e$AATwKDGHA.1384@.TK2MSFTNGP11.phx.gbl...
>|||Niels Berglund has released an custom SQL Server project, VS addin and a
stand-alone SQL CLR deployment tool which work with any edition of Visual
Studio.
http://staff.develop.com/nielsb/cod...ropAndAddIn.zip
David
"Bob Beauchemin" <no_bobb_spam@.sqlskills.com> wrote in message
news:%23AIOLzMDGHA.628@.TK2MSFTNGP14.phx.gbl...
> True. By the description in the posting, it appeared that he was looking
> for the built-in Visual Studio "SQL Server Projects" for .NET languages,
> that are included as part of some editions of Visual Studio.
> You could conceivably develop and deploy SQLCLR assemblies with a command
> line compiler and SQLCMD.exe.
> Cheers,
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb
>
> "Robbe Morris [C# MVP]" <info@.eggheadcafe.com> wrote in message
> news:%23XoVWSLDGHA.3984@.TK2MSFTNGP14.phx.gbl...
>|||Yep. I was aware of that too. ;-) It sounded as though the questioner was
asking/wondering why the built-in projects didn't show up, rather than what
are the choices when...
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:eYUIWFNDGHA.748@.TK2MSFTNGP12.phx.gbl...
> Niels Berglund has released an custom SQL Server project, VS addin and a
> stand-alone SQL CLR deployment tool which work with any edition of Visual
> Studio.
> http://staff.develop.com/nielsb/cod...ropAndAddIn.zip
> David
>
> "Bob Beauchemin" <no_bobb_spam@.sqlskills.com> wrote in message
> news:%23AIOLzMDGHA.628@.TK2MSFTNGP14.phx.gbl...
>|||I was kind of asking both, mainly "how do I develop one without notepad.exe"
:) I found all of these posts to be both correct and very helpful, thank
you all.
Craig
"Bob Beauchemin" <no_bobb_spam@.sqlskills.com> wrote in message
news:uCuImBODGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Yep. I was aware of that too. ;-) It sounded as though the questioner was
> asking/wondering why the built-in projects didn't show up, rather than
> what are the choices when...
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:eYUIWFNDGHA.748@.TK2MSFTNGP12.phx.gbl...
>
Developing app that will use SQL Server Express on back end...
Hi...
I have the full version of SQL Server installed on my machine and am developing an app using BI DTS packages, VB.Net, SQL SPs, etc.. I will need to deploy this app w/SQL Server Express (SSE).
-Do I have to install SSE on my development machine for the purpose of creating the install package of my application? I am afraid that if I do install SSE on my machine, it may mess up my installation of the full version of SQL Server... will it?
-Can you point me to a link with information about how to do the development with the full version of SS, and create the installation package using the SSE?
Thanks for your help.
Steph
You cannot deployment SQL Server 2005 Integration Services packages in SQL Server Express because the runtime now comes with the server license. In SQL Server 2000 the DTS package comes with the runtime that changed in 2005. Hope this helps.|||Thanks for the response.
The way I posed my question was misleading. I'm sorry about that. I shouldn't even have mentioned the DTS packages.
The big picture of the app is this:
- Data resides in a datamart at a central office. The central office will be running the full SQL Server 2005 version (this is where the DTS packages reside and run).
- Satellite (very small) offices need to download updated information relating to them from the central office. I'm thinking of having these satellite offices run SQL Express.
I'm developing the code to update the satellite office data from the central office data. On my development system, I am running the full version of SQL Server 2005. Should I also install SQL Express on my development system ? Will it mess up my full SQL Server 2005 installation?
Thanks,
Steph
|||It is tricky but here is how you could do it legally create Asp.net application run it from your main office SQL Server create a job to execute the many versions of the package make your small offices destination. It will take more work but the alternative solution may cost you more hardware SQL Server Express can be a subscriber in replication so you can push the data with replication. You could always talk to your local Microsoft SQL Server contact person, in some areas there is regional contact person. Hope this helps
Developing a Windows Authentication Security Model
I would like to use Windows Authentication for SQL Server 2005. I'm just no
w
trying to determine how this will work in our environment. Here are some of
my requirements.
- A given users may have different right in the each environment
(Development, QA, and production.
- A user will gain access to sql server via ione or more Domain Groups
- Do not want to change security permissions on a database when migrating it
from one environment to another.
So my real problem is how can a single windows account (user) have different
rights on say database ABC for each environment and meet the above
requirements.
Ok let's say our user is named "domain\user1" and they need to following
access in each environment:
Select, insert, update, and delete permissions on table ABC.dbo.MyTable in
development.
Select, update permissions on table ABC.dbo.MyTable in QA
Select only permissions on table ABC.dbo.MyTable in Production.
So my questions is how do I define one or more windows group that
"domain\user1" would be a member so when I assign the windows group to a SQL
and grant them access to a database that the access changes depending on the
environment for which the database is being accessed?
If you are looking for SQL Server examples check out my Website at
http://www.geocities.com/sqlserverexamplesLet me add that the development environment has a separate domain, but the Q
A
and production environment have the same domain.
--
If you are looking for SQL Server examples check out my Website at
http://www.geocities.com/sqlserverexamples
"Greg Larsen" wrote:
> I would like to use Windows Authentication for SQL Server 2005. I'm just
now
> trying to determine how this will work in our environment. Here are some
of
> my requirements.
> - A given users may have different right in the each environment
> (Development, QA, and production.
> - A user will gain access to sql server via ione or more Domain Groups
> - Do not want to change security permissions on a database when migrating
it
> from one environment to another.
> So my real problem is how can a single windows account (user) have differe
nt
> rights on say database ABC for each environment and meet the above
> requirements.
> Ok let's say our user is named "domain\user1" and they need to following
> access in each environment:
> Select, insert, update, and delete permissions on table ABC.dbo.MyTable in
> development.
> Select, update permissions on table ABC.dbo.MyTable in QA
> Select only permissions on table ABC.dbo.MyTable in Production.
> So my questions is how do I define one or more windows group that
> "domain\user1" would be a member so when I assign the windows group to a S
QL
> and grant them access to a database that the access changes depending on t
he
> environment for which the database is being accessed?
> If you are looking for SQL Server examples check out my Website at
> http://www.geocities.com/sqlserverexamples
w
trying to determine how this will work in our environment. Here are some of
my requirements.
- A given users may have different right in the each environment
(Development, QA, and production.
- A user will gain access to sql server via ione or more Domain Groups
- Do not want to change security permissions on a database when migrating it
from one environment to another.
So my real problem is how can a single windows account (user) have different
rights on say database ABC for each environment and meet the above
requirements.
Ok let's say our user is named "domain\user1" and they need to following
access in each environment:
Select, insert, update, and delete permissions on table ABC.dbo.MyTable in
development.
Select, update permissions on table ABC.dbo.MyTable in QA
Select only permissions on table ABC.dbo.MyTable in Production.
So my questions is how do I define one or more windows group that
"domain\user1" would be a member so when I assign the windows group to a SQL
and grant them access to a database that the access changes depending on the
environment for which the database is being accessed?
If you are looking for SQL Server examples check out my Website at
http://www.geocities.com/sqlserverexamplesLet me add that the development environment has a separate domain, but the Q
A
and production environment have the same domain.
--
If you are looking for SQL Server examples check out my Website at
http://www.geocities.com/sqlserverexamples
"Greg Larsen" wrote:
> I would like to use Windows Authentication for SQL Server 2005. I'm just
now
> trying to determine how this will work in our environment. Here are some
of
> my requirements.
> - A given users may have different right in the each environment
> (Development, QA, and production.
> - A user will gain access to sql server via ione or more Domain Groups
> - Do not want to change security permissions on a database when migrating
it
> from one environment to another.
> So my real problem is how can a single windows account (user) have differe
nt
> rights on say database ABC for each environment and meet the above
> requirements.
> Ok let's say our user is named "domain\user1" and they need to following
> access in each environment:
> Select, insert, update, and delete permissions on table ABC.dbo.MyTable in
> development.
> Select, update permissions on table ABC.dbo.MyTable in QA
> Select only permissions on table ABC.dbo.MyTable in Production.
> So my questions is how do I define one or more windows group that
> "domain\user1" would be a member so when I assign the windows group to a S
QL
> and grant them access to a database that the access changes depending on t
he
> environment for which the database is being accessed?
> If you are looking for SQL Server examples check out my Website at
> http://www.geocities.com/sqlserverexamples
Subscribe to:
Posts (Atom)