Mirrored databases and Witness server

We are upgrading to 2005 and have decided to go to a mirrored 2005
environment. We have picked out the production server (principal) 16
gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
having difficulty finding out how "beefy" a box we need for the Witness
server. Does anyone have any experience with this and can you assist me
in specs. I am working with our Network Administrator.
Thanks for all the help!
KristinaAm 11 Jan 2007 06:32:20 -0800 schrieb KristinaDBA@.gmail.com:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina
Hi, the whitness Server don't need to be so big ;-)
You should install the right editon of SQL Server to be Witness.
The relevance of your sizing are the other roles/jobs this server will do
beside beeing witness.
thats my opinion. hope I could help a little
greetings
Rouven|||Hi,
Kristina - your witness server can be a single processor box with
1/2 GB memory. You can even use SQL Server express. The resources
needed for the witness server is minimum.
This from our Microsoft pre-sales rep.
hth
KristinaDBA@.gmail.com wrote:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina|||Hey - thanks everyone for the help! I love this group!
JoeyD wrote:
> Hi,
> Kristina - your witness server can be a single processor box with
> 1/2 GB memory. You can even use SQL Server express. The resources
> needed for the witness server is minimum.
> This from our Microsoft pre-sales rep.
> hth
>
> KristinaDBA@.gmail.com wrote:
> > We are upgrading to 2005 and have decided to go to a mirrored 2005
> > environment. We have picked out the production server (principal) 16
> > gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> > having difficulty finding out how "beefy" a box we need for the Witness
> > server. Does anyone have any experience with this and can you assist me
> > in specs. I am working with our Network Administrator.
> >
> > Thanks for all the help!
> >
> > Kristina|||While being a witness is not a very hard job, it is important because when
the witness is down, automatic failover won't happen so while you can get by
without a lot of processor or memory resources, you don't want to use your
kid's old game machine for this. Get a good quality machine with a good NIC
card and maybe even a UPS.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<KristinaDBA@.gmail.com> wrote in message
news:1168528668.044990.221330@.i56g2000hsf.googlegroups.com...
> Hey - thanks everyone for the help! I love this group!
> JoeyD wrote:
>> Hi,
>> Kristina - your witness server can be a single processor box with
>> 1/2 GB memory. You can even use SQL Server express. The resources
>> needed for the witness server is minimum.
>> This from our Microsoft pre-sales rep.
>> hth
>>
>> KristinaDBA@.gmail.com wrote:
>> > We are upgrading to 2005 and have decided to go to a mirrored 2005
>> > environment. We have picked out the production server (principal) 16
>> > gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
>> > having difficulty finding out how "beefy" a box we need for the Witness
>> > server. Does anyone have any experience with this and can you assist me
>> > in specs. I am working with our Network Administrator.
>> >
>> > Thanks for all the help!
>> >
>> > Kristina
>

Mimic SQL Server environment

I have SQL Server 2000 installed on Windows 2003 server. SQL Server
environment was set up about a year ago. I would like to known all of the
items I need to look at on SQL Server to mimic this environment. I have
started with SQL Server configuration (sp_Configure).
What items am I missing to mimic SQL Server?
Thanks,
Depends on what you mean by mimic...
You might wish to ensure the IO subsystems are the same.
You might wish to ensure each database is set up similary in physical
structure as well as attributes ( sp_dboption)
You might with to ensure the logins match. ( look in books on line for log
shipping and there is a document about how to make the warm standby the
production server. It includes a section on making the logins and users
match.)
Think about whether replication needs to be matched.
Think about sql agent jobs, etc ( included in msdb).
Hope this helps...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mark T." <Mark T.@.discussions.microsoft.com> wrote in message
news:D76C7697-5336-494A-ADA5-ABC75B7AB421@.microsoft.com...
> I have SQL Server 2000 installed on Windows 2003 server. SQL Server
> environment was set up about a year ago. I would like to known all of the
> items I need to look at on SQL Server to mimic this environment. I have
> started with SQL Server configuration (sp_Configure).
> What items am I missing to mimic SQL Server?
> Thanks,

Mimic SQL Server environment

I have SQL Server 2000 installed on Windows 2003 server. SQL Server
environment was set up about a year ago. I would like to known all of the
items I need to look at on SQL Server to mimic this environment. I have
started with SQL Server configuration (sp_Configure).
What items am I missing to mimic SQL Server?
Thanks,Depends on what you mean by mimic...
You might wish to ensure the IO subsystems are the same.
You might wish to ensure each database is set up similary in physical
structure as well as attributes ( sp_dboption)
You might with to ensure the logins match. ( look in books on line for log
shipping and there is a document about how to make the warm standby the
production server. It includes a section on making the logins and users
match.)
Think about whether replication needs to be matched.
Think about sql agent jobs, etc ( included in msdb).
Hope this helps...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mark T." <Mark T.@.discussions.microsoft.com> wrote in message
news:D76C7697-5336-494A-ADA5-ABC75B7AB421@.microsoft.com...
> I have SQL Server 2000 installed on Windows 2003 server. SQL Server
> environment was set up about a year ago. I would like to known all of the
> items I need to look at on SQL Server to mimic this environment. I have
> started with SQL Server configuration (sp_Configure).
> What items am I missing to mimic SQL Server?
> Thanks,

Mimic SQL Server environment

I have SQL Server 2000 installed on Windows 2003 server. SQL Server
environment was set up about a year ago. I would like to known all of the
items I need to look at on SQL Server to mimic this environment. I have
started with SQL Server configuration (sp_Configure).
What items am I missing to mimic SQL Server?
Thanks,Depends on what you mean by mimic...
You might wish to ensure the IO subsystems are the same.
You might wish to ensure each database is set up similary in physical
structure as well as attributes ( sp_dboption)
You might with to ensure the logins match. ( look in books on line for log
shipping and there is a document about how to make the warm standby the
production server. It includes a section on making the logins and users
match.)
Think about whether replication needs to be matched.
Think about sql agent jobs, etc ( included in msdb).
Hope this helps...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mark T." <Mark T.@.discussions.microsoft.com> wrote in message
news:D76C7697-5336-494A-ADA5-ABC75B7AB421@.microsoft.com...
> I have SQL Server 2000 installed on Windows 2003 server. SQL Server
> environment was set up about a year ago. I would like to known all of the
> items I need to look at on SQL Server to mimic this environment. I have
> started with SQL Server configuration (sp_Configure).
> What items am I missing to mimic SQL Server?
> Thanks,

Migration to SQL 2005 ... how to setup the new enviroment

Hello,

I have been made the point person for our migration to SQL2005. We are a law firm with approximately 750 users. The first SQL environment we will be upgrading is our document management system (DMS). This is an intensive SQL product. After this migration we will more of to our finical system, records system and then all home grown databases.

What we would like to do is consolidate servers and scale out the new SQL environment to a farm. After some initial research it does not look like we will be able to scale out, since the data in the DMS is always changing.

Does anyone have some advice or guidance on what direction we should be looking? I have done tons a online searches and can find out information on everything to do with SQL, except this.

Thanks in advance,

Jeff Carroll

See this link and watch webcast #4...

http://www.microsoft.com/events/series/technetsqlserver2005.mspx

Migration from SQL2000 to Cluster SQL2005 ?

Hello Everyone,
What is the best solution for my predictament? I'm moving from a single
non-cluster SQL2000 STD environment (Server A) to a clustered SQL 2005 STD
environment (Server B). Seamlessly as possible, how can I migrate the
databases from Server A to Server B? I would like to preserve my instance
name on Server A with the new cluster environment (Server B) if possible.
Thank you
Alex Anderson
You can't do this as an in place upgrade. You are going to have to build
the new cluster, install a SQL Server failover cluster instance, and then
move the databases. The most seamless way would be using a detach/attach or
a backup/restore. You'll have to make sure you take care of the master and
msdb databases as well.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Alex Anderson" <Alex Anderson@.discussions.microsoft.com> wrote in message
news:BC54F1A0-BEE4-4492-8934-4905C80B8005@.microsoft.com...
> Hello Everyone,
> What is the best solution for my predictament? I'm moving from a single
> non-cluster SQL2000 STD environment (Server A) to a clustered SQL 2005 STD
> environment (Server B). Seamlessly as possible, how can I migrate the
> databases from Server A to Server B? I would like to preserve my instance
> name on Server A with the new cluster environment (Server B) if possible.
> Thank you
> Alex Anderson

Migration from 2000 ro 2005 Cluster

Hey All,
We have SQL Server 2000 in our production environment and we have a
brand spanking new cluster that has more CPU power and RAM than our
current server. The issue I have is how to move the data. We have 10
Databases, most are small, but we have a few that are 5 to 9 GB and
one that is over 100 GB.
I've already loaded SQL Server 2005 SP2 on the cluster for testing
etc.
My goal is to reduce downtime, and my stress, when we go live with the
cluster. My fall back plan is, backup the databases, copy the backups
to the cluster and restore them on the cluster.
I had a thought of installing SQL Server 2000 on the clusters and log
ship the databases to the SQL 2000 instance on the cluster, since I
can't log ship from 2000 to 2005. Then when go live day comes, I just
need to restore the existing logs, recover the databases and detach
the databases from 2000, then attach the databases to the 2005. From
what I know this is doable, but has anyone done this or something
similar? Are there any gotchas?
Thanks
Dave Ott<DaveOtt26.2@.gmail.com> wrote in message
news:1172770995.057390.293120@.j27g2000cwj.googlegroups.com...
> Hey All,
> We have SQL Server 2000 in our production environment and we have a
> brand spanking new cluster that has more CPU power and RAM than our
> current server. The issue I have is how to move the data. We have 10
> Databases, most are small, but we have a few that are 5 to 9 GB and
> one that is over 100 GB.
> I've already loaded SQL Server 2005 SP2 on the cluster for testing
> etc.
> My goal is to reduce downtime, and my stress, when we go live with the
> cluster. My fall back plan is, backup the databases, copy the backups
> to the cluster and restore them on the cluster.
> I had a thought of installing SQL Server 2000 on the clusters and log
> ship the databases to the SQL 2000 instance on the cluster, since I
> can't log ship from 2000 to 2005.
You can't? Why not? (I'm 99% sure a you can restore a 2000 database with
NORECOVERY in 2005. You can't however go the other way).
I'd probably go this route, but do it manually.
I.e. backup the databases, restore to the 2005 cluster with NORECOVERY.
Take a logbackup, restore to 2005 with NORECOVERY (to take care of the lag
in the original backup/restore cycle).
Repeat until you know the next round of log backup/restores will be quick
and then schedule the downtime, do one last log backup/restore and then
switch over to the 2005 server.
(I'd actually practice this once with a test client and then redo the entire
process if possible.)
Script it all out so it's fast and few mistakes.

> Then when go live day comes, I just
> need to restore the existing logs, recover the databases and detach
> the databases from 2000, then attach the databases to the 2005. From
> what I know this is doable, but has anyone done this or something
> similar? Are there any gotchas?
Seems to me more complicated than it's worth.

> Thanks
> Dave Ott
>|||If you do it all by scripts, you can log ship from SQL 2000 to SQL 2005.
You cannot use the STANDBY option but NORECOVERY works just fine. There is
no need for a SQL 2000 instance cluttering things up.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:Ozz1v$CXHHA.528@.TK2MSFTNGP03.phx.gbl...
> <DaveOtt26.2@.gmail.com> wrote in message
> news:1172770995.057390.293120@.j27g2000cwj.googlegroups.com...
> You can't? Why not? (I'm 99% sure a you can restore a 2000 database with
> NORECOVERY in 2005. You can't however go the other way).
> I'd probably go this route, but do it manually.
> I.e. backup the databases, restore to the 2005 cluster with NORECOVERY.
> Take a logbackup, restore to 2005 with NORECOVERY (to take care of the lag
> in the original backup/restore cycle).
> Repeat until you know the next round of log backup/restores will be quick
> and then schedule the downtime, do one last log backup/restore and then
> switch over to the 2005 server.
> (I'd actually practice this once with a test client and then redo the
> entire process if possible.)
> Script it all out so it's fast and few mistakes.
>
> Seems to me more complicated than it's worth.
>
>|||Geoff,
Once again you are there with the answer!
Thanks
Dave

Migration from 2000 ro 2005 Cluster

Hey All,
We have SQL Server 2000 in our production environment and we have a
brand spanking new cluster that has more CPU power and RAM than our
current server. The issue I have is how to move the data. We have 10
Databases, most are small, but we have a few that are 5 to 9 GB and
one that is over 100 GB.
I've already loaded SQL Server 2005 SP2 on the cluster for testing
etc.
My goal is to reduce downtime, and my stress, when we go live with the
cluster. My fall back plan is, backup the databases, copy the backups
to the cluster and restore them on the cluster.
I had a thought of installing SQL Server 2000 on the clusters and log
ship the databases to the SQL 2000 instance on the cluster, since I
can't log ship from 2000 to 2005. Then when go live day comes, I just
need to restore the existing logs, recover the databases and detach
the databases from 2000, then attach the databases to the 2005. From
what I know this is doable, but has anyone done this or something
similar? Are there any gotchas?
Thanks
Dave Ott<DaveOtt26.2@.gmail.com> wrote in message
news:1172770995.057390.293120@.j27g2000cwj.googlegroups.com...
> Hey All,
> We have SQL Server 2000 in our production environment and we have a
> brand spanking new cluster that has more CPU power and RAM than our
> current server. The issue I have is how to move the data. We have 10
> Databases, most are small, but we have a few that are 5 to 9 GB and
> one that is over 100 GB.
> I've already loaded SQL Server 2005 SP2 on the cluster for testing
> etc.
> My goal is to reduce downtime, and my stress, when we go live with the
> cluster. My fall back plan is, backup the databases, copy the backups
> to the cluster and restore them on the cluster.
> I had a thought of installing SQL Server 2000 on the clusters and log
> ship the databases to the SQL 2000 instance on the cluster, since I
> can't log ship from 2000 to 2005.
You can't? Why not? (I'm 99% sure a you can restore a 2000 database with
NORECOVERY in 2005. You can't however go the other way).
I'd probably go this route, but do it manually.
I.e. backup the databases, restore to the 2005 cluster with NORECOVERY.
Take a logbackup, restore to 2005 with NORECOVERY (to take care of the lag
in the original backup/restore cycle).
Repeat until you know the next round of log backup/restores will be quick
and then schedule the downtime, do one last log backup/restore and then
switch over to the 2005 server.
(I'd actually practice this once with a test client and then redo the entire
process if possible.)
Script it all out so it's fast and few mistakes.
> Then when go live day comes, I just
> need to restore the existing logs, recover the databases and detach
> the databases from 2000, then attach the databases to the 2005. From
> what I know this is doable, but has anyone done this or something
> similar? Are there any gotchas?
Seems to me more complicated than it's worth.
> Thanks
> Dave Ott
>|||If you do it all by scripts, you can log ship from SQL 2000 to SQL 2005.
You cannot use the STANDBY option but NORECOVERY works just fine. There is
no need for a SQL 2000 instance cluttering things up.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:Ozz1v$CXHHA.528@.TK2MSFTNGP03.phx.gbl...
> <DaveOtt26.2@.gmail.com> wrote in message
> news:1172770995.057390.293120@.j27g2000cwj.googlegroups.com...
>> Hey All,
>> We have SQL Server 2000 in our production environment and we have a
>> brand spanking new cluster that has more CPU power and RAM than our
>> current server. The issue I have is how to move the data. We have 10
>> Databases, most are small, but we have a few that are 5 to 9 GB and
>> one that is over 100 GB.
>> I've already loaded SQL Server 2005 SP2 on the cluster for testing
>> etc.
>> My goal is to reduce downtime, and my stress, when we go live with the
>> cluster. My fall back plan is, backup the databases, copy the backups
>> to the cluster and restore them on the cluster.
>> I had a thought of installing SQL Server 2000 on the clusters and log
>> ship the databases to the SQL 2000 instance on the cluster, since I
>> can't log ship from 2000 to 2005.
> You can't? Why not? (I'm 99% sure a you can restore a 2000 database with
> NORECOVERY in 2005. You can't however go the other way).
> I'd probably go this route, but do it manually.
> I.e. backup the databases, restore to the 2005 cluster with NORECOVERY.
> Take a logbackup, restore to 2005 with NORECOVERY (to take care of the lag
> in the original backup/restore cycle).
> Repeat until you know the next round of log backup/restores will be quick
> and then schedule the downtime, do one last log backup/restore and then
> switch over to the 2005 server.
> (I'd actually practice this once with a test client and then redo the
> entire process if possible.)
> Script it all out so it's fast and few mistakes.
>
>> Then when go live day comes, I just
>> need to restore the existing logs, recover the databases and detach
>> the databases from 2000, then attach the databases to the 2005. From
>> what I know this is doable, but has anyone done this or something
>> similar? Are there any gotchas?
> Seems to me more complicated than it's worth.
>
>> Thanks
>> Dave Ott
>|||Geoff,
Once again you are there with the answer!
Thanks
Dave

Migration 2005 beta to 2005 release

Hi Group,
Three quick questions about the 2005 beta.
1) Is it likely that restoring a 2005 beta database backup to a 2005
release environment (when it is released) will produce errors?
2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
stored procedures?
3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
beta environment?
Cheers,
Stewart"Stewart" <windsurfing_stew@.yahoo.com.au> schrieb im Newsbeitrag
news:3e8a4d01.0504282031.4c10b786@.posting.google.com...
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
There will be an whitepaper for the tap customers,perhpas that will be for
public download for release.

> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
Sure.

> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
Not sure, but I think thats possible, you only need to have to SQL Native
Client installed. I will try it on my box later.

> Cheers,
> Stewart
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--|||Hi
Just be aware, ADO.NET 1.1 does not support the new datatypes that exist in
SQL Server 2005.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stewart" wrote:

> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
> Cheers,
> Stewart
>

Migration 2005 beta to 2005 release

Hi Group,
Three quick questions about the 2005 beta.
1) Is it likely that restoring a 2005 beta database backup to a 2005
release environment (when it is released) will produce errors?
2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
stored procedures?
3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
beta environment?
Cheers,
Stewart
"Stewart" <windsurfing_stew@.yahoo.com.au> schrieb im Newsbeitrag
news:3e8a4d01.0504282031.4c10b786@.posting.google.c om...
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
There will be an whitepaper for the tap customers,perhpas that will be for
public download for release.

> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
Sure.

> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
Not sure, but I think thats possible, you only need to have to SQL Native
Client installed. I will try it on my box later.

> Cheers,
> Stewart
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Hi
Just be aware, ADO.NET 1.1 does not support the new datatypes that exist in
SQL Server 2005.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stewart" wrote:

> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
> Cheers,
> Stewart
>

Migration 2005 beta to 2005 release

Hi Group,
Three quick questions about the 2005 beta.
1) Is it likely that restoring a 2005 beta database backup to a 2005
release environment (when it is released) will produce errors?
2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
stored procedures?
3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
beta environment?
Cheers,
Stewart"Stewart" <windsurfing_stew@.yahoo.com.au> schrieb im Newsbeitrag
news:3e8a4d01.0504282031.4c10b786@.posting.google.com...
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
There will be an whitepaper for the tap customers,perhpas that will be for
public download for release.
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
Sure.
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
Not sure, but I think thats possible, you only need to have to SQL Native
Client installed. I will try it on my box later.
> Cheers,
> Stewart
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Hi
Just be aware, ADO.NET 1.1 does not support the new datatypes that exist in
SQL Server 2005.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stewart" wrote:
> Hi Group,
> Three quick questions about the 2005 beta.
> 1) Is it likely that restoring a 2005 beta database backup to a 2005
> release environment (when it is released) will produce errors?
> 2) Will the .Net framework 1.1 be able to call SQL server 2005 beta
> stored procedures?
> 3) Can I use Visual Studio .Net 1.1 to administer a SQL Server 2005
> beta environment?
> Cheers,
> Stewart
>